Not able to access Deluge Daemon through Remote Connections

Support
1

Not able to access Deluge Daemon through Remote Connections.

  1. accessing /deluge from /plinth over http/https on local network can see running daemon
  2. Allow Remote Connections checkbox is checked at Preferences > Daemon
  3. but can’t access over the external IP/domain

image

  1. Can’t connect to the daemon from the same local network using any application

image

  1. Port forwarding is enabled for the IP (…185:58846)

Problem Description
Not able to access Deluge Daemon through Remote Connections.

Diagnostic Results
App: Deluge

Test Result
Package deluged is the latest version (2.0.3-3.1) passed
Package deluge-web is the latest version (2.0.3-3.1) passed
Port http (80/tcp) available for internal networks passed
Port http (80/tcp) available for external networks passed
Port https (443/tcp) available for internal networks passed
Port https (443/tcp) available for external networks passed
Access URL https_127.0.0.1/deluge on tcp4 passed
Access URL https_[::1]/deluge on tcp6 passed
Access URL https_192.168.0.185/deluge on tcp4 passed
Access URL https_[fe80:::906c%enxb827eb2abc7a]/deluge on tcp6 passed
Access URL https_10._.1/deluge on tcp4 passed
Access URL https_[fe80:::6d32%wg0]/deluge on tcp6 passed
Access URL https_localhost/deluge on tcp4 passed
Access URL https_localhost/deluge on tcp6 passed
Access URL https_kincse/deluge on tcp4 passed
Service deluged is running passed
Listening on tcp4 port 58846 passed
Service deluge-web is running passed
Listening on tcp4 port 8112 passed

Information

  • You are running Debian GNU/Linux 11 (bullseye) and FreedomBox version 22.26. FreedomBox is up to date.

  • CPU 4x ARMv7 Processor rev 5 (v7l)

2

Do you have separate zones setup? External reaching only outside the network and internal for inside?

In FreedomBox Settings: Does the firewall page show Deluge rule is enabled?
In Cockpit: Does the port show in the rule set for the correct zones?