DELUGE PORT ISSUE — RECONNECT CHECKLIST
Blank worksheet, not a live test or a guarantee of reachability.

1. RECORD THE RUNNING DAEMON
Deluge version / libtorrent version:
Host OS / container image and version:
Daemon location (local / NAS / remote):
Network path (ISP router / VPN / Docker + VPN):

2. MATCH THE PORT
Random incoming ports disabled:
Incoming range start / end:
Actual Active Port:
Local TCP listener and bind address:
Local UDP socket and bind address:
Firewall rule matches active port / profile:
Router or VPN public port:
VPN assigned port after reconnect:
Docker networking mode and TCP/UDP mappings:

3. VERIFY THE SAME ENDPOINT
Public IP of daemon route (not necessarily browser IP):
Built-in Test Active Port result / time:
Daemon log if the test service errors:
Independent external TCP test result / time:
UDP checked separately (method / result):
Incoming peer activity:
Healthy authorized torrent result:
If still stalled: tracker / queue / ratio / disk / permissions:

Do not publicly forward Web UI 8112 or daemon-control 58846
as a substitute for the incoming torrent port.
Retest after VPN reconnects and port changes.