Jump to content

IwishIcanFLighT

Members
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About IwishIcanFLighT

  • Rank
    Member

Converted

  • Gender
    Undisclosed
  1. 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.
  2. 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
  3. Oh yeah that's correct I renamed the file when I installed the latest working version. But its content remains the same.
  4. Here's the output: Disabling script-security and redirect-gateway didn't help by the way.
  5. 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
  6. 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:
  7. 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.
  8. 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.
  9. 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!
  10. 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