[Support] binhex - DelugeVPN


Recommended Posts

On 10/1/2021 at 8:23 AM, frodr said:

I am running binhex-nzbget thru binhex-delugevpn. Up till yesterday no problem, then this error message in binhex-nzbget:

 

- TLS certificate verification failed for news.eweka.nl: certificate has expired. For more info visit http://nzbget.net/certificate-verification

 

I downloaded a new conf file from PIA, no change. Before I start the Self signed certificate process, is there another way to fix this?

 

Most happy for any help.

 

 

Im experiencing a similar problem with sonarr and radarr.  We’re you able to find a solution.

Link to comment
11 hours ago, binarymelon said:

Im experiencing a similar problem with sonarr and radarr.  We’re you able to find a solution.

No, I'm sorry. I have to start all over again with binhex-delugevpn as Wireguard. binhex-delugevpn is working, but how do I see that Wireguard setup is working?

Link to comment
On 10/5/2021 at 9:39 PM, JonathanM said:

Can you access it if you set VPN to no?

Sorry to jump in on this response. But my WebUI does not come up. But if I switch it to VPN to no like you requested to the other user, then the WebUI works. I set it back to yes and stops working. However, the container still works with Sonarr and Radarr. Do you by any chance know why this would happen? I believe all I have done is update the container and that’s it. 

Link to comment
50 minutes ago, Tucubanito07 said:

Sorry to jump in on this response. But my WebUI does not come up. But if I switch it to VPN to no like you requested to the other user, then the WebUI works. I set it back to yes and stops working. However, the container still works with Sonarr and Radarr. Do you by any chance know why this would happen? I believe all I have done is update the container and that’s it. 

The typical reason is that your VPN isn't coming up, and until the VPN is up, the app doesn't run for security reasons.

 

The 10,000 unit question is WHY your VPN isn't running. Logs will typically say why, if you can't figure it out you can post them here, just be sure to remove credentials.

Link to comment
54 minutes ago, JonathanM said:

The typical reason is that your VPN isn't coming up, and until the VPN is up, the app doesn't run for security reasons.

 

The 10,000 unit question is WHY your VPN isn't running. Logs will typically say why, if you can't figure it out you can post them here, just be sure to remove credentials.

I don't see anything wrong in the logs.

 

Edit: I deleted the logs.

Edited by Tucubanito07
Link to comment
22 minutes ago, JonathanM said:

Is that all? Doesn't look like it's completed the connection yet in those logs.

Yea. I just got another oven file and the credentials.conf has the NordVPN password I sue to login to the account. Here are the latest logs after getting a new OVPN that is dedicated to Peer to Peer.

 


Edit: I deleted the logs.

Edited by Tucubanito07
Link to comment
2 minutes ago, Tucubanito07 said:

2021-10-07 12:54:06,010 DEBG 'start-script' stdout output:
[warn] Unable to load iptable_mangle module, you will not be able to connect to the applications Web UI or Privoxy outside of your LAN
[info] unRAID/Ubuntu users: Please attempt to load the module by executing the following on your host: '/sbin/modprobe iptable_mangle'

?

  • Like 1
Link to comment
7 minutes ago, JonathanM said:

?

Well that was not there before grrrrrr. @JonathanM I swear I read the whole log and didnt see that. I believe it was the OVPN file I was trying to use that was not Peer to Peer and when I loaded the new one, It connected and threw this error and I didn't see it going through it. 

Well sir, I appreciated your help on this. I have been trying to fix this for the last couple of days. Will I have to do that command again do you happen to know?

Edited by Tucubanito07
Link to comment
1 minute ago, Tucubanito07 said:

Will I have to do that command again do you happen to know?

I've never tried to understood WHY the command is needed or not, so I can't answer the question. All I know is I've never needed it on 3 different machines, ever.

 

When you eventually reboot, check the logs and see. Under "normal" circumstances it's loaded by default, but obviously it gets gone sometimes, somehow.

  • Like 1
Link to comment
1 minute ago, JonathanM said:

I've never tried to understood WHY the command is needed or not, so I can't answer the question. All I know is I've never needed it on 3 different machines, ever.

 

When you eventually reboot, check the logs and see. Under "normal" circumstances it's loaded by default, but obviously it gets gone sometimes, somehow.

Ok awesome thank you so much. I can see it now.

Link to comment
24 minutes ago, JonathanM said:

I've never tried to understood WHY the command is needed or not, so I can't answer the question. All I know is I've never needed it on 3 different machines, ever.

 

When you eventually reboot, check the logs and see. Under "normal" circumstances it's loaded by default, but obviously it gets gone sometimes, somehow.

I don't know much more than what I've read in this thread but my understanding is that its only required if you are connecting to the webui from outside the local network.

 

@Tucubanito07 If you want the install to survive a reboot you need to add this to your go file-

# force iptable mangle module to load (required for *vpn dockers)
/sbin/modprobe iptable_mangle

 

Link to comment
1 hour ago, wgstarks said:

I don't know much more than what I've read in this thread but my understanding is that its only required if you are connecting to the webui from outside the local network.

 

@Tucubanito07 If you want the install to survive a reboot you need to add this to your go file-

# force iptable mangle module to load (required for *vpn dockers)
/sbin/modprobe iptable_mangle

 

Awesome thank you. I will update the go file with this. 

Link to comment
28 minutes ago, Geran said:

Hi,

 

I don't see a list of port forwarding servers in the supervisord.log.

 

How can I get it to show there?

Should show right after a restart of the docker. If you still dont see it attach the log to your next post with user/passwords deleted. Here’s the list if that does you any good-

[info] List of PIA endpoints that support port forwarding:-
[info] al.privacy.network
[info] ad.privacy.network
[info] austria.privacy.network
[info] brussels.privacy.network
[info] ba.privacy.network
[info] sofia.privacy.network
[info] zagreb.privacy.network
[info] czech.privacy.network
[info] denmark.privacy.network
[info] ee.privacy.network
[info] fi.privacy.network
[info] fi-2.privacy.network
[info] france.privacy.network
[info] de-berlin.privacy.network
[info] de-frankfurt.privacy.network
[info] gr.privacy.network
[info] hungary.privacy.network
[info] is.privacy.network
[info] ireland.privacy.network
[info] man.privacy.network
[info] italy.privacy.network
[info] italy-2.privacy.network
[info] lv.privacy.network
[info] liechtenstein.privacy.network
[info] lt.privacy.network
[info] lu.privacy.network
[info] mk.privacy.network
[info] malta.privacy.network
[info] md.privacy.network
[info] monaco.privacy.network
[info] montenegro.privacy.network
[info] nl-amsterdam.privacy.network
[info] no.privacy.network
[info] poland.privacy.network
[info] pt.privacy.network
[info] ro.privacy.network
[info] rs.privacy.network
[info] sk.privacy.network
[info] spain.privacy.network
[info] sweden.privacy.network
[info] sweden-2.privacy.network
[info] swiss.privacy.network
[info] ua.privacy.network
[info] uk-london.privacy.network
[info] uk-southampton.privacy.network
[info] uk-manchester.privacy.network
[info] uk-2.privacy.network
[info] bahamas.privacy.network
[info] ca-toronto.privacy.network
[info] ca-montreal.privacy.network
[info] ca-vancouver.privacy.network
[info] ca-ontario.privacy.network
[info] greenland.privacy.network
[info] mexico.privacy.network
[info] panama.privacy.network
[info] ar.privacy.network
[info] br.privacy.network
[info] venezuela.privacy.network
[info] yerevan.privacy.network
[info] bangladesh.privacy.network
[info] cambodia.privacy.network
[info] china.privacy.network
[info] cyprus.privacy.network
[info] georgia.privacy.network
[info] hk.privacy.network
[info] in.privacy.network
[info] israel.privacy.network
[info] japan.privacy.network
[info] japan-2.privacy.network
[info] kazakhstan.privacy.network
[info] macau.privacy.network
[info] mongolia.privacy.network
[info] philippines.privacy.network
[info] qatar.privacy.network
[info] saudiarabia.privacy.network
[info] sg.privacy.network
[info] srilanka.privacy.network
[info] taiwan.privacy.network
[info] tr.privacy.network
[info] ae.privacy.network
[info] vietnam.privacy.network
[info] au-sydney.privacy.network
[info] aus-melbourne.privacy.network
[info] aus-perth.privacy.network
[info] nz.privacy.network
[info] dz.privacy.network
[info] egypt.privacy.network
[info] morocco.privacy.network
[info] nigeria.privacy.network
[info] za.privacy.network

 

Link to comment

Okay, this is a weird one. Just updated to the latest Firefox on Windows 10 (v93.0), and now I can't log into my Deluge instance. Page loads, and the password dialog box comes up, but entering the password doesn't take and it keeps prompting me for it again. Testing on Edge and Chrome has no issues.

Link to comment

So DelugeVPN had been working fine until sometime in the last week.  Now the UI won't load because the VPN isn't coming up... but the VPN isn't coming but because the wg0 interface won't create:

 

2021-10-07 19:44:32,093 DEBG 'start-script' stdout output:
[info] Attempting to bring WireGuard interface 'up'...

2021-10-07 19:44:32,102 DEBG 'start-script' stderr output:
Warning: `/config/wireguard/wg0.conf' is world accessible


2021-10-07 19:44:32,109 DEBG 'start-script' stderr output:
[#] ip link add wg0 type wireguard

2021-10-07 19:44:32,121 DEBG 'start-script' stderr output:
Error: Unknown device type.


2021-10-07 19:44:32,134 DEBG 'start-script' stderr output:
Unable to access interface: Protocol not supported

2021-10-07 19:44:32,135 DEBG 'start-script' stderr output:
[#] ip link delete dev wg0

2021-10-07 19:44:32,138 DEBG 'start-script' stderr output:
Cannot find device "wg0"

2021-10-07 19:44:32,139 DEBG 'start-script' stdout output:
[warn] WireGuard interface failed to come 'up', exit code is '1'

 

Specifically looks like its having an issue with: ip link add wg0 type wireguard as it errors out with Unknown device type.

 

Any assistance here would be appreciated.  I've searched several times on these forums, general googlefu, read the FAQ on github, and some reddit posts as well but nothing seems to be quite what I'm experiencing.

 

Thank You!

Link to comment
19 hours ago, Caldorian said:

Okay, this is a weird one. Just updated to the latest Firefox on Windows 10 (v93.0), and now I can't log into my Deluge instance. Page loads, and the password dialog box comes up, but entering the password doesn't take and it keeps prompting me for it again. Testing on Edge and Chrome has no issues.

Ended up clearing the cookies for my home domain to clear the issue. Weird...

Link to comment
I guess Docker Hub is not free anymore.
 
Any replacement that is free?
It is free for pushes and pulls (limited) I'm assuming what you are referring to is automated builds on docker hub infrastructure, this is no longer free, check out GitHub workflows instead.

Sent from my CLT-L09 using Tapatalk

Link to comment

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.