OpenVPN-Client is running normally, per its logs and ifconfig.me. The vpn.ovpn and vpn.auth files are working properly.

In the Extra Parameters field of Deluge template I have added: –net=container:OpenVPN-Client

In OpenVPN-Client template:

 - Network Type is set to None
 - I have added a port record: Host Port 8112 and Container Port 6881

Deluge’s WebUI won’t load at all. I tried qBittorrent instead, using the same approach as above, and it won’t load the WebUI either.

    • ChrisLichtOPEnglish
      1·
      6 months ago

      That was very helpful, thanks!

      Only problem I have left is getting NGINX Reverse Proxy Manager set up, so that I can offer Overseerr webpage. The Let’s Encrypt cert generator keeps throwing an internal error at the last step. Something is preventing LE from reaching my server, and I’m too clueless to solve at this point.

      • gazoinksboe@lemmy.worldEnglish
        1·
        6 months ago

        Do you have Nginx on the same bridge as Overseerr? If you have multiple docker networks, they need to be on the same so they can discover one another. That bridge also needs internet access so you can generate the cert. Hope this helps

        • ChrisLichtOPEnglish
          1·
          6 months ago

          NGINX seemed to automatically grab br0. Overseerr is routed through OpenVPN-Client, as are all the other -arr apps. The -arr apps are all talking to each other well.

          Thanks for thinking about my setup! I’m playing just beyond the limit of my networking skills and stumbling around a bit on this reverse proxy thing.

  • chesh@lemmy.worldEnglish
    1·
    6 months ago

    Do you have a LAN_NETWORK variable with your local LAN identified in CIDR?

    192.168.1.0/24 Container Variable: LAN_NETWORK