Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to connect containers with ports (e.g. lscr.io/linuxserver/qbittorrent) #78

Open
bhups2k opened this issue Apr 9, 2022 · 1 comment

Comments

@bhups2k
Copy link

bhups2k commented Apr 9, 2022

I'm trying to set up lscr.io/linuxserver/qbittorrent to connect to nordvpn-proxy, but it is not possible due to the ports used on lscr.io/linuxserver/qbittorrent.

How can one set this up so we are able to use such containers via nordvpn-proxy?

I can only get lscr.io/linuxserver/qbittorrent to run if I remove the ports from the config, but then its no use as I cannot access the portal.

I'm only using lscr.io/linuxserver/qbittorrent as an example. There are many others which use a similar set up.

Thanks

@declan-wade
Copy link

Having this issue too - it has been working for serveral months and has now fallen over. I have both nordvpn_proxy and lscr.io/linuxserver/qbittorrent on the same bridge network (not the default bridge, but a custom 'named' bridge so I can resolve by hostname) but pinging the contianer name comes back with 'bad address'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants