Page 1 of 1

Can't connect to deluged from thinClient

Posted: Sun Jun 09, 2013 1:41 pm
by flux1715
Hi!

I installed deluge to my raspberry pi /arch linux.
When I start the deamon manually as root, i'm able to connect to it from windows with deluge ThinClient.
But when I set 'systemctl enable deluged', (so I start it at boot with deluge user) i can't connect to the daemon any more from the thinClient.

When i start it as root manually, the nestat says:
tcp 0 0 0.0.0.0:58846 0.0.0.0:* LISTEN
but if i start as deluge user at boot, the netsat says:
tcp 0 0 127.0.0.1:58846 0.0.0.0:* LISTEN
I don't if it is a problem or not, but in the second case i can't see the port from the windows machine. (The port scanner says it is closed).( In the first case, it's open, of course.)

Is it possible to make the port reachable from local network (so from my windows pc) or i should use ssh tunneling or port forwarding?

Thanks for your help!

Re: Can't connect to deluged from thinClient

Posted: Sun Jun 09, 2013 3:51 pm
by Cas
Starting manually and starting as a service usually will use a different config location, default to the user running the service.

Re: Can't connect to deluged from thinClient

Posted: Mon Jun 10, 2013 11:02 pm
by flux1715
Thanks, i edited the core.conf, now I can connect to the daemon with thin thinClient, but the daemon don't get any connection (no dht nodes, no peers). Again, if i start the deamon as root, it works well. I checked the conf files, i didn't see any differences, that would prevent the connection to the internet.
Any idea?