Problem solved.
I was under the impression that any device with uPnP will automatically port forward. But I had DMZ enabled in router setting, and so I still needed to manually forward a port.
Search found 3 matches
- Sun Aug 31, 2014 5:52 am
- Forum: Support
- Topic: Transmission says "Port is closed." Debug disagrees
- Replies: 2
- Views: 3906
- Sat Aug 30, 2014 4:03 pm
- Forum: Support
- Topic: Transmission says "Port is closed." Debug disagrees
- Replies: 2
- Views: 3906
Re: Transmission says "Port is closed." Debug disagrees
UPDATE:
I doubled checked and my firewall DOES allows transmission to receive incoming connections.
canyouseeme.org reports:
Error: I could not see your service on xx.xx.xx.x on port (64919)
Reason: Connection timed out
64919 is the port that my transmission uses
I doubled checked and my firewall DOES allows transmission to receive incoming connections.
canyouseeme.org reports:
Error: I could not see your service on xx.xx.xx.x on port (64919)
Reason: Connection timed out
64919 is the port that my transmission uses
- Sat Aug 30, 2014 7:04 am
- Forum: Support
- Topic: Transmission says "Port is closed." Debug disagrees
- Replies: 2
- Views: 3906
Transmission says "Port is closed." Debug disagrees
Using Transmission 2.84 on Mac OS 10.9.4
Transmission shows a red dot and states that port is closed even though debug log says port forward successful as show below.
I first turned automatic port forward off, and then turned it back on
2014-08-30 06:43:13 +0000 port-forwarding.c:180 [Info] Port ...
Transmission shows a red dot and states that port is closed even though debug log says port forward successful as show below.
I first turned automatic port forward off, and then turned it back on
2014-08-30 06:43:13 +0000 port-forwarding.c:180 [Info] Port ...