-
Notifications
You must be signed in to change notification settings - Fork 58
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
Can no access qbit webui #80
Comments
If you're trying to access it from the local LAN, you'll need to set the Also |
I am not trying to access it from local LAN. It is installed in a remote server. I want to accesss it using using its wan ip:webui port |
Accessing it directly via wan might be a bit more fiddly. As the vpn container can still communicate with other containers attached to the same Docker network, a reverse proxy might be the way to go. Something like this should work, though bear in mind the port is being exposed to the internet without any kind of encryption. Note that the port is exposed on the
Something like Traefik or nginx-proxy-manager might be a better option, though would need more setting up. |
Thanks a lot for your time. your final compose worked flawlessly. I can now access the webui. I want to know one more thing, Port used for incoming connections: 6881 , Ideally we want this port to be open so other peers can connect with me. Thats why I exposed that port without knowing how all these things work. But now Im using your final docker-compose file and I used some sites to check if the port is open but showing its not. |
I think 6881 is the default port used by Bittorrent, so if you're sticking with the defaults and using it on a normal connection, then port 6881 would need forwarding to the container via docker. When using it through a vpn though, everything goes through the tunnel instead, so forwarding ports using docker isn't needed. 6881 wouldn't work with PIA anyway, as you don't get any choice of which port number gets used for forwarding. It looks like you've got things working now though. If you're reading the port manually from the log and entering it into qbittorrent, it might be worth setting |
Issue Solved
|
Thanks for sharing! |
@Sparklingx What's in your |
everythign is working and healthy but cant access webui! checked log . no error
compose file
The text was updated successfully, but these errors were encountered: