Nice happy end and your feedback is welcome .
About the guide well it all depends of your level, I admits some parts need background. But you can help . Just register to the site itself and you have the ability to submit change to the documentation. The approval is done by administrators of course but maybe you can present things differently. Join the effort
Can't connect Deluge thin client after Win10 refresh
Re: Can't connect Deluge thin client after Win10 refresh
I'm not sure I'd want to risk messing around with it, I'm far from experienced or knowledgeable enough
I need help again. Deluge was running fine and I was using it last night. Went to look at it again just now and I was back to where I started with the server showing as red and not allowing me to connect/start the daemon - I hadn't done anything to the server.
I'm starting to get the feeling that the process wasn't running in the background for some reason so I checked and everything seemed fine. I thought maybe changing the port would work but that hasn't worked either. I stopped & started the deluged service and still nothing. Edit: I've also just restarted the server and still no luck...
I'm unsure why it crapped out now after all this time, I'm now unsure whether it was ever running in the background, and I'm now unsure how to fix it without reinstalling it again - not something I really want to have to do each time...
I need help again. Deluge was running fine and I was using it last night. Went to look at it again just now and I was back to where I started with the server showing as red and not allowing me to connect/start the daemon - I hadn't done anything to the server.
I'm starting to get the feeling that the process wasn't running in the background for some reason so I checked and everything seemed fine. I thought maybe changing the port would work but that hasn't worked either. I stopped & started the deluged service and still nothing. Edit: I've also just restarted the server and still no luck...
I'm unsure why it crapped out now after all this time, I'm now unsure whether it was ever running in the background, and I'm now unsure how to fix it without reinstalling it again - not something I really want to have to do each time...
Re: Can't connect Deluge thin client after Win10 refresh
:/
I'll say back to the beginning:
-have you followed the systemd service wiki for deluged.service and deluge-web service?
-have you enabled the logging on deluged and deluge-web service
- output of "sudo systemctl status deluged deluge-web -l" ?
-Can you check access on the Debian with deluge-console, confirming it works? then what about the web ui and the GTK (depending your usual way)
Remote access is the second part for me, I just want to confirm the Debian server is well seeing the daemon running without issue.
I'll say back to the beginning:
-have you followed the systemd service wiki for deluged.service and deluge-web service?
-have you enabled the logging on deluged and deluge-web service
- output of "sudo systemctl status deluged deluge-web -l" ?
-Can you check access on the Debian with deluge-console, confirming it works? then what about the web ui and the GTK (depending your usual way)
Remote access is the second part for me, I just want to confirm the Debian server is well seeing the daemon running without issue.
Re: Can't connect Deluge thin client after Win10 refresh
- I followed both the Thin Client guide and the systemd guide
- the only thing I didn't do was enable logging
- Output of sudo systemctl status deluged deluge-web -l (I've replaced my IP address, hostname, & location with <ip>, <host>, <location>):
-I'm unsure how to check access, but ps aux | grep also shows both Deluge & Deluge-web are running. Both ThinClient & Web Client show the status as 'offline', and have both 'start local daemon' and 'connect' greyed out.
The ThinClient which is what I use with this server was running perfectly fine up until the other night and all I did was upload some files to the server after which it stopped connecting so no idea what happened this time..
- the only thing I didn't do was enable logging
- Output of sudo systemctl status deluged deluge-web -l (I've replaced my IP address, hostname, & location with <ip>, <host>, <location>):
Code: Select all
login as: racxie
racxie@<ip>'s password:
Linux <host> 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux
server : 462315
ip : <ip>
hostname : <host>
Last login: Wed Apr 26 22:59:21 2017 from <location>
racxie@<host>:~$ sudo systemctl status deluged deluge-web -l
[sudo] password for racxie:
● deluged.service - Deluge Bittorrent Client Daemon
Loaded: loaded (/etc/systemd/system/deluged.service; enabled)
Active: active (running) since Wed 2017-04-26 07:20:53 CEST; 15h ago
Main PID: 640 (deluged)
CGroup: /system.slice/deluged.service
└─640 /usr/bin/python /usr/bin/deluged -d
Apr 26 07:20:53 <host> systemd[1]: Started Deluge Bittorrent Client Daemon.
● deluge-web.service - Deluge Bittorrent Client Web Interface
Loaded: loaded (/etc/systemd/system/deluge-web.service; enabled)
Active: active (running) since Wed 2017-04-26 07:20:53 CEST; 15h ago
Main PID: 643 (deluge-web)
CGroup: /system.slice/deluge-web.service
└─643 /usr/bin/python /usr/bin/deluge-web
Apr 26 07:20:53 <host> systemd[1]: Started Deluge Bittorrent Client Web Interface.
The ThinClient which is what I use with this server was running perfectly fine up until the other night and all I did was upload some files to the server after which it stopped connecting so no idea what happened this time..
Re: Can't connect Deluge thin client after Win10 refresh
Good start .
1. Is the logging now enabled (+services restarted) in the Debian?
2. Can you install and run deluge-console on the Debian? as the wiki has been followed
if not logged as root in ssh
launch the console as deluge user
3. please share the content (on the Debian)
4. Iptable installed? rules to open the port activated?
To test if a port is open from your Windows you can use telnet or better psping https://technet.microsoft.com/en-us/sys ... 2147217396. The line should be psping server:port
1. Is the logging now enabled (+services restarted) in the Debian?
2. Can you install and run deluge-console on the Debian? as the wiki has been followed
if not logged as root in ssh
Code: Select all
sudo bash
Code: Select all
sudo -u deluge deluge-console
Code: Select all
sudo cat /var/lib/deluge/.config/deluge/core.conf
Code: Select all
sudo cat /var/lib/deluge/.config/deluge/auth
To test if a port is open from your Windows you can use telnet or better psping https://technet.microsoft.com/en-us/sys ... 2147217396. The line should be psping server:port