Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

qbittorrent - all ports show closed except the webui

Featured Replies

The docker specific help links over to github, which is fine, but it isn't unraid CA docker specific stuff.

qbittorrent docker settings has several ports as part of it (I'm on Repository lscr.io/linuxserver/qbittorrent:5.0.3)

webui: 6881

port 6881 TCP: 6881

port 6881 UDP: 22000

webui port: 8083

torrening port: 58846

 

I think (?) that the port specified on the Docker Settings aren't being opened, or for some reason just aren't getting through. I want that 58846 to be open so I can forward that port only through the router. Right?

 

Checking on my local network via Windows Powershell:

PS C:\Users\me> Test-NetConnection -ComputerName 192.168.11.2 -Port 8083                                                                                                                                                                                                                       ComputerName     : 192.168.11.2
RemoteAddress    : 192.168.11.2
RemotePort       : 8083
InterfaceAlias   : Ethernet
SourceAddress    : 192.168.11.25
TcpTestSucceeded : True



PS C:\Users\me> Test-NetConnection -ComputerName 192.168.11.2 -Port 58846
WARNING: TCP connect to (192.168.11.2 : 58846) failed


ComputerName           : 192.168.11.2
RemoteAddress          : 192.168.11.2
RemotePort             : 58846
InterfaceAlias         : Ethernet
SourceAddress          : 192.168.11.25
PingSucceeded          : True
PingReplyDetails (RTT) : 0 ms
TcpTestSucceeded       : False

 

  • Author

I figured this out (me and chatgpt). qbittorrent was running in Network type: Host, I changed that to Bridge. Which apparently gives more control over ports. Then I had to re-add the specific port I wanted in the Docker template for qbittorrent, both tcp and udp, to entries. That brought a good response back from windows powershell command:

PS C:\Users\drew> Test-NetConnection -ComputerName 192.168.11.2 -Port 58846
ComputerName     : 192.168.11.2
RemoteAddress    : 192.168.11.2
RemotePort       : 58846
InterfaceAlias   : Ethernet
SourceAddress    : 192.168.11.25
TcpTestSucceeded : True

 

Now canyouseeme.org 58846 returns a success. Geees, this has been broken for months. derp.

Edited by rutherford

  • Author

Also, when I did those changes, I lost the webgui. It's like the

  -e 'WEBUI_PORT'='8083' (this was from docker success run page where we briefly see the docker command details)

was doign nothing, and I had to readd the port below

  -p '8083:8083/tcp'

 

<shrug> works now; webgui and torrenting port. Totally weird.

Edited by rutherford

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.