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

TCP / UDP port number reverts to 6881 after any settings change #10886

Closed
connect-dots opened this issue Jul 4, 2019 · 2 comments

Comments

Projects
None yet
2 participants
@connect-dots
Copy link

commented Jul 4, 2019

Please provide the following information

qBittorrent version and Operating System

4.1.6, Ubuntu 18.04

If on linux, libtorrent and Qt version

lib 1.1.9

What is the problem

TCP / UDP port always shows 6881, even after change.
TCP / UDP port reverts back to 6881 after any settings change is saved.

What is the expected behavior

Correct port should be shown if changed from 6881. New port should be persistent.

Steps to reproduce

Open Settings.
Change port number to anything (54321).
Save.
Go back into settings.
Port will still show 6881.
At this point the port is changed. Trackers will report connection on 54321 if seeding or downloading.
Open settings and change another value, i.e. Force Encryption
Save.
Now any newly added torrent(s) will now report connections on 6881.

Extra info(if any)

Torrents added when port is effectively changed will remain on 54321 (for example). Any newly added torrents will revert to 6881.

Have been using a linuxserver docker image of 4.1.6, but the same behaviour is observed when running 4.1.6 install direct to the OS from the qb ppa

@Kolcha

This comment has been minimized.

Copy link
Contributor

commented Jul 5, 2019

looks like qBittorrent unable to save settings...
did you run qbittorrent as root (using sudo)? if so, just delete (with sudo) configuration files at ~/.config/qBittorrent and try again

@connect-dots

This comment has been minimized.

Copy link
Author

commented Jul 15, 2019

After a lot of testing, it seems the bug is in Chrome / Chromium (Windows & Linux - tested on separate machines). The ports are correctly displayed in Firefox / Opera.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.