IwishIcanFLighT

Members
  • Posts

    15
  • Joined

Everything posted by IwishIcanFLighT

  1. This is obviously super late to the party but I came across the exact same issue (locked out of my own TS server admin group after formatting my PC and no way to find the ServerQuery password). Recreating the entire server configuration and channels was not an option, so I found a solution on my own and thought I'd share it here in case someone needs it later. a) How to reset the ServerQuery password From your unraid SSH terminal, enter your running teamspeak container: docker exec -it <teamspeak container ID> bash Open with a text editor the file ~/start.sh . I use nano as it's available in this container: nano ~/start.sh Find the "# run teamspeak server" line, it was at the bottom of mine and looked like this: cd "${install_path}/sql/" && /usr/bin/ts3server logpath=/config/ dbsqlpath=/usr/share/teamspeak3-server/sql/ licensepath=/config/ license_accepted=1 Modify the line by adding "serveradmin_password=YourNewPassword". It should look like this: cd "${install_path}/sql/" && /usr/bin/ts3server logpath=/config/ dbsqlpath=/usr/share/teamspeak3-server/sql/ licensepath=/config/ license_accepted=1 serveradmin_password=<New serveradmin Password Here> Save the file, exit the container and restart it from the Unraid Dashboard. Save your new serveradmin password somewhere safe (e.g. password manager) for future usage, skipping this step. b) How to create a new privilege key via ServerQuery Connect to your TS server with a regular client. Go to Permissions > Servergroups. Memorize the number in parentheses behind the server group you want to recover. Usually Server Admin is ID 6. Connect via telnet to the ServerQuery. I use Kitty but you can use Putty or anything else: IP: your Unraid Server IP Port: 10011 Upon connecting, you should see the following text. If not, you probably used the wrong port: TS3 Welcome to the TeamSpeak 3 ServerQuery interface, type "help" for a list of commands and "help <command>" for information on a specific command. Type login serveradmin <New serveradmin Password Here> and press Enter. The server should respond error id=0 msg=ok Type use port=<The port you used to connect using the TS3 Client, usually 9987> and press Enter. The server should respond error id=0 msg=ok Type privilegekeyadd tokentype=0 tokenid1=<The Number you memorized in step 1> tokenid2=0 and press Enter. The server should respond: token=YourNewTokenReadyToBeUSed error id=0 msg=ok Return to your TS client, Go to Permissions > Use Privilege Key and paste the token in the input box. Go back to the ~/start.sh file modified in step a) and remove the serveradmin_password=<New serveradmin Password Here> argument as it's not needed anymore. Note that the new serveradmin password will still work, the argument resets it at each restart of the server. Done. 😉 c) Optional but recommended: remove your old TS credentials If you completely lost your previous credentials, there's no need to keep them on your server. You can remove them: Go to Permissions > Server Groups Select the admin group On the right side of the window there's a list of all the users in that group. Find your old account and remove it. If the username are similar, you can temporally change your current username and refresh the list to distinguish them.
  2. That did the trick! However the pull seemed to timeout from the Dashboard so I had to manually pull from the terminal then trigger the update from the Dashboard. Thanks a lot!
  3. Hi! I was updating my Teamspeak image from 3.11.1 to 3.12.1 today. However, the update says it when fine pulling latest but it actually didn't update the server at all. I managed to force update to 3.12.1 by forcing the repository address to "binhex/arch-teamspeak:3.12.1-1-01", but as soon as I replace it to "binhex/arch-teamspeak" it rolls back to pulling "latest" 3.11.1. And while I could leave the force 3.12 address repository, it's not ideal because the check for update won't find future versions. Any help is welcomed, thanks!
  4. Can confirm this is still happening for me as well after updating to 6.8.2.
  5. Hum that's unfortunate. I guess I'll stick to the older version of the docker image. At least until my vpn subscription is over. Then I'll probably move on. Thanks for your help anyway! I really appreciate.
  6. Alright I had to remove --deamon from the args in order to have the logs. We seems to have a fatal error indeed. I might be wrong but it looks like there's an issue with tun0. See attached log file. outputlog.txt
  7. Oh yeah that's correct I renamed the file when I installed the latest working version. But its content remains the same.
  8. Here's the output: Disabling script-security and redirect-gateway didn't help by the way.
  9. Okay so this morning I deleted everything and started from scratch. Pulled the latest version but I'm still unable to connect. However, I deleted everything once more and force pulled an older version of your repo, v1.3.13-31. And voila, deluge is back up with the exact same ovpn and template configurations. For now I'm good if I don't update, but I don't like the idea of not updating my server services, especially when it comes to security stuff like a VPN. I'm gonna dig into redirect-gateway and script-security later today, but I'm starting to wonder if the changes you made since 1.3.13-32 might crumple a bit my VPN provider. Do you remember if one of your modifications over the last updates could lead into client/server disagreement? Thanks
  10. Yeah I'm using Notepad++ and just double checked: the file is Unix (LF). I also tried to save it with vim via a ssh. Here's the ovpn file by the way:
  11. I already did that and just tried once more. I'm still unable to access deluge UI. Don't know if that's related, but when I download the ovpn file from my provider, I have to comment these lines: Otherwise I get this error: But this modification was working prior to today's update, so I don't think that's the issue.
  12. Thanks for the answer. This time the start script seems to be run once: However I still can't reach the webUI (and Sonarr can't ping deluge as well). My vpn provider only logs one connection though: 2 minutes long, 7,4 Kio up / 2,6 Kio down. It's running on a core i5 750 with 16Gb of ram. Not brand new, but still somewhat capable.
  13. Hi there! I updated my delugevpn this morning and I can't reach the webGUI. Logs: As you can see, OpenVPN restarts every 20 seconds or so. What I don't understand is that my VPN provider logs does receive these "successful" connections They last 2 minutes each: 7,4 Kio up / 2,6 Kio down. I tried removing the delugevpn image pulling it again. I also tried with a brand new config file from my vpn provider. But no success so far... Any help is welcome!
  14. Hi there My teamspeak container wouldn't launch the server lately. The logs saying the following: 2015-12-27 17:25:23.437401|INFO |VirtualServer | 1| listening on 0.0.0.0:9987 2015-12-30 11:12:36.702394|INFO |VirtualServerBase| 1| stopped 2015-12-27 17:25:22.208427|INFO |DatabaseQuery | | dbPlugin name: SQLite3 plugin, Version 2, (c)TeamSpeak Systems GmbH 2015-12-27 17:25:22.208689|INFO |DatabaseQuery | | dbPlugin version: 3.6.21 2015-12-27 17:25:22.209416|INFO |DatabaseQuery | | checking database integrity (may take a while) 2015-12-27 17:25:22.240732|WARNING |Accounting | | Unable to find valid license key, falling back to limited functionality 2015-12-27 17:25:23.377622|INFO | | | Puzzle precompute time: 617 2015-12-27 17:25:23.378317|INFO |FileManager | | listening on 0.0.0.0:30033 2015-12-27 17:25:23.439342|INFO |CIDRManager | | updated query_ip_whitelist ips: 127.0.0.1, 2015-12-27 17:25:23.440321|INFO |Query | | listening on 0.0.0.0:10011 2015-12-30 01:00:52.038882|ERROR | | | TS3ANetwork::ResolveHostName failed error: -2 (Name or service not known) 0 2015-12-30 11:12:36.651294|INFO |ServerMain | | Received signal SIGTERM, shutting down. [K[[0;31m FAIL [0m] Starting ts3-server: Tmux not installed * Tmux is required to run this server. * Please see the the following link. * http://gameservermanagers.com/tmux-not-found The linked documentation at http://gameservermanagers.com/tmux-not-found instructed me to install Tmux by doing a apt-get install tmux. I did it within the container (using docker exec -it) and my teamspeak server is now back up. I thought I'd mention that because as far as I understand Docker (new user as you would guess), next time the container gets updated Tmux will be gone, right? Thanks