DJiK

Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by DJiK

  1. That's correct. Thank you so much! Please let me know if I can help by trying out different configuration parameters on my server on your behalf.
  2. Hi @binhex, could you please help me out? I'm trying to run DelugeVPN on a remote server that I have full root access to. The problem is that I cannot access WebUI via the public web when VPN_ENABLED=yes. I.e., "page not found" on http://domain.com:8112. Having read through a lot of posts on this thread, I have narrowed the problem down to: Incorrect LAN_NETWORK settings ifconfig returns the following (somewhat masked) results: docker0 Link encap:Ethernet HWaddr 02:42:87:a1:2a:94 inet addr:172.17.0.1 Bcast:0.0.0.0 Mask:255.255.0.0 inet6 addr: [masked] Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:365588 errors:0 dropped:0 overruns:0 frame:0 TX packets:2189298 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:55260071 (55.2 MB) TX bytes:328364237 (328.3 MB) ens18 Link encap:Ethernet HWaddr [masked] inet addr:11.22.33.239 Bcast:11.22.33.255 Mask:255.255.255.224 inet6 addr: [masked] Scope:Link inet6 addr: [masked] Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:136502544 errors:145 dropped:0 overruns:0 frame:145 TX packets:125433044 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:54284693025 (54.2 GB) TX bytes:27021607924 (27.0 GB) Whereby, I have set LAN_NETWORK to be 11.22.33.224/27, according to this CIDR calculator. Not exposing the port from within Docker As you have recommended to another user, I ran curl http://localhost:8112 from within the server, and it showed the HTML contents of the Deluge UI client. However, other applications that are configured in the same way (as seen with the docker ps command) are properly exposed and are visible to the outside world. This is my first time trying to configure Deluge with VPN. I have signed up with privateinternetaccess™ and even generated a different VPN user a few times to ensure that there are no special characters in either the username or the password -- there weren't any. Lastly, please see my slightly masked supervisord.log attached below. Thanks for all of your help and for this great piece of software! supervisord.log