-
Notifications
You must be signed in to change notification settings - Fork 52
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
Qbittorrent not updating port on container start #267
Comments
I think you need to manually change the port in qbittorrent to the correct one. The log sounds like it's going to automate this for you but I've never experienced it doing that. |
Oof. That's rough. How often are you finding that you have to manually update it? Curious if anyone else is having the issue. |
I've only had to update it when changing VPN config so not too often. |
Ah. Mine is getting a random port assigned from the VPN without any changes to the configuration which leads to me chasing it anytime the connection refreshes. |
@binhex - Sorry for the ping but any insights you can provide here would be greatly appreciated. Love the work! |
Hi all,
I've got an issue that I can't seem to figure out. The container starts fine and I can connect without issue. The problem is that even though it's being detected that the incoming port on the VPN is different than qBittorrent, it's not setting the port in the program once qBit launches. Below is the last snippet of the logs. Admittedly, I'm still a bit new to this, but I can't seem to figure it out. Any help would be greatly appreciated!
The text was updated successfully, but these errors were encountered: