UI not accessible

[smilin229]

I've setup and configured this docker image, but am having problems accessing the web ui. When looking in STDOUT I find the following error repeating. I have verified the credentials, but its still not authenticating.

[dreamcat4]

enable shell script trace with debug=true environment variable.

https://github.com/dreamcat4/docker-images/blob/master/deluge-pia/services.d/pia_update_listen_port/run#L3

you can also try runing manually the curl command to the pia api. By substituting those other $vars in the lines:

https://github.com/dreamcat4/docker-images/blob/master/deluge-pia/services.d/pia_update_listen_port/run#L20-L30

[smilin229]

I ran the following:

curl --interface tun0 -s -d user=[user-removed]&pass=[password-removed]&client_id=16201327e38e0e28ccb1727bff539357&local_ip=10.2.10.6 https://ww w.privateinternetaccess.com/vpninfo/port_forward_assignment

The result was:

[1] 12973
[2] 12974
[3] 12975
bash: https://www.privateinternetaccess.com/vpninfo/port_forward_assignment: No such file or directory`

The debug also shows a trailing space after the username, I have deleted the pw file, and recreated it using notepad++ but the trailing space is still there.

[smilin229]

Looking intot he 404 error, I believe https://www.privateinternetaccess.com/helpdesk/kb/articles/can-i-use-port-forwarding-without-using-the-pia-client has the answer. the url I believe has changed to http://209.222.18.222:2000/

[dreamcat4]

notepad++ is a windows text editor right? well the windows CR LF is not correct for unix. Maybe this extra newline is the extra space you see at the end of your password?

[smilin229]

Thanks for the heads up. Notepad++ is usually better with unix files. I have docker running on a synology nas, so deleted the file, and installed nano, then recreated it. Now its working fine, but not on the port I set. A minor issue, but I can live with it

[dreamcat4]

This bit:

2020-06-04 13:21:49 | stdout | + socat tcp4-listen:58846,bind=192.168.1.95,fork tcp:localhost:58846
-- | -- | --

@smilin229 yes now i remember... my image uses socat program here to forwards the local LAN side port, this bit:

https://github.com/dreamcat4/docker-images/blob/master/deluge-pia/services.d/deluge/run#L61-L75

which uses from other included file:

https://github.com/dreamcat4/docker-images/blob/master/deluge-pia/services.d/_includes/helpers.sh#L28-L64

So perhaps your issue is something going wrong in there.

I cannot remember the specifics. But perhaps the reason for that [more complicated] code there is because the container has multiple network interfaces active... so it is to ensure that deluge does not bind to 0.0.0.0 by default which would then bind admin / webgui / daemon ports on to all of the active interfaces of the container. But you only want your LAN side bound to the interface that connects to your local LAN. And not also on to the WAN side.

[dreamcat4]

However you also may have some settings in deluge itself. In regards to the daemon port, which IP to bind to for which service, etc. So you probably want to have the container's deluge_daemon_port to match what is in your deluge configuration settings. Otherwise that call to socat on localhost to forward the port will fail to work since it's not forwarding the correct port anymore.