Working proxy setup to remotely access a dependent container's WebUI? #175
Legomaniac
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have this nordlynx container setup and working with my deluge container to route it's traffic via NordVPN, yet allow the Deluge WebUI and server API to be accessible within my local network. Here is the relevant snippet of my docker compose file:
I can access the Deluge WebUI (port 8112) and server API (port 58846, for use with the Trireme Android app) from my local network just fine, the NET_LOCAL variable works as I would expect.
However, I have a DNS entry that is dynamically updated by a DDNS client that points to my home's IP address. I would like to be able to access the Deluge WebUI and API without updating the NET_LOCAL variable from every possible IP address I may want to access from (this sounds really tedious).
For now I have just added the CIDR ranges for Verizon Wireless to my NET_LOCAL (
NET_LOCAL=192.168.1.0/24,174.192.0.0/10,75.192.0.0/10,75.96.0.0/11
). This works fine if I'm on my phone's 5G connection, but if I'm on somebody else's WiFi, I'll need to update the NET_LOCAL variable before I can use the Android app to interact with the Deluge server.I have seen mention of setting up a proxy to forward traffic to get this to work. @Gunther-Shulz made a post here: #105 (reply in thread)
However, I have struggled to do this successfully.
I have tried using the traefik example from here: https://github.com/bubuntux/nordvpn to no avail.
I'm hoping someone has gotten this working or can point me in the right direction to someone that has. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions