August 5, 20232 yr Hi all, I have a weird issue around qbit port that I cant wrap my head around: A private tracker requires me to have a different port in the client besides the known torrent port (6881). Therefore, I changed the port in the webgui of qbit as well as in the docker container settings to 50123. Problem is that Im not considered connectable with that setting. I only get connectable if I change the port setting in the webgui of qbit back to standard (6881) so it matches the host port shown for the docker image. Then portforwaring works and Im also connectable. But if I do that, than my private tracker complains that the port is not allowed and blocks traffic (because it sees the internal qbit port (6881) instead of the external port 50123. How can I work around this? Is it possible to change the internal host port of qbittorent docker (see picture attached)? Can I avoid that qbit is sending the port info?
August 5, 20232 yr Take a look in the support thread for the specific container that you are running, there should be FAQ or documentation explaining it, if not, ask the question in that thread.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.