Opened 9 years ago

Closed 8 years ago

Last modified 4 years ago

#2203 closed bug (Fixed)

1.3.900-dev connection manager port is 0

Reported by: MasterCATZ Owned by:
Priority: minor Milestone: 2.x
Component: GTK UI Version: master
Keywords: Cc:

Description

for some reason all the remote servers are listed as port 0 and I can not manually change them they keep resetting back to port 0

connection manager

add

type in hostname type in port port 58846 click somewhere else it changes back to 0

Change History (10)

comment:1 follow-up: Changed 9 years ago by Cas

Sounds suspiciously like you are trying to connect to a 1.3.x daemon.

comment:2 in reply to: ↑ 1 Changed 9 years ago by Prodec

Replying to Cas:

Sounds suspiciously like you are trying to connect to a 1.3.x daemon.

I have the same problem with 1.3.9-dev on windows 7 64bit. From Linux 1.3.9-dev works right, and can connect to my headless server running 1.3.9-dev.

comment:3 Changed 9 years ago by MasterCATZ

what pre configured 1.3.5 show's

http://imageshack.us/photo/my-images/23/screenshotfrom201211012.png/

what 1.3.5 pre configured show's afer updated to 1.3.900-dev

http://imageshack.us/photo/my-images/856/screenshotfrom201211012.png/

but if you click on that fancy edit button BOoM port 0

http://imageshack.us/photo/my-images/824/screenshotfrom201211012.png/

I mostly use deluge to connect to my seed box's now

this is doing it on both FreeBSD and Ubuntu

daemons been left as 1.3.5 as proven stable ( running on FreeBSD and rather not build from source )

how ever the GUI on Ubuntu is another story :P

I do like the looks of whats going towards 1.4

comment:4 Changed 9 years ago by Cas

You cannot connect to 1.3.5 with git master as it is destined to be 1.4 and major versions of Deluge are incompatible, I have mentioned this many times on the forum.

comment:5 Changed 9 years ago by MasterCATZ

  • Version changed from other (please specify) to git master

ok

sorry about that then

I guess thats why the ones on the local LAN here that were updated did work

but still why is the port number not changing >?

if I was to add a new server in the listing it still just goes 0

or does the new system no longer need a port ?

comment:6 Changed 9 years ago by Cas

I think it is because you are migrating your config from 1.3 to dev so try a fresh config.

comment:7 Changed 9 years ago by MasterCATZ

still did it and as root account rm -R /root/.config/deluge

sure it created a working localclient@127.0.0.1:58846

but if you click edit it goes to port 0

and trying to add any others they all go port 0

any other idea's

comment:8 Changed 9 years ago by Cas

  • Milestone changed from Future to 1.4.0

comment:9 Changed 8 years ago by bro

  • Component changed from other/unknown to GTK-UI
  • Resolution set to Fixed
  • Status changed from new to closed

I believe the issue with the port being reset to 0 was fixed in cdfb337b

comment:10 Changed 4 years ago by Cas

  • Milestone changed from 2.0.x to 2.x

Milestone renamed

Note: See TracTickets for help on using tickets.