Jump to content
binhex

[Support] binhex - DelugeVPN

6105 posts in this topic Last Reply

Recommended Posts

I had the GUI running fine for 2 days, but I added a static ip OpenVPN config file, restarted my unRAID server, and now can't load the GUI. Log just shows this error:

 

twisted.internet.error.CannotListenError: Couldn't listen on 0.0.0.0:8112: [Errno 98] Address already in use.

 

I tried removing the Docker and reinstalling, but getting the same error. Any tips? And no, I'm not running another instance of the docker AFAIK.

Edited by BBLV

Share this post


Link to post
5 hours ago, BBLV said:

I had the GUI running fine for 2 days, but I added a static ip OpenVPN config file, restarted my unRAID server, and now can't load the GUI. Log just shows this error:

 

twisted.internet.error.CannotListenError: Couldn't listen on 0.0.0.0:8112: [Errno 98] Address already in use.

 

I tried removing the Docker and reinstalling, but getting the same error. Any tips? And no, I'm not running another instance of the docker AFAIK.

there is only ever one reason for the above message, and that is the port being in use by another plugin/container/vm, your choice is change the port on the host side to be something different to 8112 (8113 for example) for this container or find out what is listening on port 8112 and shut it down or change that to something else.

Share this post


Link to post
19 hours ago, BBLV said:

Should my Deluge "Incoming Port" match the port specified in my OpenVPN config file? i.e. OpenVPN has port 1194

thats not the incoming port, thats the port for the vpn endpoint not the same thing at all.

 

19 hours ago, BBLV said:

Could this be the cause of me not being very connectable?

no, see Q6. for info on that:-

 

https://forums.unraid.net/topic/44108-support-binhex-general/?tab=comments#comment-433613

 

Share this post


Link to post
4 hours ago, binhex said:

there is only ever one reason for the above message, and that is the port being in use by another plugin/container/vm, your choice is change the port on the host side to be something different to 8112 (8113 for example) for this container or find out what is listening on port 8112 and shut it down or change that to something else.

The only other docker I have is your PlexPass docker (port 32400, WebGUI works just fine) and I'm still getting the "Address already in use error". I've cleared cache, reinstalled the docker, restarted my router, restarted my server, can't figure it out. Any way to clear all docker/port data and start fresh - do I just uninstall and delete the appdata folder for delugevpn?

Share this post


Link to post
7 minutes ago, BBLV said:

The only other docker I have is your PlexPass docker (port 32400, WebGUI works just fine) and I'm still getting the "Address already in use error". I've cleared cache, reinstalled the docker, restarted my router, restarted my server, can't figure it out. Any way to clear all docker/port data and start fresh - do I just uninstall and delete the appdata folder for delugevpn?

try this, issue the following via the console of the host (not the containers console):-

 

docker ps | grep 8112

it will display containers that are running that are using port 8112.

Share this post


Link to post
17 minutes ago, binhex said:

try this, issue the following via the console of the host (not the containers console):-

 


docker ps | grep 8112

it will display containers that are running that are using port 8112.

Here's the result

dockerps.png

Share this post


Link to post
1 minute ago, BBLV said:

Here's the result

dockerps.png

so there ya go you already have this container running, and its using port 8112 as expected, thats why you cant create another container with the same port, so either work out why this isnt working or delete it and create a new container, my advise is to try and work out why you cant access the web ui for the existing container, if you want to do this then follow the steps in the link below:-

 

https://forums.unraid.net/topic/44108-support-binhex-general/?do=findComment&comment=435831

 

 

Share this post


Link to post
43 minutes ago, binhex said:

so there ya go you already have this container running, and its using port 8112 as expected, thats why you cant create another container with the same port, so either work out why this isnt working or delete it and create a new container, my advise is to try and work out why you cant access the web ui for the existing container, if you want to do this then follow the steps in the link below:-

 

https://forums.unraid.net/topic/44108-support-binhex-general/?do=findComment&comment=435831

 

 

That was with the docker running. As soon as I stop the docker and run the same command line, it returns nothing. Here is the screenshot - first line is without the docker running, second line is WITH the docker running.

 

I also included a screenshot of my docker page for reference. Maybe something funky is going on (this is my first dive into unRAID and I'm just figuring out all of its quirks and nuances, but have watched an insane amount of YT videos and spent hours upon hours in the forums researching).

 

Thanks for all the help binhex, donation coming your way!

docker screen1.png

dockerps2.png

Share this post


Link to post
2 minutes ago, BBLV said:

Here is the screenshot - first line is without the docker running, second line is WITH the docker running.

 

yeah completely expected, if you grep for port 8112 with the container stopped then it wont match anything (and thus nothing is returned), if you start the container then it will return something as the port is listening and thus a grep (match) is found for port 8112.

Share this post


Link to post
12 minutes ago, BBLV said:

Maybe something funky is going on

According to your screenshot, you've got the same port mapped three times in your container settings (port 58846).  That doesn't look right.

Share this post


Link to post
1 minute ago, Cessquill said:

According to your screenshot, you've got the same port mapped three times in your container settings (port 58846).  That doesn't look right.

no he doesnt, he has 58846 mapped once and 58946 mapped twice (tcp and udp) completely normal.

Share this post


Link to post
2 minutes ago, binhex said:

no he doesnt, he has 58846 mapped once and 58946 mapped twice (tcp and udp) completely normal.

Apologies - I stared at that for ages and still missed it.  Long day.  Didn't help that I checked against mine on a mobile phone and don't have 58946 mapped.

 

As you were...

Share this post


Link to post
2 minutes ago, Cessquill said:

Apologies - I stared at that for ages and still missed it.  Long day.  Didn't help that I checked against mine on a mobile phone and don't have 58946 mapped.

 

As you were...

lol no apology required 🙂

Share this post


Link to post
18 hours ago, l3gion said:

Hi everyone,

 

Maybe a stupid question, but can someone explain me why the eth0 and tun0 values diverge? Should't they kind be the same, since tun0 goes through eth0?

 

See attached image. This was from the binhex-delugevpn console.

 

Thanks.

eth0-vs-tun0.png

Any idea anyone? @binhex maybe?

Thanks.

Share this post


Link to post
1 hour ago, binhex said:

so far i see no problems, time to dig into it, do the following procedure in the link below:-

 

https://forums.unraid.net/topic/44108-support-binhex-general/?do=findComment&comment=435831

 

I'll perform this when I get home this evening. One thing I was thinking about is that it worked just fine (I just wasn't connectable) until I added the new Windscribe Static IP OpenVPN config file. Nothing else changed. Would that have anything to do with the internal app port being buggered?

Share this post


Link to post
1 hour ago, BBLV said:

One thing I was thinking about is that it worked just fine (I just wasn't connectable) until I added the new Windscribe Static IP OpenVPN config file. Nothing else changed. Would that have anything to do with the internal app port being buggered?

i would suspect the ovpn file you have downloaded is either corrupt or simply badly formed, this in turn will mean the vpn tunnel cannot be established, and this is turn means the app cant start (designed not to start until tunnel is running) and thus cannot be accessed via the web ui.

Share this post


Link to post
1 hour ago, l3gion said:

Any idea anyone? @binhex maybe?

Thanks.

completely normal:-

tun0 = vpn traffic only

eth0 = vpn traffic (tunnel runs over eth0) AND all local traffic (web interface, api calls from sonarr etc).

Share this post


Link to post
18 hours ago, seventhaxis said:

Just got this docker installed and working, but I'm having issue adding torrents. When adding via File, the upload fails. When attempting to add via URL, it also fails to download the .torrent content and add to the system. The only way I've found so far is to stop the docker, add the .torrent file to a folder which auto-imports into Deluge, then start the docker again and manage the newly added torrents.

 

Any help with this is greatly appreciated.

@BBLV Thanks for the suggestion. I'll remember that one but I'm trying to stay away from all things Google.

 

@binhex Any ideas what I should try or what could be wrong? Or is it working as expected?

Share this post


Link to post

Hello, Been trying to get this to work for a while.  I bash in to the container and the VPN is working but Deluge is not accessible.  I need a new set of eyes on it.  There is so much information I cannot parse it all.  Thank you.

supervisord.log

Share this post


Link to post
3 hours ago, binhex said:

completely normal:-

tun0 = vpn traffic only

eth0 = vpn traffic (tunnel runs over eth0) AND all local traffic (web interface, api calls from sonarr etc).

Thanks for getting back to me. I imagined it could be all the local traffic on deluge. Now I'm just surprised at the amount of data transfered locally from the web interface, sonarr, radarr and jackett. 10gb download and 6gb upload over a couple of days 😅

Share this post


Link to post
9 hours ago, binhex said:

so far i see no problems, time to dig into it, do the following procedure in the link below:-

 

https://forums.unraid.net/topic/44108-support-binhex-general/?do=findComment&comment=435831

 

Here's my supervisord log file. FYI I switched back to the non-static ip OpenVPN config that previously worked - no longer working and kicking back that same "address already in use" error in the log. Something must be jammed up somewhere indicating that the container is already running and therefore the 8112 port is blocked/in use. Looking forward to your feedback.

supervisord.log

Share this post


Link to post
10 hours ago, BBLV said:

Here's my supervisord log file. FYI I switched back to the non-static ip OpenVPN config that previously worked - no longer working and kicking back that same "address already in use" error in the log. Something must be jammed up somewhere indicating that the container is already running and therefore the 8112 port is blocked/in use. Looking forward to your feedback.

supervisord.log

hmm ok so it looks like its twisted (python module) that is reporting the port clash, lets have a look at your deluge config file then, can you attach /config/core.conf here.

Share this post


Link to post
1 hour ago, binhex said:

hmm ok so it looks like its twisted (python module) that is reporting the port clash, lets have a look at your deluge config file then, can you attach /config/core.conf here.

Here's my core.cong and a screenshot of my delugevpn folder (directory and duplicate files normal?).

core.conf

delugevpn folder.png

Share this post


Link to post
41 minutes ago, BBLV said:

Here's my core.cong and a screenshot of my delugevpn folder (directory and duplicate files normal?).

core.conf

delugevpn folder.png

yep so this is your issue, in the file core.conf line 59 to 62 you have somehow got the incoming port set to the same port number as the web interface, as in port 8112, so when deluge-ui tries to start it starts the web ui on port 8112 (separate process to deluge), then deluged reads the core.conf and attempts to set the incoming port to 8112, which it cant cos its already in use by the web interface and then blows up.

 

here is the misconfigured section:-

 

  "listen_ports": [
    8112, 
    8112
  ], 

 

so the fix is stop the container, and set it to the following, do NOT use windows notepad, use notepad++ or atom:-

 

  "listen_ports": [
    1234, 
    1234
  ], 

save the file and then start the container.

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.