How would you troubleshoot: Transmission port test fails despite port being open. Unable to download torrents
Recently started having trouble with Transmission, worked fine before. But now it just never starts downloading the torrents. I went to see if maybe it was a firewall issue so I looked in preferences and saw that it was set to 51413. I tired to test the port using the tool provided by transmission and that test came back Closed. So I went went to the CL and explicitly opened it with sudo ufw allow 51413 Here is my ufw status:
Status: active
To Action From
-- ------ ----
22 ALLOW Anywhere
51413 ALLOW Anywhere
22 (v6) ALLOW Anywhere (v6)
51413 (v6) ALLOW Anywhere (v6)
I go back into transmission and test the port, and it still comes back as closed.
I tried disabling the firewall altogether, no difference.
Has anyone else seen this issue? Any suggestions for further troubleshooting?
UPDATE
I let the Transmission torrent just sit there and I just noted that it started downloading. I checked my firewall rules and I saw that I was no longer explicitly opening 51413. I double checked that the port had not been changed in Transmission, it was still 51413. I tried to test the port again using Transmission and it just sits there with Testing TCP Port... and never comes back with a result.
By the way, the item I was downloading was heavily seeded.
Any ideas why Transmission would take so long (30 min) to begin a download and or ideas about the port testing flakiness?
firewall bittorrent transmission
asked Dec 13 '18 at 19:47
Robert Baker
739
add a comment |
Recently started having trouble with Transmission, worked fine before. But now it just never starts downloading the torrents. I went to see if maybe it was a firewall issue so I looked in preferences and saw that it was set to 51413. I tired to test the port using the tool provided by transmission and that test came back Closed. So I went went to the CL and explicitly opened it with sudo ufw allow 51413 Here is my ufw status:
Status: active
To Action From
-- ------ ----
22 ALLOW Anywhere
51413 ALLOW Anywhere
22 (v6) ALLOW Anywhere (v6)
51413 (v6) ALLOW Anywhere (v6)
I go back into transmission and test the port, and it still comes back as closed.
I tried disabling the firewall altogether, no difference.
Has anyone else seen this issue? Any suggestions for further troubleshooting?
UPDATE
I let the Transmission torrent just sit there and I just noted that it started downloading. I checked my firewall rules and I saw that I was no longer explicitly opening 51413. I double checked that the port had not been changed in Transmission, it was still 51413. I tried to test the port again using Transmission and it just sits there with Testing TCP Port... and never comes back with a result.
By the way, the item I was downloading was heavily seeded.
Any ideas why Transmission would take so long (30 min) to begin a download and or ideas about the port testing flakiness?
firewall bittorrent transmission
asked Dec 13 '18 at 19:47
Robert Baker
739
1
It's probably not Transmission - mine is rock solid and super-fast. So it's probably not Ubuntu either. Start looking at how limiting yourself to a single open port throttles your ability to get updates from the tracker and negotiate access to other members of the swarm.
– user535733
Dec 13 '18 at 21:48
add a comment |
Recently started having trouble with Transmission, worked fine before. But now it just never starts downloading the torrents. I went to see if maybe it was a firewall issue so I looked in preferences and saw that it was set to 51413. I tired to test the port using the tool provided by transmission and that test came back Closed. So I went went to the CL and explicitly opened it with sudo ufw allow 51413 Here is my ufw status:
Status: active
To Action From
-- ------ ----
22 ALLOW Anywhere
51413 ALLOW Anywhere
22 (v6) ALLOW Anywhere (v6)
51413 (v6) ALLOW Anywhere (v6)
I go back into transmission and test the port, and it still comes back as closed.
I tried disabling the firewall altogether, no difference.
Has anyone else seen this issue? Any suggestions for further troubleshooting?
UPDATE
I let the Transmission torrent just sit there and I just noted that it started downloading. I checked my firewall rules and I saw that I was no longer explicitly opening 51413. I double checked that the port had not been changed in Transmission, it was still 51413. I tried to test the port again using Transmission and it just sits there with Testing TCP Port... and never comes back with a result.
By the way, the item I was downloading was heavily seeded.
Any ideas why Transmission would take so long (30 min) to begin a download and or ideas about the port testing flakiness?
firewall bittorrent transmission
asked Dec 13 '18 at 19:47
Robert Baker
739
Recently started having trouble with Transmission, worked fine before. But now it just never starts downloading the torrents. I went to see if maybe it was a firewall issue so I looked in preferences and saw that it was set to 51413. I tired to test the port using the tool provided by transmission and that test came back Closed. So I went went to the CL and explicitly opened it with sudo ufw allow 51413 Here is my ufw status:
Status: active
To Action From
-- ------ ----
22 ALLOW Anywhere
51413 ALLOW Anywhere
22 (v6) ALLOW Anywhere (v6)
51413 (v6) ALLOW Anywhere (v6)
I go back into transmission and test the port, and it still comes back as closed.
I tried disabling the firewall altogether, no difference.
Has anyone else seen this issue? Any suggestions for further troubleshooting?
UPDATE
I let the Transmission torrent just sit there and I just noted that it started downloading. I checked my firewall rules and I saw that I was no longer explicitly opening 51413. I double checked that the port had not been changed in Transmission, it was still 51413. I tried to test the port again using Transmission and it just sits there with Testing TCP Port... and never comes back with a result.
By the way, the item I was downloading was heavily seeded.
Any ideas why Transmission would take so long (30 min) to begin a download and or ideas about the port testing flakiness?
firewall bittorrent transmission
firewall bittorrent transmission
asked Dec 13 '18 at 19:47
Robert Baker
739
asked Dec 13 '18 at 19:47
Robert Baker
739
edited Dec 13 '18 at 20:09
asked Dec 13 '18 at 19:47
Robert Baker
739
asked Dec 13 '18 at 19:47
Robert Baker
739
asked Dec 13 '18 at 19:47
Robert Baker
739
739
1
It's probably not Transmission - mine is rock solid and super-fast. So it's probably not Ubuntu either. Start looking at how limiting yourself to a single open port throttles your ability to get updates from the tracker and negotiate access to other members of the swarm.
– user535733
Dec 13 '18 at 21:48
add a comment |
1
It's probably not Transmission - mine is rock solid and super-fast. So it's probably not Ubuntu either. Start looking at how limiting yourself to a single open port throttles your ability to get updates from the tracker and negotiate access to other members of the swarm.
– user535733
Dec 13 '18 at 21:48
1
1
It's probably not Transmission - mine is rock solid and super-fast. So it's probably not Ubuntu either. Start looking at how limiting yourself to a single open port throttles your ability to get updates from the tracker and negotiate access to other members of the swarm.
– user535733
Dec 13 '18 at 21:48
It's probably not Transmission - mine is rock solid and super-fast. So it's probably not Ubuntu either. Start looking at how limiting yourself to a single open port throttles your ability to get updates from the tracker and negotiate access to other members of the swarm.
– user535733
Dec 13 '18 at 21:48
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1100712%2fhow-would-you-troubleshoot-transmission-port-test-fails-despite-port-being-open%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1100712%2fhow-would-you-troubleshoot-transmission-port-test-fails-despite-port-being-open%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
It's probably not Transmission - mine is rock solid and super-fast. So it's probably not Ubuntu either. Start looking at how limiting yourself to a single open port throttles your ability to get updates from the tracker and negotiate access to other members of the swarm.
– user535733
Dec 13 '18 at 21:48