-
Notifications
You must be signed in to change notification settings - Fork 84
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
seedbox.io strangely not supported #125
Comments
This may be because their setup uses digest authentication while Electorrent only supports basic authentication. Similar to #90 and #97. Adding digest authentication is a planned feature. If you can confirm that Seedbox.io in fact uses digest authentication, please get back to me. Then we have a definite solution. |
Thank you I will contact them right away |
You were right my friend. Here is the confirmation from seedbox.io.
|
I will see if I can find some time to implement this feature, busy times at the moment though. |
Has it been fixed? I can't manage to setup it with seedbox.io and I found this thread, but on recent thread I have read that digest authentication is now supported. |
I don't use seedbox.io hence I can't test it. Digest authentication has been implemented, which should provide the features necessary to support this. In Electorrent, I would try to fiddle with the path option. Once you find that path where the XML-RPC is available, it should work. Sometimes this path is |
Not sure if this has already been answered elsewhere but to anyone who stumbles upon this, |
hey am trying to connect to seedbox.io with Electorrent... ok...solved....apparently its port:443 |
I am very happy with Seedbox.io and they uses rTorrent but they said that currently their setup is not supported by Electorrent even thought they first thought it would be no problems and that their users had used it in the past.
They really tried giving me all the support they could think of like setting my RCP path "/RPC/24344/" and other stuff. (great guys) But it just keeps spinning and spinning and never connects. (no problems on my end with firewall or anything)
Ultimately after having a engineer doing some hands on test they came to the conclusion that
I know it's their setup and that they could fix it somehow i guess. But maybe something could be done from the developing end so that more configs would work. Like theirs for example
The text was updated successfully, but these errors were encountered: