Opened 15 years ago

Closed 14 years ago

Last modified 14 years ago

#403 closed bug (Invalid)

Manual port does not work

Reported by: tim.kornhammar@… Owned by: markybob
Priority: minor Milestone:
Component: Core Version: 1.0.4
Keywords: network listening ports random Cc:



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 Changed 15 years ago by tim.kornhammar@…

  • Resolution set to fixed
  • Status changed from new to closed
  • Version changed from 0.9.04 (1.0.0_RC4) to 0.9.05 (1.0.0_RC5)

Problem fixed in 0.9.06.

comment:2 Changed 14 years ago by ippazio.martella@…

  • Component changed from 0.5.x to core
  • Keywords network listening ports random added
  • Milestone changed from 1.0.0 to 1.0.4
  • Priority changed from major to minor
  • Resolution fixed deleted
  • Status changed from closed to reopened
  • Version changed from 0.9.05 (1.0.0_RC5) to 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 Changed 14 years ago by mvoncken

deluge will pick a random port if the chosen port is not availble. run netstat to check if the port is free.

comment:4 follow-up: Changed 14 years ago by ippazio.martella@…

You are right. But those port are owned by deluged, how can it be?

comment:5 in reply to: ↑ 4 Changed 14 years ago by ippazio.martella@…

Replying to

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 Changed 14 years ago by markybob

  • Resolution set to invalid
  • Status changed from reopened to closed

comment:7 Changed 14 years ago by anonymous

  • Milestone 1.0.4 deleted

Milestone 1.0.4 deleted

Note: See TracTickets for help on using tickets.