• Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

ainuke's Achievements


Rookie (2/14)



  1. New Topic: Is there an easy way to run speedtest through the GluetunVPN? Using LibreSpeed(linuxserver), if I use the "--network=container:GluetunVPN" parameter, the container fails to install with an error Error response from daemon: conflicting options: port publishing and the container type network mode I just picked this speed test docker on a whim; if there's a better way to speed test the vpn, I'd be happy to hear it. I'm currently getting <1Mb/s on NBZGet, which is waaaay down from where it was a month ago. Speed to the server minus VPN is 900Mb/s. Trying to track down what's changed...
  2. Sorry, that was my bad. I was looking too far up in the log; the http server error was from when it was shutting down. Everything is working now, although to get access to the containers' UI (NZBGet and Sonarr) on the LAN, their ports need to be manually specified/added. From the description, I thought that was the purpose of ADDIDIONAL_FIREWALL_INPUT_PORTS? Not really worried about it at this point, given that it's functional; just curious. Thanks for your help!
  3. I'm getting a "ERROR http server: http: Server closed" error when restarting Gluetun, with both the other containers stopped.
  4. Ok, did that, but now when I start sonarr or nzbget containers, I get "Execution Error No such container"
  5. Not sure if there's a better way to do this, but here goes: Everything is at default with the exception of ports added for nzbget and sonarr, plus login creds and server region. Thanks for the help!
  6. Hi, Having issues with GluetunVPN setup, specifically having Sonarr and NZBGet communicate with each other. I can access both UI fine from browser on the LAN, but Sonarr is throwing an "Error: ConnectFailure (No route to host): 'http://**.*.*.***:6789/jsonrpc'". I'm coming from a previous version of Gluetun Docker (not DPC), which was working fine, but with different parameter names. I've added ports 6789,8989 to "ADDITIONAL_FIREWALL_INPUT_PORTS" and added "--network=container:GluetunVPN" to Extra Parameters. I've also tried adding the ports via "add another path, port, variable, etc" as was needed with my previous iteration of Gluetun/PIA, to no avail. Is there something I need to do with "FIREWALL_OUTBOUND_SUBNETS"? TIA, Erik
  7. I have the same issue, except with PIA as a stand-alone VPN Docker. Haven’t tracked it down as it isn’t a big issue for me, but I’ve wondered if it’s an artifact of the tunneling. Although I didn’t have this issue when I was running VPN and NZBGet + ‘arrs on a standalone pi.
  8. Hmmmm, OK. In the "Wireguard" folder in AppData, the conf file shows "" for the endpoint, which is the server I'd have picked anyway... Is that static, or does it change when restarted? I don't recall ever setting that, but maybe I did. 😕
  9. OK, thanks. I'm running the Wireguard version. Is there a like setting for that?
  10. Is there a way to specify which PIA server to use? My firewall blocks many countries, and I've had connections issues with port forwarding inside this docker as a result. Would like to choose a server in the whitelist...
  11. Ok, I don’t know what I did differently, but it seems to be excluding the designated folders as expected now. 🤷🏼‍♂️ consider my issue solved
  12. Anyone have any thoughts on this?
  13. OK, I've got it sorted. I had to reclaim the server through the webui, but it didn't work before because I had the container in bridge mode, I think. I changed it back to host to claim the server, then restarted the container as bridge. Everything is fine, now.
  14. UPDATE: tried reverting to my old password. That didn't work and I'm now locked out of my PMS instance from both and webui.