[SUPPORT] djismGAMING | storm, a self-hosted mobile-friendly webUI for deluge

[djismgaming]

 

Application Name: storm
Application Site: https://github.com/relvacode/storm
Docker Image Repository: https://github.com/relvacode/storm/pkgs/container/storm
Github: https://github.com/relvacode/storm

 

Please post any questions/issues relating to this docker you have in this thread.

 

If you need help but are not using unRAID, then please do not post here, instead head to the application's GitHub repository and open an issue there.

 

PLEASE READ THIS, IMPORTANT TO MAKE THE CONTAINER WORK WITH YOUR DELUGE CONTAINER

 

Introducing Storm

 

A slick remote interface for Deluge that fully supports mobile devices (including as a home-screen app)

 

Some necessary steps:

 

- You'll need a Deluge container running with a valid auth configuration
  as shown here: https://dev.deluge-torrent.org/wiki/UserGuide/Authentication
- Storm needs a way to contact the Deluge RPC daemon so it's best that you
  create a Docker network and attach the Storm container to that network.
- Once that's setup you'll need to configure Deluge to allow remote RPC connections:
  - Open up core.conf in your Deluge configuration folder
    -  set "allow_remote": true

 

Edited April 1, 2022 by @djismgaming (my first unRAID template ever!)

Edited February 27, 2023 by @djismgaming (added Readme from template)

Edited February 27, 2023 by djismgaming
added Readme from template

[g1toncho]

I can not get Storm to connect to my delugevpn container. I've created a new custom network for them to connect on and tried using the IP as hostname, but I keep getting these two errors:

ERROR pool storm/pool.go:217 Failed to establish Deluge RPC connection {"error": "dial tcp 172.19.0.3:58846: connect: connection timed out"}

and

ERROR api storm/api.go:206 Internal Server Error {"Method": "GET", "URL": "/api/plugins", "RemoteAddr": "xxx.xxx.xxx.xxx:55450", "Time": "2022-05-16T12:19:40.638Z", "StatusCode": 500, "ResponseSize": 103, "Duration": "2m12.245713456s", "error": "A connection to the Deluge RPC daemon could not be established by the connection pool"}

 

[djismgaming]

8 hours ago, g1toncho said:

I can not get Storm to connect to my delugevpn container. I've created a new custom network for them to connect on and tried using the IP as hostname, but I keep getting these two errors:

ERROR pool storm/pool.go:217 Failed to establish Deluge RPC connection {"error": "dial tcp 172.19.0.3:58846: connect: connection timed out"}

and

ERROR api storm/api.go:206 Internal Server Error {"Method": "GET", "URL": "/api/plugins", "RemoteAddr": "xxx.xxx.xxx.xxx:55450", "Time": "2022-05-16T12:19:40.638Z", "StatusCode": 500, "ResponseSize": 103, "Duration": "2m12.245713456s", "error": "A connection to the Deluge RPC daemon could not be established by the connection pool"}

 

Try not to use IPs when using a custom docker network.

 

The custom docker network makes it possible, for all containers on it, to address one another via their hostname (container name) http://storm >>>> http://delugevpn.

 

I always try troubleshooting by using

curl

 

On the container console:

 

Enter these commands to see if the containers see each other:

 

apk add curl

 

This will install curl inside the alpine-based storm container.

 

curl delugecontainername:8112

 

This uses curl to get the html response from the deluge container in it's port 8112. Shown in my setup below:

 

 

 

my command in this case was:

 

curl delugevpn:8112

 

Try that to see if the containers see each other in their custom docker network.
Here the explanation of how it works: https://docs.docker.com/network/bridge/

 

Also, be aware that, by default, custom docker networks are not persistent in unRAID.

 

Edited May 16, 2022 by djismgaming

[waymon]

2022-10-16T04:46:18.932Z        INFO    api     storm/server.go:93      Ready to serve HTTP connections on :8221/
2022-10-16T04:46:25.305Z        ERROR   pool    storm/pool.go:217       Failed to establish Deluge RPC connection        {"error": "dial tcp: lookup binhex-delugevpn on 10.0.44.1:53: no such host"}
2022-10-16T04:46:25.305Z        ERROR   api     storm/api.go:206        Internal Server Error   {"Method": "GET", "URL": "/api/plugins", "RemoteAddr": "10.0.44.6:52296", "Time": "2022-10-16T04:46:25.165Z", "StatusCode": 500, "ResponseSize": 103, "Duration": "139.998576ms", "error": "A connection to the Deluge RPC daemon could not be established by the connection pool"}

 

I'm getting the same thing.  What do you mean "Try not to use IPs when using a custom docker network."

 

What additional steps need to be taken?  😀

[djismgaming]

On 10/16/2022 at 12:53 AM, waymon said:

 

I'm getting the same thing.  What do you mean "Try not to use IPs when using a custom docker network."

 

What additional steps need to be taken?  😀

That means that, while using a custom docker network, the container IPs can change but their hostnames wont, which by default are the defined by the container name.

 

Custom docker networks are created on the unraid host CLI by using:

docker network create <networkname>

If you have deluge installed with container name "delugedownloads" then, from any of the other containers on that same custom network, you can

curl delugedownloads:8112

and it will work. IPs on the other hand can change for a variety of reasons.

 

That's why I don't use IPs but hostnames between containers.

 

As an example, if you're going to add Deluge, with container name "delugevpn", as a downloader entry on Sonarr, as long as the two containers are on the same custom docker network, you can add "delugevpn" on the host field. That is possible because the two containers share the same custom docker network.

 

Example below:

 

[waymon]

Still having an issue getting connected.  Are these settings correct?

 

This is my auth file

[djismgaming]

I think the issue you're having is that both containers are just members of the bridge network and not of a custom network.

 

We need to have both containers to be in the same custom network OR instead of "binhex-delugevpn", use the static IP of your machine on the variable "DELUGE_RPC_HOSTNAME".

The custom network, as its shared by any number of containers, will make it so you can do as you did (give just the container name) and it should work. But the default bridge network does not have that capability. (Modified the URL from the quote so it gets you directly to the differences between default/custom bridge docker networks.) User-defined bridges provide automatic DNS resolution between containers.

 

On 5/16/2022 at 5:27 PM, djismgaming said:

Here the explanation of how it works: https://docs.docker.com/network/bridge/#differences-between-user-defined-bridges-and-the-default-bridge

 

Also, be aware that, by default, custom docker networks are not persistent in unRAID. (SETTINGS > DOCKER > ADVANCED VIEW)

 

 

Edited October 31, 2022 by djismgaming

[waymon]

I created a custom network but neither my deluge or storm container would start.  They would just fail.

I changed it to the IP and now I am getting this error below.  Why is it trying to connect to .103:60937 ?  Where is it getting those numbers?

 

2022-10-31T14:04:50.568Z        INFO    api     storm/server.go:93      Ready to serve HTTP connections on :8221/
2022-10-31T14:04:58.859Z        ERROR   pool    storm/pool.go:217       Failed to establish Deluge RPC connection        {"error": "RPC error BadLoginError('Password does not match')\nTraceback: Traceback (most recent call last):\n  File \"/usr/lib/python3.10/site-packages/deluge/core/rpcserver.py\", line 275, in dispatch\n    ret = component.get('AuthManager').authorize(*args, **kwargs)\n  File \"/usr/lib/python3.10/site-packages/deluge/core/authmanager.py\", line 121, in authorize\n    raise BadLoginError('Password does not match', username)\ndeluge.error.BadLoginError: Password does not match\n"}
2022-10-31T14:04:58.859Z        ERROR   api     storm/api.go:206        Internal Server Error   {"Method": "GET", "URL": "/api/plugins", "RemoteAddr": "10.0.44.103:60937", "Time": "2022-10-31T14:04:58.827Z", "StatusCode": 500, "ResponseSize": 103, "Duration": "32.771232ms", "error": "A connection to the Deluge RPC daemon could not be established by the connection pool"}
2022-10-31T14:05:35.647Z        ERROR   pool    storm/pool.go:217       Failed to establish Deluge RPC connection        {"error": "RPC error BadLoginError('Password does not match')\nTraceback: Traceback (most recent call last):\n  File \"/usr/lib/python3.10/site-packages/deluge/core/rpcserver.py\", line 275, in dispatch\n    ret = component.get('AuthManager').authorize(*args, **kwargs)\n  File \"/usr/lib/python3.10/site-packages/deluge/core/authmanager.py\", line 121, in authorize\n    raise BadLoginError('Password does not match', username)\ndeluge.error.BadLoginError: Password does not match\n"}
2022-10-31T14:05:35.647Z        ERROR   api     storm/api.go:206        Internal Server Error   {"Method": "GET", "URL": "/api/plugins", "RemoteAddr": "10.0.44.103:60956", "Time": "2022-10-31T14:05:35.636Z", "StatusCode": 500, "ResponseSize": 103, "Duration": "10.539642ms", "error": "A connection to the Deluge RPC daemon could not be established by the connection pool"}
2022-10-31T14:09:24.064Z        ERROR   pool    storm/pool.go:217       Failed to establish Deluge RPC connection        {"error": "RPC error BadLoginError('Password does not match')\nTraceback: Traceback (most recent call last):\n  File \"/usr/lib/python3.10/site-packages/deluge/core/rpcserver.py\", line 275, in dispatch\n    ret = component.get('AuthManager').authorize(*args, **kwargs)\n  File \"/usr/lib/python3.10/site-packages/deluge/core/authmanager.py\", line 121, in authorize\n    raise BadLoginError('Password does not match', username)\ndeluge.error.BadLoginError: Password does not match\n"}
2022-10-31T14:09:24.064Z        ERROR   api     storm/api.go:206        Internal Server Error   {"Method": "GET", "URL": "/api/plugins", "RemoteAddr": "10.0.44.103:61176", "Time": "2022-10-31T14:09:24.054Z", "StatusCode": 500, "ResponseSize": 103, "Duration": "10.38151ms", "error": "A connection to the Deluge RPC daemon could not be established by the connection pool"}

 

[djismgaming]

I see you have a DELUGE_RPC_PORT variable on Storm. THat is not on the latest version.

You may be using an outdated template.

Try to remove it by deleting the container completely, going into "add container" and select storm from the container list and then press the X on the side of the template name:

 

 

You can also delete them directly from the flash drive from: Flash\config\plugins\dockerMan\templates-user.

Then install from the CA again from scratch.

 

Also "10.0.44.103:61176" may be your client PC's IP as Storm uses your IP to communicate. Those ports are randomly selected for outgoing communication from Storm with your PC. It's normal.

 

But the error itself is telling you that the passwords do not match.

 

Try removing the spaces/new lines on the end of the file. I have no new lines and it works.

Make sure you're saving the auth file in LF line breaks and not CRLF.

vscode example:

Edited October 31, 2022 by djismgaming

[waymon]

Thanks. The extra lines was it.  Appreciate the help!

Looking forward to using this. 

[djismgaming]

Glad to be of help  

[waymon]

I have over 1000 torrents.  I’d like to sort by “added” but without having to scroll to the bottom.  Can you add “reverse added” ?

 

thanks

[djismgaming]

I’m not the application developer. Sorry. I just created the template for the CA in unraid. 
 

you can try the application url in the original post and open an issue on it. 
 

the developer may help. 

[Wadert3]

I know this is an old thread but was hoping I could get a little assistance. Love the UI. I just got it installed and running on the docker along side deluge and can access it but it seems to be stuck in a perpetual loading state and doesnt allow me to add any torrents, is that an issue with it not connecting to deluge properlyI know this is an old thread but was hoping I could get a little assistance. Love the UI. I just got it installed and running on the docker along side deluge and can access it but it seems to be stuck in a perpetual loading state and doesnt allow me to add any torrents, is that an issue with it not connecting to deluge properly

[djismgaming]

I've not had this one myself as I just tried both and are working correctly in my setup (although not my daily torrent/webui apps).

 

We'll need a little more data to help you out. How does your docker template look for the apps you use (torrent/storm webui)?

 

Edited February 24, 2023 by djismgaming

[Wadert3]

Storm:

 

Deluge:

[djismgaming]

I think I see your issue. 
 

I don’t know if hostname resolution works on the br0 network on unraid. You can create a custom docker network for that I guess. I need to test in the br0 network though. 
 

Also, are those user/password setup in the deluge container itself on appdata/deluge/auth file? (“deluge” being the directory where the deluge config resides)

Edited February 24, 2023 by djismgaming

[Wadert3]

Switched to a custom network and yes the user and pass are setup in the auth file heres a screenshot as an example

Still getting a load and it doesnt look like theres any connection to the main app. Heres what Im seeing in storm:

[djismgaming]

I'm setting up the same on my side to see. I've never used this br0 network so that will give me some insight.

[djismgaming]

OK, I see an issue with the br0 network.

 

This network is in your home subnet 192.168.0.0/24. This means the container will take an IP from your router (or DHCP server) via DHCP. The hostname resolution in docker will not function correctly.

 

In your case it would be better to use a user-set custom docker network for this connection. (that will entail having all other apps that need connection to deluge in that same user created custom network) That is done via:

 

docker network create <name of network here>

 

For that to stick on reboot/array restart, you'll need to go to Settings > Docker > advanced view > Preserve user defined networks to YES.

 

Another way would be to set both containers in the Bridge network (the containers will use your server IP) and use, in storm, the IP of your unraid server. (The way I have it setup for testing)

 

Edited February 27, 2023 by djismgaming

[djismgaming]

If you want to continue using br0, then set a specific static IP for the deluge container in the "Fixed IP address". Then in storm, use that as the DELUGE_RPC_HOSTNAME.

Edited February 27, 2023 by djismgaming

[djismgaming]

I've done more testing and I can most certainly say, the linuxserver container, somehow, does not work with storm. No issues with the binhex-deluge one.

Weird indeed. 

 

Can you try with the binhex-deluge one on your side and let me know?

 

I've tried the linuxserver version in the br0, in a custom set network (via command: docker network create test), set that test network on both containers, allso using the Bridge network. Everytime I just get the spinning wheel as you do.

Edited February 27, 2023 by djismgaming

[djismgaming]

Finally found the culprit in the testing.

 

In the notes on the container template there is this line:

 

- Once that's setup you'll need to configure Deluge to allow remote RPC connections:
  - Open up core.conf in your Deluge configuration folder
    -  set "allow_remote": true

 

That was my issue on testing. Can you check if you followed that step? Remember to stop the deluge container while doing this change in the file. After the change, then start the container.

 

It works now with the linuxserver image. Before, I was getting all these "connection refused" in storm's logs:

 

Edited February 27, 2023 by djismgaming

[Wadert3]

Sorry for getting back to you so late, havent been on my server for a while. It looks like that did it! Great fix It looks like it working perfect after switching the networks and getting a forced update. You the man!

[djismgaming]

Glad to be of help