Port always closed

Ask for help and report issues with the Mac OS X version of Transmission
himhim
Posts: 12
Joined: Fri Mar 31, 2023 7:24 am

Port always closed

Post by himhim »

Hi there,

I'm having trouble getting the port open. Running Ventura 13.3, Transmission 4.0.2, tp-link AX1800. My router supports UPnP, but it doesn't seem to work. I have set up a port forward in my router per the instructions. Everything should be good, but it just stays red. My debug log is:

2023-03-31 07:27:49 +0000 port-forwarding-natpmp.cc:38 [Debug] port-forwarding-natpmp.cc:38: sendnewportmappingrequest succeeded (12)
2023-03-31 07:27:49 +0000 port-forwarding.cc:218 [Info] port-forwarding.cc:218: State changed from 'Forwarded' to 'Stopping'
2023-03-31 07:28:10 +0000 announcer-udp.cc:435 [Debug] 9.rarbg.me:2930: DNS lookup succeeded
2023-03-31 07:28:10 +0000 announcer-udp.cc:323 [Debug] 9.rarbg.to:2930: Got a new connection ID from tracker: 12782870857851616400
2023-03-31 07:28:10 +0000 announcer-udp.cc:520 [Debug] 9.rarbg.to:2930: sending req 0x7f96a5987c10
2023-03-31 07:28:10 +0000 announcer-udp.cc:537 [Debug] 9.rarbg.to:2930: sending request w/connection id 12782870857851616400
2023-03-31 07:28:11 +0000 announcer.cc:690 [Debug] Party.Down.S03E03.2160p.WEB.H265-GGWP[rarbg] at 9.rarbg.to:2930: peer counts: 19 seeders, 1 leechers.
2023-03-31 07:28:11 +0000 announcer-udp.cc:323 [Debug] 9.rarbg.me:2930: Got a new connection ID from tracker: 12782870857851616400
2023-03-31 07:28:11 +0000 announcer-udp.cc:520 [Debug] 9.rarbg.me:2930: sending req 0x7f96a5cefa10
2023-03-31 07:28:11 +0000 announcer-udp.cc:537 [Debug] 9.rarbg.me:2930: sending request w/connection id 12782870857851616400
2023-03-31 07:28:11 +0000 announcer.cc:690 [Debug] Party.Down.S03E01.2160p.WEB.H265-GGEZ[rarbg] at 9.rarbg.me:2930: peer counts: 13 seeders, 2 leechers.
2023-03-31 07:28:20 +0000 port-forwarding-natpmp.cc:38 [Debug] port-forwarding-natpmp.cc:38: initnatpmp succeeded (0)
2023-03-31 07:28:20 +0000 port-forwarding-natpmp.cc:38 [Debug] port-forwarding-natpmp.cc:38: sendpublicaddressrequest succeeded (2)
2023-03-31 07:28:20 +0000 port-forwarding.cc:218 [Info] port-forwarding.cc:218: State changed from 'Not forwarded' to 'Starting'
2023-03-31 07:28:23 +0000 port-forwarding-upnp.cc:290 [Debug] port-forwarding-upnp.cc:290: UPNP_GetValidIGD failed: Undefined error: 0 (0)
2023-03-31 07:28:23 +0000 port-forwarding-upnp.cc:291 [Debug] port-forwarding-upnp.cc:291: If your router supports UPnP, please make sure UPnP is enabled!
2023-03-31 07:28:28 +0000 port-forwarding-natpmp.cc:38 [Debug] port-forwarding-natpmp.cc:38: readnatpmpresponseorretry succeeded (0)
2023-03-31 07:28:28 +0000 port-forwarding-natpmp.cc:86 [Info] port-forwarding-natpmp.cc:86: Found public address '100.64.108.248'
2023-03-31 07:28:28 +0000 port-forwarding-natpmp.cc:38 [Debug] port-forwarding-natpmp.cc:38: sendnewportmappingrequest succeeded (12)
2023-03-31 07:28:28 +0000 port-forwarding-natpmp.cc:38 [Debug] port-forwarding-natpmp.cc:38: readnatpmpresponseorretry succeeded (0)
2023-03-31 07:28:28 +0000 port-forwarding-natpmp.cc:177 [Info] port-forwarding-natpmp.cc:177: Port 64621 forwarded successfully
2023-03-31 07:28:28 +0000 port-forwarding.cc:203 [Info] port-forwarding.cc:203: Mapped private port 64621 to public port 64621
2023-03-31 07:28:28 +0000 port-forwarding.cc:218 [Info] port-forwarding.cc:218: State changed from 'Starting' to 'Forwarded'
2023-03-31 07:29:20 +0000 announcer-udp.cc:435 [Debug] exodus.desync.com:6969: DNS lookup succeeded
2023-03-31 07:29:20 +0000 announcer-udp.cc:435 [Debug] tracker.opentrackr.org:1337: DNS lookup succeeded
2023-03-31 07:29:20 +0000 announcer-udp.cc:323 [Debug] glotorrents.pw:6969: Got a new connection ID from tracker: 7216609179065623135
2023-03-31 07:29:20 +0000 announcer-udp.cc:520 [Debug] glotorrents.pw:6969: sending req 0x7f96a7016c10
2023-03-31 07:29:20 +0000 announcer-udp.cc:537 [Debug] glotorrents.pw:6969: sending request w/connection id 7216609179065623135
2023-03-31 07:29:20 +0000 announcer.cc:690 [Debug] Animal.Control.S01E07.Peacocks.and.Pumas.1080p.AMZN.WEB-DL.DDP5.1.H.264-NTb[tracker.example.com].mkv at glotorrents.pw:6969: peer counts: 0 seeders, 0 leechers.
2023-03-31 07:29:21 +0000 announcer-udp.cc:323 [Debug] tracker.opentrackr.org:1337: Got a new connection ID from tracker: 9856266175496323213
2023-03-31 07:29:21 +0000 announcer-udp.cc:520 [Debug] tracker.opentrackr.org:1337: sending req 0x7f96a7017a10
2023-03-31 07:29:21 +0000 announcer-udp.cc:537 [Debug] tracker.opentrackr.org:1337: sending request w/connection id 9856266175496323213
2023-03-31 07:29:21 +0000 announcer-udp.cc:323 [Debug] exodus.desync.com:6969: Got a new connection ID from tracker: 14021544315526668778
2023-03-31 07:29:21 +0000 announcer-udp.cc:520 [Debug] exodus.desync.com:6969: sending req 0x7f96a7021410
2023-03-31 07:29:21 +0000 announcer-udp.cc:537 [Debug] exodus.desync.com:6969: sending request w/connection id 14021544315526668778
2023-03-31 07:29:21 +0000 announcer.cc:690 [Debug] Animal.Control.S01E07.Peacocks.and.Pumas.1080p.AMZN.WEB-DL.DDP5.1.H.264-NTb[tracker.example.com].mkv at exodus.desync.com:6969: peer counts: 3 seeders, 2 leechers.
2023-03-31 07:29:21 +0000 announcer.cc:690 [Debug] Animal.Control.S01E07.Peacocks.and.Pumas.1080p.AMZN.WEB-DL.DDP5.1.H.264-NTb[tracker.example.com].mkv at tracker.opentrackr.org:1337: peer counts: 40 seeders, 14 leechers.


I do note that it says halfway down that UPNP_GetValidIGD failed: Undefined error: 0 (0). Any ideas? Many thanks.
darmok
Posts: 119
Joined: Tue Oct 16, 2007 9:14 pm
Location: New Jersey, USA

Re: Port always closed

Post by darmok »

himhim wrote: Fri Mar 31, 2023 7:31 am \\snip
2023-03-31 07:28:20 +0000 port-forwarding.cc:218 [Info] port-forwarding.cc:218: State changed from 'Not forwarded' to 'Starting'
2023-03-31 07:28:23 +0000 port-forwarding-upnp.cc:290 [Debug] port-forwarding-upnp.cc:290: UPNP_GetValidIGD failed: Undefined error: 0 (0)
\\then, a bit later
2023-03-31 07:28:28 +0000 port-forwarding-natpmp.cc:86 [Info] port-forwarding-natpmp.cc:86: Found public address '100.64.108.248'
2023-03-31 07:28:28 +0000 port-forwarding-natpmp.cc:38 [Debug] port-forwarding-natpmp.cc:38: sendnewportmappingrequest succeeded (12)
2023-03-31 07:28:28 +0000 port-forwarding-natpmp.cc:38 [Debug] port-forwarding-natpmp.cc:38: readnatpmpresponseorretry succeeded (0)
2023-03-31 07:28:28 +0000 port-forwarding-natpmp.cc:177 [Info] port-forwarding-natpmp.cc:177: Port 64621 forwarded successfully
2023-03-31 07:28:28 +0000 port-forwarding.cc:203 [Info] port-forwarding.cc:203: Mapped private port 64621 to public port 64621
2023-03-31 07:28:28 +0000 port-forwarding.cc:218 [Info] port-forwarding.cc:218: State changed from 'Starting' to 'Forwarded'
I've had a lot of difficulty with UPnP, not just in Transmission. Too many timing / stability difficulties.

The solution, IMO, is to disable UPnP, and forward a port directly in your router.

fwiw,
- Dan.
himhim
Posts: 12
Joined: Fri Mar 31, 2023 7:24 am

Re: Port always closed

Post by himhim »

Hi Dan,

Thanks for your reply. I have set up a port forward already without luck – should I have the Automatically Map Port box unticked too? Randomise is already off.

Cheers
darmok
Posts: 119
Joined: Tue Oct 16, 2007 9:14 pm
Location: New Jersey, USA

Re: Port always closed

Post by darmok »

If you've told Transmission the open port to use, the two checkboxes below it shouldn't matter.
himhim
Posts: 12
Joined: Fri Mar 31, 2023 7:24 am

Re: Port always closed

Post by himhim »

Yeah I have typed the open port, but it doesn’t seem to see it as open. Can still give the red failure dot.
darmok
Posts: 119
Joined: Tue Oct 16, 2007 9:14 pm
Location: New Jersey, USA

Re: Port always closed

Post by darmok »

hum.

Go to https://www.grc.com/ and use the ShieldsUp tool to see if the port you're using is open.
himhim
Posts: 12
Joined: Fri Mar 31, 2023 7:24 am

Re: Port always closed

Post by himhim »

Hmm. It passed the ShieldsUp test, meaning the port is closed. It was seen as "Stealth – Unknown Protocol/Application for this port". But I've set up port forwarding in the router per instructions, a static IP address, and macOS Firewall is set to allow incoming connections for Transmission. I can't think what else might be stopping it – no antivirus running etc.
darmok
Posts: 119
Joined: Tue Oct 16, 2007 9:14 pm
Location: New Jersey, USA

Re: Port always closed

Post by darmok »

The basic ShieldsUp test checks the lower block of (mostly already assigned) ports. You need to dig deeper. The port you've opened for Transmission should be in the range 45000 or higher.

You need to pick something from the higher block, say 45451 or higher. Set up your router to open (forward) that. Then probe it - make sure it's open. THEN launch Transmission and tell it the port number...
himhim
Posts: 12
Joined: Fri Mar 31, 2023 7:24 am

Re: Port always closed

Post by himhim »

Hi - thanks, but I’m already doing that. It’s in the 64000 range. Router is forwarding, probe shows it’s closed.
darmok
Posts: 119
Joined: Tue Oct 16, 2007 9:14 pm
Location: New Jersey, USA

Re: Port always closed

Post by darmok »

and GRC shows the port as consistently open?
himhim
Posts: 12
Joined: Fri Mar 31, 2023 7:24 am

Re: Port always closed

Post by himhim »

No, GRC shows it closed, but my port is in the appropriate range specified.
darmok
Posts: 119
Joined: Tue Oct 16, 2007 9:14 pm
Location: New Jersey, USA

Re: Port always closed

Post by darmok »

If GRC shows the port as closed, then it's closed. For bittorrent to use it, it must be Open.

See also
https://github.com/transmission/transmi ... g-Guide.md
himhim
Posts: 12
Joined: Fri Mar 31, 2023 7:24 am

Re: Port always closed

Post by himhim »

I know, but I have opened the port in my router. That's why I'm so stumped.

Image
darmok
Posts: 119
Joined: Tue Oct 16, 2007 9:14 pm
Location: New Jersey, USA

Re: Port always closed

Post by darmok »

Is that device IP supposed to be your LAN or WAN address?
himhim
Posts: 12
Joined: Fri Mar 31, 2023 7:24 am

Re: Port always closed

Post by himhim »

That's my static IP address set up for my LAN, per the guides.
Post Reply