#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)
follow-up: 2 comment:1 by , 12 years ago
comment:2 by , 12 years ago
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 by , 12 years ago
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 by , 12 years ago
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 by , 12 years ago
Version: | other (please specify) → 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 by , 12 years ago
I think it is because you are migrating your config from 1.3 to dev so try a fresh config.
comment:7 by , 12 years ago
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 by , 12 years ago
Milestone: | Future → 1.4.0 |
---|
comment:9 by , 11 years ago
Component: | other/unknown → GTK-UI |
---|---|
Resolution: | → Fixed |
Status: | new → closed |
I believe the issue with the port being reset to 0 was fixed in cdfb337b
Sounds suspiciously like you are trying to connect to a 1.3.x daemon.