no connection when hosting in cpanel

[Fernando]

I'm having this problem when I host jts3servermod in cpanel







only works when I install within vps

[Stefan1200]

More information please. What problem you have?

[Fernando]

my jts3servermod is not having connection to my cpanel site is giving this red error down there, only that when I install it in a vps it goes normal

[Fernando]

Code Select Expand

2019-02-07 14:42:20 START_MANAGER JTS3ServerMod 6.5.4 Hosting Edition (05.01.2019) Instance Manager started...
2019-02-07 14:42:20 SYSTEM_INFO Operating System : Linux (version: 4.4.0-141-generic / arch: amd64)
2019-02-07 14:42:20 SYSTEM_INFO Used Java Version: 1.8.0_201 (path: /usr/lib/jvm/java-8-oracle/jre)
2019-02-07 14:42:20 SYSTEM_INFO Current directory: /root/boot
2019-02-07 14:42:20 CONFIG Loading InstanceManager config file from: /root/boot/config/JTS3ServerMod_InstanceManager.cfg
2019-02-07 14:42:20 CONFIG Bot chat command !exec is disabled!
2019-02-07 14:42:20 CONFIG Multi IP Mode disabled!
2019-02-07 14:42:21 LOGGER_SQL_CONNECT Successfully connected to MySQL server for logging!
2019-02-07 14:42:21 CONFIG MySQL mode enabled!
2019-02-07 14:42:25 LICENCE_CHECK Licence key is valid! Thank you very much for your support, Fernando!
2019-02-07 14:42:25 TELNET_START Query Interface started on port 5873!


[Stefan1200]

This log looks perfect. Please send me a screenshot of the Web Interface / Settings / Query Interface page.

[Fernando]

This log looks perfect. Please send me a screenshot of the Web Interface / Settings / Query Interface page.

[Stefan1200]

Okay, how are the JTS3ServerMod_InstanceManager.cfg telnet_whitelist settings? Are you sure, that the firewall allows a direct tcp connection from the web interface to the JTS3ServerMod?

[Fernando]

my hosting company

only releases port 5873

just to leave the hosting will the problem is that?

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 = I WILL PASS THE PASSWORD
# 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 = 108.167.168.49
# Local IP Address of the chat connection, make sure that this is not the same as for main and cache!
multiipmode_ip_chat = 108.167.168.49
# Local IP Address of the cache connection, make sure that this is not the same as for chat and main!
multiipmode_ip_cache = 108.167.168.49
# 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 = I WILL PASS THE PASSWORD
# 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 =
# 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 = 108.167.168.49
# 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 = 108.167.168.49
mysql_port = 3306
mysql_user = shooterd_boot
mysql_password =  I WILL PASS THE PASSWORD
mysql_database = shooterd_boot

# 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

# Passphrase for the encryption of TS3 server query passwords.
# This key has to be the same as in the PHP PWCrypt class.
# Leave it empty to disable encrypting and decrypting query passwords.
# If the passphrase will be changed after some passwords was encrypted,
# it is not possible to decrypt the encrypted passwords again.
crypt_key =


[Stefan1200]

Since telnet_connection_log is set to 1, you should see connection attempts in the JTS3ServerMod_InstanceManager.log. If that is not the case, like in the log above, the TCP connection from the Web Interface never reach the JTS3ServerMod process. So I guess the firewall of the Web Interface server or the JTS3ServerMod server blocks this connection attempt.