Deluge Forum

Hi,
I cannot get a successful open port with Deluge
I have used the same port number that I use for Azureus.
I have tried opening a new port specifically for Deluge.
Nothing seems to work.

I did notice that Deluge appears to be scanning ports on my router, possibly my router my interpret this as hostile activity and block it accordingly.

Currently I am back on Azureus

Used the previous release and the latest > .95

Any help would be appreciated

John

teaBagger wrote:Hi,
I cannot get a successful open port with Deluge
I have used the same port number that I use for Azureus.
I have tried opening a new port specifically for Deluge.
Nothing seems to work.

I did notice that Deluge appears to be scanning ports on my router, possibly my router my interpret this as hostile activity and block it accordingly.

Currently I am back on Azureus

Used the previous release and the latest > .95

Any help would be appreciated

John

which os?

OS: Vista64

With the latest versions, whenever I clicked the "test active port" button, it returns a message that the port xxxx is closed at 72.x.x.x. Did I miss something here?

mynogan wrote:With the latest versions, whenever I clicked the "test active port" button, it returns a message that the port xxxx is closed at 72.x.x.x. Did I miss something here?

you need to open up the port in your firewall and/or forward the port in your router

Port has been opened manually in firewall and router.
Router supports uPNP port mapping.
Still cannot get a connection to deluge? I really want to use this program.
Azureus and uTorrent can get port connections fine (green)

>>markybob

The relevant port has been forwarded in the router. My Wan IP (dynamic) is never in the 72.x.x.x range, it's always been either in 188.x.x.x., 218.x.x.x., or 219.x.x.x. and is so reported in the router's status.

Hmmm, p.s., it's testing through the deluge web browser??

mynogan wrote:>>markybob

The relevant port has been forwarded in the router. My Wan IP (dynamic) is never in the 72.x.x.x range, it's always been either in 188.x.x.x., 218.x.x.x., or 219.x.x.x. and is so reported in the router's status.

Hmmm, p.s., it's testing through the deluge web browser??

yeah that's a bug which has been fixed in svn and will be in the next release.
try copying the address found in the deluge web browser into your normal web browser and see what is says.

you could also try enabling the network health monitor plugin and seeing what is says (it's displays a message in the status bar at the bottom of the main window in deluge).