New Transmission 2.84 add-on for ReadyNAS Duo/NV+ (sparc)

Did you ever manually edit the config? If so, did you make sure to edit it using an appropriate text editor.

mdgm wrote:
Have you tried clearing your web browser cache, closing your web browser, then reopening Transmission's preference page and seeing if it's then displayed correctly?

It never worked for me, for reasons unknown, but the port is wide open, and the traffic passes through it with no issues. It's just broken. Which is why i was asking what gave everyone the testresults that the port actually was closed, and not just misreported.
B!

Have you tried clearing your web browser cache, closing your web browser, then reopening Transmission's preference page and seeing if it's then displayed correctly?

Mr_B wrote:

I have to ask again, what, exactly, is used to test the port, and gets the answer that it's closed, to make you guys default to thinking that transmission is at fault? At this point nobody can help you since they cant reproduce the error, and quite frankly, the error assumed, and the error messages supposedly being had according to the last few posts, doesn't add up. The communication with the TRACKER has NOTHING to do with the forwarded (or not) port for Transmission. If you can't reach the tracker, the problem isn't the port being forwarded or not. B!

Quite right, and my install of transmission does in fact work fine. The blocklist seemed to be the issue, the mint 7.1 install iso downloaded fine once I turned it off.

However, transmission's preferences page still reports the port being closed. I've verified it's open by ssh'ing to an Amazon EC2 instance I use at work, and using telnet to connect back, using the port listed. It happily connects. Switching uPnP off at the router, rebooting the nas and trying telnet again with the new, randomized port fails. Clearly it's working as intended, just being mis-reported in the preferences window.

Since it does work, I'm not really concerned with fixing it. Merely adding my two-bits to addict, confirming he's not the only one seeing it. Whether that particular issue has anything to do with his other issues, I don't know enough to have an opinion on.

Another idea.
You can't use blacklists with some trackers. Or put it this way, blocklists are getting too greedy.

I have to ask again, what, exactly, is used to test the port, and gets the answer that it's closed, to make you guys default to thinking that transmission is at fault?
At this point nobody can help you since they cant reproduce the error, and quite frankly, the error assumed, and the error messages supposedly being had according to the last few posts, doesn't add up.
The communication with the TRACKER has NOTHING to do with the forwarded (or not) port for Transmission. If you can't reach the tracker, the problem isn't the port being forwarded or not.
B!

I am also suffering from this issue. I have been for about a week, but I had things so screwed up from my deb-package making attempts that I didn't worry much about it. Just finished a full and complete factory reset after backing up my data, installed the transmission 2.84 addon and am now showing the port as closed. uPnP is enabled on the router, and no peers on any torrent. The NAS has internet connectivity, tested as good.

Just found another user experiencing the exact same symptoms using version 2.84 of Transmission on his Synology NAS. It started May 30, 2016, same as me. What could be going on here!?

oddly, there are no tracker errors, just Transmission showing Port Closed and no peers connected. I'll disable UPnP, go back to static routing, and try the same set of ports you used to see if it does anything. Thank You for replying!

I've been ransacking my memory, and i know i have set my transmission clients to static ports and manually configured them in the firewall, since some torrent sites had the habit of claiming that i was "un-connectable" at the uPnP specified port. But while some trackers reported this, others never saw an issue, so i believe it was actually on the tracker-end this issue existed. It also never resolved those trackers, they still think my port isn't open. In the end i just reported it to the admins, who made sure the tracker didn't pay attention to that, and that the peers gets my info regardless. What i'm aiming at... Are you sure your "checking" it with a working tool?

Also, "could not connect to tracker" shouldn't have anything to do with your port forward setup. the port you set is nothing but active mode transfers. Thats peer to peer. The tracker communication doesn't need a incoming port configured. It just expects that outgoing traffic is allowed, and the tracker has the "active" role in the conversation. Meaning unless your NAS is blocked from accessing the net, it's not on your end. The tracker simply doesn't respond. You can be blocked / banned, or, the tracker is blocked / banned, in your gateway/firewall, or possibly on a ISP level.

Anyway, the description of the error, and the suggested problem doesn't seam to add up. Figure out whats actually broken, and start looking at it from that end, and it should be easier to provide an answer...
B!