Transmission port closed

Troubleshooting
1

Already port forwarding 51413 but still show port closed ? anyone know why ?

2

Is transmission running?
sudo systemctl status transmission-daemon

3

Also, are you running a vpn?

4 
 transmission-daemon.service - Transmission BitTorrent Daemon
     Loaded: loaded (/lib/systemd/system/transmission-daemon.service; disabled; vendor preset: enabled)
     Active: active (running) since Mon 2022-06-27 13:58:31 BST; 2h 22min ago
   Main PID: 1454 (transmission-da)
     Status: "Idle."
      Tasks: 4 (limit: 4448)
     Memory: 15.8M
        CPU: 1min 2.622s
     CGroup: /system.slice/transmission-daemon.service
             └─1454 /usr/bin/transmission-daemon -f --log-error

Jun 27 13:58:31 DietPi systemd[1]: Starting Transmission BitTorrent Daemon...
Jun 27 13:58:31 DietPi systemd[1]: Started Transmission BitTorrent Daemon.
Jun 27 14:04:39 DietPi transmission-daemon[1454]: [2022-06-27 14:04:39.690] UDP Failed to set receive buffer: requested 4194304, got 360448 (tr-udp.c:97)
Jun 27 14:04:39 DietPi transmission-daemon[1454]: [2022-06-27 14:04:39.690] UDP Failed to set send buffer: requested 1048576, got 360448 (tr-udp.c:105)
Jun 27 14:04:39 DietPi transmission-daemon[1454]: [2022-06-27 14:04:39.691] UDP Failed to set receive buffer: requested 4194304, got 360448 (tr-udp.c:97)
Jun 27 14:04:39 DietPi transmission-daemon[1454]: [2022-06-27 14:04:39.691] UDP Failed to set send buffer: requested 1048576, got 360448 (tr-udp.c:105)
root@DietPi:~#
5

No because I am using as seed box and ppt not allow me to use vpn .

6

Check whether Transmission really listens on this port and whether there is a firewall rule active:

ss -tulpn
iptables -L
7 
root@DietPi:~# ss -tulpn
iptables -L
Netid   State    Recv-Q    Send-Q                                Local Address:Port        Peer Address:Port   Process
udp     UNCONN   0         0                                           0.0.0.0:59912            0.0.0.0:*       users:(("transmission-da",pid=1454,fd=20))
udp     UNCONN   0         0                                           0.0.0.0:68               0.0.0.0:*       users:(("dhclient",pid=456,fd=9))
udp     UNCONN   0         0                                   xxx.yyy.zzz.aaa:6771             0.0.0.0:*       users:(("transmission-da",pid=1454,fd=19))
udp     UNCONN   0         0                                           0.0.0.0:32897            0.0.0.0:*       users:(("transmission-da",pid=1454,fd=13))
udp     UNCONN   0         0                                    192.168.50.255:137              0.0.0.0:*       users:(("nmbd",pid=1429,fd=16))
udp     UNCONN   0         0                                    192.168.50.113:137              0.0.0.0:*       users:(("nmbd",pid=1429,fd=15))
udp     UNCONN   0         0                                           0.0.0.0:137              0.0.0.0:*       users:(("nmbd",pid=1429,fd=13))
udp     UNCONN   0         0                                    192.168.50.255:138              0.0.0.0:*       users:(("nmbd",pid=1429,fd=18))
udp     UNCONN   0         0                                    192.168.50.113:138              0.0.0.0:*       users:(("nmbd",pid=1429,fd=17))
udp     UNCONN   0         0                                           0.0.0.0:138              0.0.0.0:*       users:(("nmbd",pid=1429,fd=14))
udp     UNCONN   0         0                                           0.0.0.0:51413            0.0.0.0:*       users:(("transmission-da",pid=1454,fd=17))
udp     UNCONN   0         0            [xxxx:yyyy:....]:51413               [::]:*       users:(("transmission-da",pid=1454,fd=18))
tcp     LISTEN   0         128                                         0.0.0.0:9091             0.0.0.0:*       users:(("transmission-da",pid=1454,fd=14))
tcp     LISTEN   0         50                                          0.0.0.0:139              0.0.0.0:*       users:(("smbd",pid=1441,fd=45))
tcp     LISTEN   0         50                                          0.0.0.0:8112             0.0.0.0:*       users:(("deluge-web",pid=1473,fd=7))
tcp     LISTEN   0         128                                         0.0.0.0:51413            0.0.0.0:*       users:(("transmission-da",pid=1454,fd=15))
tcp     LISTEN   0         128                                         0.0.0.0:22               0.0.0.0:*       users:(("sshd",pid=562,fd=3))
tcp     LISTEN   0         50                                          0.0.0.0:445              0.0.0.0:*       users:(("smbd",pid=1441,fd=44))
tcp     LISTEN   0         50                                          0.0.0.0:58846            0.0.0.0:*       users:(("deluged",pid=1465,fd=13))
tcp     LISTEN   0         50                                             [::]:139                 [::]:*       users:(("smbd",pid=1441,fd=43))
tcp     LISTEN   0         128                                            [::]:51413               [::]:*       users:(("transmission-da",pid=1454,fd=16))
tcp     LISTEN   0         128                                            [::]:22                  [::]:*       users:(("sshd",pid=562,fd=4))
tcp     LISTEN   0         50                                             [::]:445                 [::]:*       users:(("smbd",pid=1441,fd=42))
-bash: iptables: command not found
root@DietPi:~#
8

I don’t know if i did it right because in Unraid transmission port forwarding is : 444,25565,51413 but i don’t know much about dietpi transmission i only did 51413

9

Okay so port is listened on and no iptables installed (nftables isn’t either, right?), so from that end it looks good. Double check that TCP and UDP port is forwarded.

Also check whether the web UI is reachable externally when you (temporarily) forward that TCP port 9091.

10

screenshot removed deleted

11

Check this out, this is adressing the buffer error:

1 Like
12

Ah, probably this is even the reason for the failed port check. I’ll check our Transmission config, probably we set buffer sizes there which exceed the ones allowed by the system :thinking:.

13

now i removed the screen shot

14

anyone fix that already ?