thatsthefrickenlightning

Thanks for taking the time to let us know. Would it be wise to stop binhex containers in the meantime?

Installed as a precaution. Thank you!

Update: I was in the process of reporting the bug and now I'm not getting the NAT-PMP error. QBVPN is working fine. Will observe the situation and come back if the error returns.

Same problem here. I'll contact them tomorrow morning. cc @VRA and @krazytaco It's laudable how much support binhex provides for these free containers. So if you haven't already: BUY HIM A COFFEE.

Hello, May I suggest adding a notification to this plug-in to warn users who are still using the old AppData Backup plug-in? I only recently updated from 6.11.5 to 6.12.x (6.12.1 is the cut-off) and only today did I realize a backup hasn't been run since that upgrade (~1mo). I'm having some cache drive trouble right now and could have really used some recent backups.

After reading up on the developments on this front: thank you! Both for the work and the info supply.

Do what you want of course, but you're aware PIA has been bought by a company with a less than stellar reputation? E: Sorry, never got back to you on this one. The connection tends to be spotty at times, but the tunnel and port forwarding also recover on their own. With this being a service that's on 24/7 but not actively used 24/7, I don't mind there being some downtime here and there. I'm sure the fault is with Proton and them being overloaded at times.

Working fine for now. Guess the unavailable service errors are just that: Proton's server being overloaded.

Thanks for the documentation. I successfully added ProtonVPN to the list of VPN Providers and enabled it. One thing that had me confused was appending '+pmp' to my VPN username in the container parameters. I'm on Wireguard so the wg0.conf file contains all the VPN login info needed, right? I wouldn't even know what to put there. My Proton username? The private key from the conf file? I ended up just entering +pmp and nothing else in that field and the system works. Another snag I ran into is that the logs say my chosen server doesn't support port forwarding, but it did have the arrows icon. I generated another config file with a different server and it's now working, so that was probably a gaffe on Proton's end. Thanks again! EDIT: weird, after an initial connection and everything working fine, the tunnel seems to die and it says NAT-PMP is not supported. But before that, a port is established just fine, Privoxy works and the trackers report me as connectable. It starts with not being able to resolve google.com and then.. 2023-07-09 DEBG •watchdog-script' stdout output: Having issues resolving name Retrying in 5 secs... 9 retries left 22:09:49, 141 DEBG •start-script' stderr output: readnatpmpresponseorretry() failed : the gateway does not support nat-pmp errno=11 'Resource temporarily unavailable ' I can upload a full supervisord.log if you want.

I wish you'd said something! I would have gladly provided you with configuration files for Proton VPN. Anyway, glad it's to your satisfaction, then I'm sure it will be to mine as well.

Binhex, that's absolutely great, thank you so much! I haven't had a chance to tinker with it more and the job just got a whole lot easier. I'll buy you some more beers in a bit.

Apologies! I didn't see that section of the how-to. I'll walk through that when I'm home from work. I'm sure that's the missing piece to get QBVPN working, albeit with some extra manual work required after every container restart. Something something gift horse, of course. @st34m, I got natpmpc installed without issue. As Binhex said, I suspect you entered the commands in Unraid's terminal instead of the container's.

This is what I get when I enter 'natpmpc' after installing it in the container's console. QB is working fine at this point, just not connectable. initnatpmp() returned (SUCCESS) using gateway: 172.17.0.1 sendpublicaddressrequest returned 2 (SUCCESS) readnatpmpresponseorretry returned -7 (FAILED) readnatpmpresponseorretry() failed: the gateway does not support nat-pmp errno-111 'Connection refused' But we may not need to get into that all the way. There's another container (Gluetun) that just added support for Proton VPN port forwarding (which I suspect just means it supports NAT-PMP port forwarding). A few thoughts on this: Seeing as Gluetun works with an MIT license, could this situation be as simple as just copying Gluetun's work with some changes to fit your container? Or, as a stop-gap fix, I can point the QBVPN container to Gluetun for its network access. I'm no expert, but I've always felt reassured by your iptables approach to prevent leaks. Does Gluetun sound like it has similar reliability? They say the following about this feature: I'm no big fish but I do like my privacy. Many thanks.

Any and all work is appreciated. I believe I donated to you in the past but I'll have to do so again given how much I use your software. In the meantime, can you clue me in as to how to discover the NAT-PMP forwarded port for manual entry? E: I suspect with the excellent Mullvad sunsetting port forwarding support, this question will be asked more than once.

Sorry to harp on about this. Further tinkering has revealed to me that NAT-PMP changes up the forwarded port on each connection. The Proton VPN client for Windows will tell you the port, as will the Wireguard client for Windows. I cannot however find the forwarded port in the log files for this container. So how do I know which port to manually enter in the WebUI settings? Aside from this, would it be possible to have the container automatically change the listening port based on what Proton's NAT-PMP system reports as the currently forwarded port? Otherwise we'll all be manually updating that port every time there's a reconnection, which in my case would be daily, as it goes down for an AppData backup. Hope I'm on the right track with this.

After some more reading, I suspect port forwarding via NAT-PMP is not supported on this container at the moment. @binhexcan you comment on this? Many thanks.

Did any of you get this container working with ProtonVPN? I created a .conf file with no fancy stuff like the VPN accelerator or extra filtering and chose a server with P2P support, and enabled NAT-PMP. The tunnel will come up and the web UI is accessible, but I am not connectable yet.

You're entirely correct. I deleted the appdata folders but kept the container/template I fetched a while back. I think I'll keep my folders for this new server and re-pull the template/container to make sure everything is up-to-date then. Thanks for the reply!

Evening Ich777, many thanks for your server containers. I'm a happy user of the Zomboid one. I installed it after months of inactivity and I had trouble connecting. I opened all the so-called player ports in my modem and router but it kept saying they were closed. Upon inspection, it seems they're wrongly set to TCP in the template. The documentation says they need to be UDP, as do users in the community. Changing this variable myself (and making the same change in my network gear) took away the port warning. So if I've done my homework correctly, this needs a change. I think the multiple player ports are still needed but the documentation only mentions one, so I'm unsure if they're incomplete or that's outdated as well. Again, many thanks for your work.

Same Q here but I went ahead and installed it anyway. I can report that the update check succeeded before installing the plugin, but after installing it just the same. So my careful, relative layman's guess is it can't hurt.

Hi all, Since upgrading from Unraid 6.9.2 (I think it was) to 6.11.1, QBVPN is on the fritz. I can still access the web ui, but no indication of connectability in the ui, no Privoxy working, no uploading of torrents and no ip getting assigned according to the logs. Would love if someone could take a look. It was working fine before the upgrade. Supervisord is attached. Many thanks. New wireguard config file fixed it. Weird situation. QB's web ui is crazy sluggish though and no actual downloading/uploading taking place so far... Okay down/uploads working, but the web ui is crazy sluggish in Firefox. Seems to be my install, as Chrome works fine. Firefox issue went away on its own. I am just made of small, annoying problems today.

Sorry for the lateness of my reply. And I don't know, I haven't checked. Though if it's any consolation, the move to LSIO's container was very easy.

Weird, I'm in the same boat (using Firefox and info panel shows nothing), but clearing cookies and site data does not help me. In a Private Window, I can see the info panel contents. Puzzling... EDIT: after a restart of the browser, I am seeing the info again. Will skip this latest version.

Noted, thanks!

Having some hardlink troubles. I added '-H' to Unbalance's flags (so the field now reads '-XH', the X is a default). Then I moved a folder containing hardlinked files to another drive. I hoped the system would know that these files were hardlinked, find the other copies and copy them over as well, all while keeping the directory structures that hold the files intact. That unfortunately didn't happen. The initial files were moved just fine, but the other hardlinked files are still on the original disk. So the end result is the same files on two drives and the space savings of hardlinking temporarily undone. What am I doing wrong here? Any help grealy appreciated, thanks.