Burizado

Another observation. If I leave the 'STRICT_PORT_FORWARD' set to yes and start the container it will eventually connect.

Thanks @Alex_75 Would this be the same as using the 'PIA-WG-Config-Generator' from SpaceInvader One to generate the wg0.conf file?

I am not sure if this error is a generic error, but while troubleshooting with AI I found my issue was having the 'STRICT_PORT_FORWARD' parameter set to 'yes'. I got this while setting up a second binhex-delugevpn container to separate out my media. The information I got was even though I changed all the ports from the old and new, it said PIA was seeing duplicate connections from the same hardware. I'm not how much I trust that explanation, but setting it to 'no' did get me by the error. As @Iridix mentioned above, it might be on the PIA side.

I follow these up to step 8, then I do not see my server in the left side menu after clicking the spanner icon. Only sections with my user ID, and Plex Web.

I have been running the L2.21A version we received from William (I think that was his name) in their Support team. I have also been hesitant to update since everything has been running fine. 🙂

@Hoopster Thanks for the info! I don't have a test Unraid server, but I could load up one of my RasPis and probably do it from there, if it doesn't work directly on my server. I'll give it a try once I have my server in a quiet time, in case something goes horribly wrong. 😅

@ionred would you do this from the Unraid terminal session? Also, you mention this can be done while the server is running with no downtime?

Yeah, I have a similar issue where the IPMI would just keep going back to the login screen as well. I thought it was something odd in my network setup, but since nothing else seemed to be effected it wasn't high on my priority list to track down. Sounds like this might be the same as what you both listyed above. I will have to try reflashing next time I take the server down. Thanks for the heads up!

You need to be more descriptive in your question. Post what the symptoms are, your logs (with user and password redacted), what have you tried to resolve the issue, etc. For me (and I may just be lucky, and I am touching wood right now) this app has been working fine for me through several app/docker updates, and a recent Unraid upgrade from 6.9 to 6.11 (yes I know I was overdue). I am guessing the common reply is going to be follow the FAQ documents that are linked in Binhex's signature, probably the VPN FAQ based on what it seems you are having issues with.

Don't downloads go to the device you are downloading them on? Like if I was traveling and wanted to download episodes/movies, they would go onto the tablet/phone I am taking with me, not the Plex server. Am I wrong in my thinking here?

Thanks! Yeah, I spun up a test Radarr to see how it works, and saw all the Indexers start appearing in Radarr. So it seems Radarr/Sonarr/Lidarr will use the Indexers defined in their individual apps, but the Indexers are managed by Prowlarr. I like that there is more control over each Indexers individual settings with this setup, and you only have to manage them in 1 app (Prowlarr). Since I have 5 apps to manage the Indexers for it makes it nice to be all in one spot.

Firstly, thanks for all your hard work on all your dockers Binhex. I just installed this Docker and I am trying to understand how it works with Deluge and other the *ARR dockers. If I wanted to use this as my main Indexer, do I need to set anything up in Sonarr/Radarr? Currently I have Jackett setup in each of the applications as the only Indexer. Do I just delete that in Sonarr/Radarr, and have Prowlarr setup as 'Full Sync' for both applications? My Sonarr and Radarr dockers are also connected to my Trakt lists as well as my Plex docker. So when new content is added to Sonarr/Radarr via my Trakt lists does Prowlarr just know to look for the missing content? I guess I'm not understanding how Prowlarr would know to search for the missing content without a connection setup in Sonarr/Radarr, unless it is via the 'Full Sync' connection and it is always looking for changes in those applications (i.e. new content added or missing content found). So then in my Sonarr/Radarr dockers I would just have the download client, Trakt list, and Plex as my defined connections I am thinking.

Same here. I don't use the docker much (setup as a secondary media docker). I started it after updating, and when I open the WebUI I just get a page with 'Forbidden'. I rolled back to 4.6.4.0-3-01 and the WebUI loads fine. I didn't see any errors in the log with version 4.6.6.0-1-01 or latest. Not a huge issue for me since as I mentioned this is a secondary docker I have just to test out other media library front ends. Plex is my main media front end. I just wanted to post that I see a similar issue and heads up if anyone else has a similar issue.

Nope. Working fine for me. I am using one of the CA endpoints FYI.

Do you have a link to the download? I am assuming this is only if you are using the ovpn files and not using Wireguard?