Can only access WebUI from one computer

[important]

I am quite new to using deluge and even more so synology, where I am running deluge. I've managed to set up deluge in a container and everything works fine except that I can't access the WebUI from any other computer than my desktop where everything works fine. Using 192.168.0.XX:8112 and the webui shows up and I can log in with default password. But if I try to do the same thing using my laptop, GFs laptop or my phone for example - it just times out.

Not sure what I've done wrong or what I can do to fix this. In the core.conf file I have "allow_remove" set to True. Any ideas for someone who is quite new to all this? I have no need to access the webui from outside the local network but I would like to be able to access it from any computer on the local network. Thanks!

[mhertz]

You didn't mention auth file, so if haven't already, then follow the official thinclient guide: https://dev.deluge-torrent.org/wiki/Use ... ThinClient

Edit: Also, both ends needs same major version number for client/daemon, so v2.x or v1.x.

[important]

You didn't mention auth file, so if haven't already, then follow the official thinclient guide: https://dev.deluge-torrent.org/wiki/Use ... ThinClient

Edit: Also, both ends needs same major version number for client/daemon, so v2.x or v1.x.

I've tried looking at that guide and I added a user according to it. But makes not difference. I don't understand how adding a user there would help since I guess this has to do with login for loging into the webui? I can't even reach the webui with the IP address.

With that being said I don't even understand why my desktop computer works since it's not the one hosting deluge. My auth file looks like this:

Code: Select all

localclient:4b7c45471d950d383e76bff8ad613b30a2ea80b4:10
USERNAME_REMOVED:PASS_REMOVED:10

With the first line being there from the start. Second one is the one I tried adding.

[shamael]

It sounds more like an network issue here (route, fw restriction, etc). From the working computer a ping should work hence a TCP ping on the dedicated port 8112 should work too (psping or anything similar to do a tcpping). If it doesn't work from another computer check the network configuration and your router. Maybe the container too and the iptable. There is a restriction but you need to nail it down

[mhertz]

Just wanted to say sorry to OP for impropper help, I was little to quick there and didn't thought it through properly, but good shamael could come with some good advice for you to follow/think-about instead!

[important]

It sounds more like an network issue here (route, fw restriction, etc). From the working computer a ping should work hence a TCP ping on the dedicated port 8112 should work too (psping or anything similar to do a tcpping). If it doesn't work from another computer check the network configuration and your router. Maybe the container too and the iptable. There is a restriction but you need to nail it down

After adding the second line to the auth file and restarting the container, using psping worked and apparently also connecting to the webui. I am not sure if this fixed the problem permanently or if its just randomly worked this time around and might stop working in the future. But if it does I will try to look into your suggestion more.

I also find it strange why adding that line to the auth file would fix it which is why I am not sure it's permanently? The login still looks the same as on my desktop and I can't use the username/password that I added to login, only the default 'deluge' one.

Thanks!

[important]

Just wanted to say sorry to OP for impropper help, I was little to quick there and didn't thought it through properly, but good shamael could come with some good advice for you to follow/think-about instead!

Any suggestions is better than none I appreciate it

[shamael]

Just wanted to say sorry to OP for impropper help, I was little to quick there and didn't thought it through properly, but good shamael could come with some good advice for you to follow/think-about instead!

Any suggestions is better than none I appreciate it

Could not agree more

[shamael]

It sounds more like an network issue here (route, fw restriction, etc). From the working computer a ping should work hence a TCP ping on the dedicated port 8112 should work too (psping or anything similar to do a tcpping). If it doesn't work from another computer check the network configuration and your router. Maybe the container too and the iptable. There is a restriction but you need to nail it down

After adding the second line to the auth file and restarting the container, using psping worked and apparently also connecting to the webui. I am not sure if this fixed the problem permanently or if its just randomly worked this time around and might stop working in the future. But if it does I will try to look into your suggestion more.

I also find it strange why adding that line to the auth file would fix it which is why I am not sure it's permanently? The login still looks the same as on my desktop and I can't use the username/password that I added to login, only the default 'deluge' one.

Thanks!

From my experience the auth file is used by the GTK client, as the parameter "allow_remote: true" in core.conf file.
I configured it to use the fat client but the access through the webui is apart, meaning I had to change it there too otherwise "deluge" user remains.