You can edit the .sqlite file that stores the database to change settings like ports. You can also connect to the telnet port locally and change settings while the server is running.
@chocolateshirt said: If you are unable to change TS3 port to match your NAT port then use iptables port forwarding.
I never thought of this. This appears to be the simplest solution, thanks.
@pike said: You can edit the .sqlite file that stores the database to change settings like ports. You can also connect to the telnet port locally and change settings while the server is running.
So TS3 is no longer reading the .ini file even when using the "inifile=" argument? None of the changes I made to that configuration file are having an impact.
@Privacy I cannot comment on that. I remember that either the startscript or minimal_runscript has a line that you can edit to feed commandline options to the server (which I used to change the serveradmin password). However, using telnet is the best practice to change any settings/create more virtual servers.
@pike said: cannot comment on that. I remember that either the startscript or minimal_runscript has a line that you can edit to feed commandline options to the server (which I used to change the serveradmin password). However, using telnet is the best practice to change any settings/create more virtual servers.
edit: its startscript
Looks like I'll use Telnet to fix it. It appears that TS3 no longer accepts the ts3server.ini configuration file, at least from my testing.
@bsh said: I found the reason you look for NAT KVM VPS. TeamSpeak behind NAT?
It's not my only use, but I do prefer KVM over OpenVZ. I prefer to have control over the kernel for security purposes and for the more standardized installation of WireGuard.
Comments
If you are unable to change TS3 port to match your NAT port then use iptables port forwarding.
You can edit the .sqlite file that stores the database to change settings like ports. You can also connect to the telnet port locally and change settings while the server is running.
I never thought of this. This appears to be the simplest solution, thanks.
So TS3 is no longer reading the .ini file even when using the "inifile=" argument? None of the changes I made to that configuration file are having an impact.
@Privacy I cannot comment on that. I remember that either the startscript or minimal_runscript has a line that you can edit to feed commandline options to the server (which I used to change the serveradmin password). However, using telnet is the best practice to change any settings/create more virtual servers.
edit: its startscript
I remember using this script years back for TS3 NAT setup. Maybe try that one?
https://github.com/bosscoder/NAT-TS3-Installer
Looks like I'll use Telnet to fix it. It appears that TS3 no longer accepts the ts3server.ini configuration file, at least from my testing.
Anyone else running TS3 on a NAT box willing to share how they set it up?
I found the reason you look for NAT KVM VPS. TeamSpeak behind NAT?
It's not my only use, but I do prefer KVM over OpenVZ. I prefer to have control over the kernel for security purposes and for the more standardized installation of WireGuard.
You could also use docker. Portforwarding is pretty straight forward in docker.