#403 closed bug (Invalid)
Manual port does not work
Reported by: | tim.kornhammar@gmail.com | Owned by: | markybob |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Core | Version: | 1.0.4 |
Keywords: | network listening ports random | Cc: |
Description
Hi.
I've been trying to select a port that I would like to use as fixed port in Deluge. However Deluge only seems to accept "random" ports even though it is not selected. Even check if active port shows the wrong port.
This is a major problem since I cannot run Deluge in active mode.
Change History (7)
comment:1 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Version: | 0.9.04 (1.0.0_RC4) → 0.9.05 (1.0.0_RC5) |
comment:2 by , 16 years ago
Component: | 0.5.x → core |
---|---|
Keywords: | network listening ports random added |
Milestone: | 1.0.0 → 1.0.4 |
Priority: | major → minor |
Resolution: | fixed |
Status: | closed → reopened |
Version: | 0.9.05 (1.0.0_RC5) → 1.0.4 |
Same problem with version 1.0.3 and 1.0.4. Tell me where is my mistake: In the network section the "Use random ports" checkbox is checked. So I uncheck the option, I change the two port numbers to 6883 and I click apply. The active port label changes to a new random port and I got "no incoming connection" in the statusbar.
comment:3 by , 16 years ago
deluge will pick a random port if the chosen port is not availble. run netstat to check if the port is free.
follow-up: 5 comment:4 by , 16 years ago
You are right. But those port are owned by deluged, how can it be?
comment:5 by , 16 years ago
Replying to ippazio.martella@gmail.com:
You are right. But those port are owned by deluged, how can it be?
Thx for your help. Multiple istances of deluged were running. It seems that when I closed deluge during my tests, the deluged daemon wasn't terminate as well and they keep the desired ports busy. How can I avoid this?
comment:6 by , 16 years ago
Resolution: | → invalid |
---|---|
Status: | reopened → closed |
Problem fixed in 0.9.06.