When Deluge
is run on a system running the Microsoft Windows operating system,
it stores the location it uses for the incoming port number(s) in
a configuration file, core.conf
under the user's %APPDATA%\deluge
directory. The %APPDATA% environment variable usually
expands to something like the following, where YourUserName
is the user name for the relevant Windows account:
C:\Users\YourUsername\AppData\Roaming\deluge\core.conf
Note: You can see the value for %APPDATA%
by issuing the command echo %APPDATA%
in a command prompt window.
The %APPDATA% directory is a hidden
directory, but you can see the contents of the Deluge configuration directory
in the Windows
file manager even if you haven't turned on the display of hidden folders by putting %APPDATA%\deluge in the address field in
the file manager. You can then right-click on the file and choose to open
it with the Windows Notepad. You can also access the directory by pressing
the Win + R
keys.
By default, Deluge uses a random network port or the 6881-6889 range (frequently defaulting to 6881 in many setups like Docker). You can check or change the exact active incoming port when Deluge is running under Preferences → Network. If you open the configuration file in a text editor, such as Windows Notepad, you will see something similar to the following:
"listen_ports": [6881, 6891], "random_port": false
- listen_ports — The incoming port range. If both numbers are the same, Deluge uses a single configured port.
- random_port — If true, Deluge selects a port randomly at startup; the configured range may not reflect the active port. If false, it uses the configured listen_ports range.
If you need to change the port before starting Deluge, e.g., to match an incoming port provided by a VPN provider, you can change the values. E.g., if you wanted Deluge to use port 39755, you could put the following entries in the file and then start Deluge:
"listen_ports": [
39755,
39755
],
"listen_random_port": null,
"listen_reuse_port": true,
Note: If you need the actual port Deluge is listening on right now, rather than its saved setting, check Deluge's Preferences → Network → Incoming Ports. With random port selection enabled, the active port can differ from the saved value if you haven't restarted Deluge after updating the port number.
When you start Deluge, you can see if there are incoming connections to that port using the netstat command. E.g., netstat -an | find "39755".
C:\Users\Jill>netstat -an | find "39755" TCP 10.164.7.152:39755 0.0.0.0:0 LISTENING TCP 10.164.7.152:39755 10.43.22.249:64621 TIME_WAIT TCP 10.164.7.152:39755 10.157.104.168:49659 TIME_WAIT TCP 10.164.7.152:39755 10.157.104.168:57171 TIME_WAIT TCP 10.164.7.152:39755 10.169.234.135:49738 TIME_WAIT TCP 10.164.7.152:39755 10.169.234.135:55102 TIME_WAIT TCP 10.164.7.152:39755 10.175.210.63:50713 TIME_WAIT TCP 10.164.7.152:39755 10.194.155.52:14534 SYN_RECEIVED TCP 10.164.7.152:54686 178.93.201.240:39755 SYN_SENT TCP 127.0.0.1:39755 0.0.0.0:0 LISTENING TCP 192.168.1.7:39755 0.0.0.0:0 LISTENING UDP 10.162.7.159:39755 *:* UDP 127.0.0.1:39755 *:* UDP 192.168.1.7:39755 *:* C:\Users\Jill>
References:
