-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not connect to Deluge #14
Comments
should be webUI port |
it still fails every time. Is it because deluge doesn't let you set a username? |
I solved it. The deluge GUI doesn't allow you to set credentials, you must add them to the "auth" file in the appdata folder. the format is: the port you enter in seedcross is the daemon port, not the webui port. default is 58846. |
Hello, I am having the same issue. I've tried the WebUI and Daemon ports, I've added a user to the auth file...nothing works. My Deluge is installed on windows and seedcross is in a docker container. |
Same as below. Seedcross on Docker, Deluge daemon on Windows and it won't connect. Booooo - have added to auth file etc etc but no joy. Gonna try installing QB even though that won't work for me as seeding in deluge but at least see if it will connect to a client.
|
Works immediately with authentication on QB :( So it seems to be a Deluge authentication issue. Weird Sage got it working... |
Anyone fixed this in the meantime? Got the same problem, installed both seedcross as deluge in a separate docker containers. Deluge already for a long time never had problems connecting with radarr, sonarr or readarr. localclient:0f7e9ada3c0bc8d2992ec20abffb5a196150c519:10 |
Fixed it!
|
I'm unable to get seedcross to connect to deluge and I'm not sure what the issue is. I get this log every time:
Connecting: 192.168.0.3
Connecting to 192.168.0.3:8112
Could not connect to Deluge 192.168.0.3
Connect failed: 192.168.0.3
Finished of this session
i've tried the webUI port, the network port, and the daemon port and they all fail.
The text was updated successfully, but these errors were encountered: