Messages

I'm using the OVH DNS servers since the server is behind their firewall. I allowed the Google DNS ip and now it's working, thanks!

I used nslookup on your domain.

Code Select Expand


root@ts:~# nslookup www.stefan1200.de
Server: 213.186.33.99
Address: 213.186.33.99#53

Non-authoritative answer:
www.stefan1200.de canonical name = stefan1200.de.
Name: stefan1200.de
Address: 136.243.108.70


Also everything else (curl, apt-get etc) on the system is working.

DNS is working; using curl I can connect and download the page at https://www.stefan1200.de just fine.

Hosting Edition.
The webui seems unable to connect to the telnet server:

Code Select Expand

Reached no service on that IP address / port! Make sure that the JTS3ServerMod process is running and the telnet_enable and telnet_run_forever settings at the JTS3ServerMod_InstanceManager.cfg are enabled!

This is my config file:

Code Select Expand


# JTS3ServerMod Instance Manager config file
#
# This file must be saved with the encoding ISO-8859-1!

# A comma seperated list (without spaces) of unique user ids,
# which should be able to use bot full admin commands on all bot instances.
# Bot full admin can also see the TS3 server password and is able to use the !exec command.
# The unique user ids looks like this: mBbHRXwDAG7R19Rv3PorhMwbZW4=
bot_fulladmin_list =
# Allow !exec and !execwait commands for bot full admins? 1 = Yes, 0 = No
# This allow you to execute system commands.
# Only use !execwait for commands which quits within some seconds,
# because the bot waits for the end of this command to send you the text output of the program.
# Use !exec for commands with a longer runtime instead,
# this command don't send you any text output, because the bot don't wait for it.
bot_command_exec = 0
# Every time a bot full admin connects to the TS3 server it will be checked if an update for the JTS3ServerMod is available.
# If an update is available, a chat message will be sent to the bot full admin.
# 0 = disable, 1 = final versions, 2 = final and test versions
bot_update_check = 0
# The own personal licence key.
# Read the instructions, to know how to get one, at the download page of the JTS3ServerMod Hosting Edition.
bot_licence_key = <redacted>
# Add a small delay in milliseconds to the bot starting process.
# Only change this value if you have problems starting all bots at once, like hanging bot threads.
delay_bot_start = 100

# Enable the multi IP mode. 1 = Enable, 0 = Disable
# If slow mode is activated, this feature split bot connections to the Teamspeak 3 servers.
# Events (Chat and some functions) and the Client Database Cache gets an own connection which should solve the IP ban problem.
multiipmode_enable = 0
# Local IP Address of the main connection, make sure that this is not the same as for chat and cache!
multiipmode_ip_main = 123.123.123.123
# Local IP Address of the chat connection, make sure that this is not the same as for main and cache!
multiipmode_ip_chat = 124.124.124.124
# Local IP Address of the cache connection, make sure that this is not the same as for chat and main!
multiipmode_ip_cache = 125.125.125.125
# First local port
multiipmode_portrange_min = 50000
# Last local port
# Make sure, that you have at least 3 ports for every bot, which use the slow mode!
multiipmode_portrange_max = 51999

# Enable the Query Interface of the JTS3ServerMod. 1 = Enable, 0 = Disable
# You are able to start, stop or reload a virtual bot instance using this Query Interface.
telnet_enable = 1
# Choose a port for the Query Interface, default port is 5873.
telnet_port = 5873
# Choose a password for the Query Interface.
# If this password is shorter than 6 characters, the Query Interface will be disabled!
telnet_password = <redacted>
# Choose a network interface for the Query Interface. Only set a single ip address of a local network interface here.
# Set nothing here to bound the Query Interface to all network interfaces (default).
# Example: Set to 127.0.0.1 (IPv4) or ::1 (IPv6) to allow connections only from localhost.
telnet_bindTo = 127.0.0.1
# A comma seperated list (without spaces) of IP addresses, which are allowed to connect to the Query Interface.
# Leave empty, if every IP address is allowed to connect.
telnet_whitelist = 127.0.0.1
# Log query connection attempts to logfile? 1 = Enable, 0 = Disable
telnet_connection_log = 1
# Enable this to prevent that the JTS3ServerMod process quits if no bot instances are running. 1 = Enable, 0 = Disable
# You can still quit the process with !botquit in TS3 client chat or with botquit on the Query Interface.
telnet_run_forever = 1

# Use a MySQL database to save bot instances and configurations. 1 = Enable, 0 = Disable
# There should be a structure sql file in the documents directory.
# Import this into your MySQL database to create the tables (the included web interface do this already for you).
# But you must fill this tables by yourself, the bot just reads the information out there.
mysql_enable = 1
mysql_host = 127.0.0.1
mysql_port = 3306
mysql_user = root
mysql_password = <redacted>
mysql_database = jts3

# Optional MySQL settings, more information on https://dev.mysql.com/doc/connector-j/5.1/en/connector-j-reference-configuration-properties.html#connector-j-reference-set-config
# Possible values: -1 = default, 0 = disable, 1 = enable
mysql_verifyServerCertificate = -1
mysql_useSSL = -1
mysql_requireSSL = -1
mysql_useCompression = -1

# Normal log entries older than X days will be deleted from MySQL jts3servermod_log table. 0 = disable auto delete!
mysql_log_delete = 0
# Connection log entries older than X days will be deleted from MySQL jts3servermod_log table. 0 = disable auto delete!
mysql_connection_log_delete = 0


Log:

Code Select Expand


2017-05-18 19:49:48 START_MANAGER JTS3ServerMod 6.4.0 Hosting Edition (24.03.2017) Instance Manager started...
2017-05-18 19:49:48 CONFIG Loading InstanceManager config file from: /opt/jts3/config/JTS3ServerMod_InstanceManager.cfg
2017-05-18 19:49:48 CONFIG Bot chat command !exec is disabled!
2017-05-18 19:49:48 CONFIG Multi IP Mode disabled!
2017-05-18 19:49:48 LOGGER_SQL_CONNECT Successfully connected to MySQL server for logging!
2017-05-18 19:49:48 CONFIG MySQL mode enabled!


Using netstat I noticed port 5873 is not being used at all even though JTS3ServerMod is running.
Also in the license management page it says "Licence Key currently not used!" even though the program is started.