Can't connect Deluge thin client after Win10 refresh

General support for any problems installing or running Deluge
Racxie
New User
New User
Posts: 3
Joined: Thu Mar 16, 2017 1:23 am
OS or Distro: Windows/Debian

Can't connect Deluge thin client after Win10 refresh

Postby Racxie » Thu Mar 16, 2017 1:28 am

I recenty refreshed Windows 10 (a bit like a factory reset but keeps your documents/some files) and re-installed Deluge.

Once I've entered the details into the connection manager, the status shows as red and the "Start local daemon" button is greyed out.

I've tried restarting Deluge on my Debian server as well as changing the active port and mirroring that in the client but the button is still greyed out and it won't connect (had no problems prior to refresh).

I've also ensured that "allow_remote" is set to "true" and that the auth file contains my login details. I can access the server via WinSCP as well as ping it so there's no issues with the server running.

The 'ps aux | grep deluge' command shows that deluge is running.

Any help would be greatly appreciated as I've scoured Google and asked on Reddit without any luck.

shamael
Seeder
Seeder
Posts: 152
Joined: Sat Oct 08, 2016 9:28 am
OS or Distro: osmc

Re: Can't connect Deluge thin client after Win10 refresh

Postby shamael » Thu Mar 16, 2017 9:54 am

What tells the deluged log on the Debian server? Can you connect the daemon with deluge-console on the server itself?
The webui is available?

Racxie
New User
New User
Posts: 3
Joined: Thu Mar 16, 2017 1:23 am
OS or Distro: Windows/Debian

Re: Can't connect Deluge thin client after Win10 refresh

Postby Racxie » Thu Mar 16, 2017 3:32 pm

I'm not sure where the log file is/how to access it? I've just installed the Web UI but can't connect (status says offline/start daemon button is greyed out).
Installed and ran deluge-console but get the error "Failed to connect to <host:port> with reason: Connection refused" - I tried both the default host & port as well as the server's IP and port I had changed it to but all the connections were refused.

I quit the console and the command line displayed the following:

Code: Select all

Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
Failure: twisted.internet.error.ConnectionRefusedError: Connection was refused by other side: 111: Connection refused.


Although I did install the WebUI on a different server with the help of a friend and installed the thin client myself at least a year ago, I'm not very proficient with Linux or Deluge so sorry if I'm asking some basic questions!

shamael
Seeder
Seeder
Posts: 152
Joined: Sat Oct 08, 2016 9:28 am
OS or Distro: osmc

Re: Can't connect Deluge thin client after Win10 refresh

Postby shamael » Fri Mar 17, 2017 10:00 am

Is the Debian server configured as mentioned in the wiki on this side? Various setup can be made to install Deluge so first we have to figure out what's yours (systemV or systemD startup config etc).

I'm not sure so prefer to ask: did you started the deluge-console command on the Debian server? The goal is to connect from an SSH session to the local daemon assuming it works. Do not forget the command need to be run with the same user as the daemon to be able to access it if the wiki was followed. for example, always with the wiki in mind:

Code: Select all

sudo -u deluge deluge-console

if deluge is the correct user

Assuming the deluge-console is able to connect on the server we know Deluge's daemon is working. The second test is the web access, independent from your windows refresh. Review your setup on the Debian server first and assume it works, then tou can take care of the remote access

Racxie
New User
New User
Posts: 3
Joined: Thu Mar 16, 2017 1:23 am
OS or Distro: Windows/Debian

Re: Can't connect Deluge thin client after Win10 refresh

Postby Racxie » Mon Mar 20, 2017 12:24 am

As far as I know it is. I haven't changed anything since it was working apart from the active port, and when I tried comparing the settings to the Wiki I couldn't see anything different.

I'm not sure if mine is SystemV or SystemD, all I can say is that I followed the guidd for installing it on Debian Jessie.

My laptop OS is Windows which has the Thin Client installed, and the server is Debian Jessie which has Deluge installed - I installed the deluge-console on the server and that's where I was getting the errors above.

The user on the server is the same username I have on the thin client, but I just tried your command with my username and I still get the connection refused status.

Might it be worth me uninstalling Deluge on the server and starting again from fresh? Assuming I won't lose my files that way, although I guess I would need to re-add them to carry on being apart of the seed pool? Unless there's a way to uninstall it while keeping that information.

shamael
Seeder
Seeder
Posts: 152
Joined: Sat Oct 08, 2016 9:28 am
OS or Distro: osmc

Re: Can't connect Deluge thin client after Win10 refresh

Postby shamael » Mon Mar 20, 2017 9:48 am

With Debian Jessie systemd is in use, so I suppose you followed this wiki http://dev.deluge-torrent.org/wiki/UserGuide/Service/systemd for the startup of the daemon. The files manually created contain the log location. If you didn't make this part of the setup, you still can.

The user to access the webui/gtk is defined in the auth file, but the daemon on the server can run with a dedicated user. My example was given with the user created in the procedure in the link above. You can check the user with the command.

The Debian Jessie section of the wiki has been upgraded recently. To save your current torrent you only have to keep safe the state located in the user's profile of the daemon. However it seems you don't have a clear picture of your actual setup on the server. Grabbing the info to now how to launch a debug session and how is the daemon launched will be more productive even if you decide to upgrade afterward.


Return to “Support”

Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 4 guests