Bungy

Community Developer
  • Content Count

    373
  • Joined

  • Last visited

Community Reputation

13 Good

1 Follower

About Bungy

  • Rank
    Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. I see - So your sonarr/lidarr/etc are using the http_proxy and no_proxy environmental variables to get VPN access into them. Have you tried setting your no_proxy env variable to 192.168.1.71 and then in sonarr set your nzbget server to be 192.168.1.71:6789? Alternatively, if you have local DNS, you can set your no_proxy to something like: no_proxy: *.local,192.168.1.71 I'm using internal DNS to get a ".kube" domain address and then telling it not to use the proxy for all *.kube lookups.
  2. Can you confirm your LAN network is in fact 192.168.1.0/24? What's the IP address on the machine you're currently using? You can try to set the LAN_NETWORK to 0.0.0.0/0 and confirm that the traffic isn't being blocked. That'll verify that the issue is with your setting of that environmental variable. Then you'll need to figure out your docker network address + subnet and include that in the LAN_NETWORK variable. Here is what mine looks like but I have multiple networks and run my containers on a kubernetes cluster, so yours will likely need to differ as well: 192.168.1.0/24,192
  3. Make sure your LAN_NETWORK environmental variable is set properly to allow access from your sonarr/radarr/lidarr ip address. I have mine set to handle local network traffic as well as docker network traffic. You can set it to 0.0.0.0/0 to allow all inwards traffic, but that's not recommended.
  4. Shoot me a DM with your config info and I'll see if I can find the issue.
  5. Check your config and environmental variables that should be set compared to whats in the PIA section on the github page here: https://github.com/jshridha/docker-nzbgetvpn The unraid template is probably outdated. I haven't updated that thing in years especially since I'm not running linux containers on unraid anymore.
  6. Glad it's working well for you! I too am getting 3x the openvpn speed, so thanks for pushing me to get that done. I'm also glad you were able to resurrect your server and are recovering down in TX.
  7. It's live now. You can either use the latest tag or the v21.0-3 tag
  8. Done! The builds will be hitting docker hub in the next 15 minutes. Enjoy!
  9. Not that I know of. Containers generally run under the host's network stack. They don't work like virtual machines where each machine can have its own ip address.
  10. Set the network type back to the default. Then you should be able to connect to it using the host unraid system's ip address and port 3306
  11. Yep that's right. Glad you figured it out.
  12. Yeah, it works the same way. Just set VPN_ENABLED=<yes|no>
  13. Interesting. If people are finding my docker semi-useful, I'll have to devote some time into making it work better and more seamlessly. I'll pick this project back up and continue developing on it. Pull requests are always welcome!
  14. I'm planning on adding it to the container, but I have not yet. You're better off adding it to the container directly Sent from my SM-N950U using Tapatalk