Hi,
I have deluge deamon on my raspberry pi.
I have a server on the PC.
i get an error "Port Issue" i fwd the port on my router and verified it is open. i do not randomize the ports.
i set the incoming port to be the same as the port but it keeps changing when i restart deluge, why?
what can i do to fix the port issue.
the other issue is that both the web interface and the pc server are showing the downloaded torrents but the deluge on the pi shows nothing
Port Issue + no torrent shown on deluge gui
Re: Port Issue + no torrent shown on deluge gui
Hello janjan,
Could you maybe verify/post the settings in core.conf?
Do this command to see what settings are being used on the server where deluged (daemon) is running and post this here.
You will see something like this.
Also to see what ports deluge is listening on execute the next command.
After verifying that at least the settings of Deluge are correct, we can start looking at other things.
It will look something like this.
Could you maybe verify/post the settings in core.conf?
Do this command to see what settings are being used on the server where deluged (daemon) is running and post this here.
grep -E -A5 "listen_ports" core.conf && grep -E -A2 "outgoing_ports" core.confYou will see something like this.
Code: Select all
<user>@<system>:/var/lib/deluged/.config/deluge# grep -E -A5 "listen_ports" core.conf && grep -E -A2 "outgoing_ports" core.conf
"listen_ports": [
3000,
3000
],
"listen_random_port": null,
"listen_reuse_port": true,
"outgoing_ports": [
4000,
4000
--
"random_outgoing_ports": false,
"random_port": false,
"rate_limit_ip_overhead": true,After verifying that at least the settings of Deluge are correct, we can start looking at other things.
ss -tulpn | grep delugeIt will look something like this.
Code: Select all
<user>@<system>:/var/lib/deluged/.config/deluge# ss -tulpn | grep deluge
udp UNCONN 0 0 <ipv4address>%enP4p65s0:3000 0.0.0.0:* users:(("deluged",pid=832,fd=13))
udp UNCONN 0 0 0.0.0.0:6771 0.0.0.0:* users:(("deluged",pid=832,fd=16))
udp UNCONN 0 0 <ipv4address>:39560 0.0.0.0:* users:(("deluged",pid=832,fd=18))
udp UNCONN 0 0 <ipv6 adress>%enP4p65s0:3000 [::]:* users:(("deluged",pid=832,fd=15))
udp UNCONN 0 0 *:6771 *:* users:(("deluged",pid=832,fd=17))
tcp LISTEN 0 50 0.0.0.0:8112 0.0.0.0:* users:(("deluge-web",pid=833,fd=8))
tcp LISTEN 0 50 0.0.0.0:58846 0.0.0.0:* users:(("deluged",pid=832,fd=22))
tcp LISTEN 0 3000 <ipv4address>%enP4p65s0:3000 0.0.0.0:* users:(("deluged",pid=832,fd=11))
tcp LISTEN 0 3000 <ipv6address>%enP4p65s0:3000 [::]:* users:(("deluged",pid=832,fd=14))===============================================================
Server: Rock 5B 8 Cores (ARM), 16 GB RAM, 2 TB 970 Evo +
OS: Linux Ubuntu 24.04 LTS
Deluge: v2.2.0
Plugins: Blocklist, LabelPlus, ItConfig, MyScheduler, Stats, Notifications, YaRSS2
Server: Rock 5B 8 Cores (ARM), 16 GB RAM, 2 TB 970 Evo +
OS: Linux Ubuntu 24.04 LTS
Deluge: v2.2.0
Plugins: Blocklist, LabelPlus, ItConfig, MyScheduler, Stats, Notifications, YaRSS2
Deluge

