betaman

Yeah, I'm not that savvy with Linux. Would you mind sending the commands I need to execute? Much appreciated.

Thanks for the post. I just noticed this but I don't see a docker data directory for PIA-WG-Config-Generator in my appdata folder. I also don't see a container variable specifying the datadir so where exactly would I replace the piawg.py file?

I know this is a custom docker from SpaceInvader but I couldn't find a support page in the forum. Sorry if I missed it and this is the wrong section to post. Anyway, since PIA recently changed some of their endpoints, the configurator doesn't seem to work. I'm not sure if these two are related or not but ever since the change, I'm having issues getting a proper config file from a server that supports port forwarding. Does anyone know how I can fix this? The wg0.conf file in my /cache/appdata/wireguard-easy/ directory has file permissions that won't allow me to view it. I know how to change them but thought I'd ask here first if anyone knows why SI's docker isn't working? EDIT: Ok, I was able to find a server (Netherlands) that generated a file correctly. I then had another issue to get Prowlarr and Flaresolverr talking to each other behind by custom WG PIA VPN network (had to add a Host variable of 0.0.0.0 to Flaresolvver to look at all incoming traffic) and now my indexers are working again. Prefer a physically closer server than Netherlands but for now at least I'm running again.

Is my issue RAM?

Just bumping this in case anyone has any feedback. I haven't seen any further errors since posting.

EDIT: Ok, once I realized the problem was the network config, setting both Prowlarr and FlareSolverr to use the Bridge network resolved the communication. I had gone in and setup a custom netowrk wg0 using Wireguard and PIA to put my *arr dockers behind a firewall. Apparently, puting Prowlarr and FlareSolverr on this network breaks the communcation due to cloudfare? Is there a workaround for this? I found a reddit post where a user mentioned adding the following env variable to Prowlarr but it didn't seem to work:

Fix Common Problems reported a Machine Check Event. Any help intepreting the issue would be great. Thanks in advance. tower-diagnostics-20260707-0947.zip

Just reporting back as stated above. Been using the wireguard method and still haven't noticed any speed issues torrenting. Note: I only use public trackers so perhaps if I was seeding more it might be more noticeable? Not sure tbh.

Ok, interesting. I didn't see a noticable difference in speeds between my old (this docker) and new (Unraid wireguard setup from video) setups. I'll keep an eye on it and report back.

Ok, so it's the upload speed that will be majorly impacted in this case? You're saying this is a WG limitation?

So I'm not sure if this is the same thing or not but I think that's why I need a PIA Server that uses port forwarding? If I don't pick one that has it then the bittorrent client either fails or is miserably slow. Make sense? p.s. Huge thanks to you and the work you've done over the years. My server dates back to 2009 and I've used your dockers forever!

Well, this is super easy to configure and essentially offers the same benefit as the VPN enabled dockers. I didn't change containers as mentioned, just disabled the built-in VPN and moved all my dockers over to the tunnel network. Anyone just starting out and wanting to put "all" their containers behind a VPN should use the method in the video. It's way simpler now with the advances in the OS and use of Wireguard.

I ended up just configuring a Wireguard Tunnel to work with PIA per this video and just disabling VPN on my binhex VPN containers (vs installing the non-VPN versions):

Thanks for the help. Will report back once I’m home and can make the changes.

How's this I think I am...I was using CA Ontario. When I tried to use SpaceInvaders config app, it hangs on this server but I can generate US East no issue. EDIT: But the weird thing is my Sabnzbdvpn docker from Binhex works just fine with same config. I think I just need to setup wireguard thru PIA and route all docker containers thru it - instead of using these VPN dockers.

Reading back thru the thread, I think my problem might be in an invalid wireguard config file. I'm using PIA so will try to remember how to generate a new config. EDIT: It looks like when I upgraded to 7.3 that my wireguard tunnel was deleted.

Isn't the syslog.txt in the tower-diagnostics file I posted the same thing? I'm not aware of another method being required to post logs for issues? Also, how would you anonymize?

Yeah, sorry. I know better...haha tower-diagnostics-20260610-1600.zip

This is what I'm seeing in my qbittorrentvpn log. Is this a PIA issue?

Still down for me. Starting to wonder if something more long term is up with duckdns?

Ok, good. I wanted to make sure it wasn't just me. Ironically enough, I've been using duckdns for several years and first time I notice it's down. Guess I was just lucky...

I'm having issues but they seem to be related to duckdns.org. I've tried on multiple devices on different networks but continually getting a 404 Not Found error. Can anyone else confirm?

The latter. It seems as though this is a "feature" of the CP1500PFCLCD. I was reading the NUT+ plugin thread and it sounded like adding a parameter of "Ondelay=0" might be necessary?

I haven't kept up with the changes to using a battery backup with UnRAID. In the past, I've used various plugins (e.g. Nut) to manage this. Recently, I had a power outage that resulted in an unclean shutdown and discovered I lost connection to the UPS (a CyberPower 1500PFCLCD). I'm just looking for recommendations on the best configuration as I recall in the past one of the major issues with my setup is the battery backup not powering backup once power is restored. In reviewing the Nut plugin thread, there seems to be some workarounds but before I explore that route, I wanted to see if there's a better option with the current OS?

Just bumping this thread to see if anyone has upgraded recently?