Deluge remote client
Set up deluge on synology (2020)
Hello, first and foremost, I’d like to express my gratitude for this app! I’ve successfully integrated it with sonarr and radarr, but deluge on my remote seedbox is causing problems. I’m trying to connect to https://user:[email protected]:port, but it’s not working. I was able to connect to it using transdrone with the same credentials; the only difference being that instead of defining the URL, transdrone asked me to enter information into different fields. Another feature in transdrone that I had to enable or else it wouldn’t attach was an option called “All SSL certificates should be accepted. Enable any thumbprint to attach to any other thumbprint.”
I’ve had the same problem. I have to manually open Deluge in the browser, login, and then it pulls up fine in NZB after that. However, once the session has ended, it will not connect until I login with a browser again.
Often, make sure the password is right. You’ll need to enable the WebUi plugin on the thin client for this to work. I couldn’t get the plugin to work over the web ui address for a seed box (SErver>/user/deluge), so I used the thin client. It should auto-connect once activated, as it does for things like sonarr. I’m hoping it doesn’t give me a session timeout.
How to use deluge webui on linux
Then check that the daemon is running by going to the Connection Manager on the media center’s Deluge and clicking Start Daemon and connecting locally (you might need to switch off Classic Mode under Preferences -> Interface first).
Also, make sure the port on your router is redirected to your media center (if you’re not sure how to do this, give me your router’s make/model and I’ll try to find instructions). If you just want to run the WebUI (Preferences -> WebUI), remember to do this for the port number, but first try to get regular connections working.
How to access your torrents remotely!
Deluge is an open source BitTorrent client with a lot of features. Its backend is based on libtorrent, and it has several user interfaces. The client-server model was used to build it. The Deluge daemon can run on the server and handle all bittorrent operation, while user interfaces can communicate from any device remotely.
SSH tunneling is not needed if you are on a trusted local network since all communication between the GTK UI and the daemon is encrypted using an automatically created self-signed certificate. And if you’re connecting to the daemon over the internet, you can use an SSH tunnel.
For Deluge’s WebUI, HTTPS or HTTP is an either/or situation; you can access the WebUI through HTTP or HTTPS. Since you’ll be creating a self-signed certificate for this, your web browser will report the link as unsafe.
How to setup deluge daemon on headless server
My god, I’m feeling so dumb right now…
Deluge remote guide – how to access your torrents remotely
I was able to resolve the above problem within minutes of posting it. However, after walking in circles for a few days, this has caused me a great deal of irritation. When I double-checked the allow remote setting in the C:config locationcore.conf file, I discovered that it was always set to “false.” To put it another way, I’d use NSSM to interrupt the services (deluged-debug.exe & deluge-web-debug.exe). Using a text editor, manually set allow remote to “real” in C:config location, save the changes, close the file, and then restart the services (deluged-debug.exe & deluge-web-debug.exe) through NSSM. The allow remote setting will revert to “false” each time. The solution… Using the Deluge thin-client Interface connected to 127.0.0.1:58846 on the server, allow remote connections. as well as now… When I open the link manager on the remote computer, I’m greeted by a lovely green circle. Hopefully, this will help someone else who is looking for a solution to the same problem. Here’s how it works: