Port is closed issue

Ask for help and report issues with the Mac OS X version of Transmission
Post Reply
tapeworm48
Posts: 1
Joined: Thu Mar 03, 2022 1:15 am

Port is closed issue

Post by tapeworm48 »

I'm new to the Mac OS and trying to get transmission setup.

I want to upload to Dimeadozen, but once I download the torrent file, select the source directory, there is no traction in uploading my files and seeding.

I included the error log below. Everything is setup in accordance with all the guidance I'm finding online for OS Monterrey.

FWIW I'm on a VPN (Surfshark) and using an Asus RTn56u router. uPnP is enabled, and I've opened port 50001 for transmission. additionally, incoming connections are allowed on the firewall from Transmission.

Thanks in advance!

Code: Select all

2022-03-02 18:15:20 +0000 session.c:769 [Info] Transmission: Transmission 3.00 (f4489c982e) started
2022-03-02 18:15:20 +0000 utils.c:263 [Debug] Transmission: Couldn't read "/Users/vikasbhatia/Library/Application Support/Transmission/stats.json": No such file or directory
2022-03-02 18:15:20 +0000 utils.c:263 [Debug] Transmission: Couldn't read "/Users/vikasbhatia/Library/Application Support/Transmission/stats.benc": No such file or directory
2022-03-02 18:15:20 +0000 cache.c:260 [Debug] Cache: Maximum cache size set to 4.00 MB (244 blocks)
2022-03-02 18:15:20 +0000 rpc-server.c:956 [Info] RPC Server: Adding address to whitelist: 127.0.0.1
2022-03-02 18:15:20 +0000 rpc-server.c:956 [Info] RPC Server: Adding address to whitelist: ::1
2022-03-02 18:15:20 +0000 net.c:462 [Debug] Transmission: Bound socket 9 to port 50001 on 0.0.0.0
2022-03-02 18:15:20 +0000 net.c:462 [Debug] Transmission: Bound socket 10 to port 50001 on ::
2022-03-02 18:15:20 +0000 tr-dht.c:338 [Debug] DHT: Initializing DHT
2022-03-02 18:15:20 +0000 tr-dht.c:383 [Info] DHT: Reusing old id
2022-03-02 18:15:20 +0000 tr-dht.c:413 [Debug] DHT: DHT initialized
2022-03-02 18:15:20 +0000 tr-dht.c:172 [Info] DHT: Bootstrapping from 300 IPv4 nodes
2022-03-02 18:15:20 +0000 rpc-server.c:956 [Info] RPC Server: Adding address to whitelist: 127.0.0.1
2022-03-02 18:15:20 +0000 resume.c:841 [Debug] beck2021-10-01.at831.flac24: Read resume file "/Users/vikasbhatia/Library/Application Support/Transmission/Resume/d31d282730101327c0f538cc49e910701b7ecdfb.resume"
2022-03-02 18:15:20 +0000 resume.c:96 [Debug] beck2021-10-01.at831.flac24: Loaded 3 IPv4 peers from resume file
2022-03-02 18:15:20 +0000 resume.c:201 [Debug] beck2021-10-01.at831.flac24: Resume file found 22 files marked for download
2022-03-02 18:15:20 +0000 variant.c:1221 [Info] Transmission: Saved "/Users/vikasbhatia/Library/Application Support/Transmission/Torrents/d31d282730101327c0f538cc49e910701b7ecdfb.torrent"
2022-03-02 18:15:20 +0000 natpmp.c:73 [Info] Port Forwarding (NAT-PMP): initnatpmp succeeded (0)
2022-03-02 18:15:20 +0000 natpmp.c:73 [Info] Port Forwarding (NAT-PMP): sendpublicaddressrequest succeeded (2)
2022-03-02 18:15:20 +0000 upnp.c:208 [Debug] Port Forwarding (UPnP): UPNP_GetValidIGD failed (errno 0 - Undefined error: 0)
2022-03-02 18:15:20 +0000 upnp.c:209 [Debug] Port Forwarding (UPnP): If your router supports UPnP, please make sure UPnP is enabled!
2022-03-02 18:15:20 +0000 port-forwarding.c:107 [Info] Port Forwarding: State changed from "Not forwarded" to "Starting"
2022-03-02 18:15:28 +0000 announcer.c:1723 [Debug] beck2021-10-01.at831.flac24: Announcing to tracker
2022-03-02 18:15:28 +0000 web.c:456 [Info] web: will verify tracker certs using envvar CURL_CA_BUNDLE: none
2022-03-02 18:15:28 +0000 web.c:457 [Info] web: NB: this only works if you built against libcurl with openssl or gnutls, NOT nss
2022-03-02 18:15:28 +0000 web.c:458 [Info] web: NB: invalid certs will show up as 'Could not connect to tracker' like many other errors
2022-03-02 18:15:28 +0000 natpmp.c:78 [Debug] Port Forwarding (NAT-PMP): readnatpmpresponseorretry failed. Natpmp returned -7 (the gateway does not support nat-pmp); errno is 61 (Connection refused)
2022-03-02 18:15:28 +0000 port-forwarding.c:107 [Info] Port Forwarding: State changed from "Starting" to "???"
2022-03-02 18:15:29 +0000 fdlimit.c:408 [Info] Transmission: Changed open file limit from 2560 to 1024
2022-03-02 18:15:29 +0000 fdlimit.c:576 [Debug] Transmission: SO_SNDBUF size is 131072
2022-03-02 18:15:29 +0000 fdlimit.c:584 [Debug] Transmission: SO_RCVBUF size is 131072
2022-03-02 18:15:39 +0000 torrent.c:604 [Debug] beck2021-10-01.at831.flac24: Got 3 peers from tracker
2022-03-02 18:15:41 +0000 announcer.c:1486 [Debug] beck2021-10-01.at831.flac24: Scrape successful. Rescraping in 1800 seconds.
AlienLanes
Posts: 5
Joined: Tue Nov 30, 2010 7:39 pm

Re: Port is closed issue

Post by AlienLanes »

i'm a novice, absolutely no tech knowledge but i found this in search.
Port is closed Problem
viewtopic.php?t=18195

for me transmission 3.00 on M1 12.2.1, paid VPN, maybe once per two weeks TM stops DL/UL (i've changed no options). quit/restart... maybe does a few KB UL/DL then all pause again. i can see status in torrent "Seeding to 2 of 6"... "Downloading from 5 of 30"... but no actual data transfers. this lasts for hours/couple days. then transmission works as normal. TM has been installed/working for 3 months then this started. i always then install VUZE which immediately works when Transmission is not.

not sure if we're experiencing the same issue?
Post Reply