HumanSkunk

Still unable to run this with any VPN enabled. using my old Openvpn config I still cannot download any test files within sabnzbd. With the VPN disabled everything works exactly how it used to with the VPN enabled. No idea what the issue is. No change to any of the previous log files no matter what setting I modify within the containers.

Done some more debugging into the wireguard option, I have switched the server to multiple UK based ones in the wg0.conf with no luck. I have noticed that the Interface Address at the top of the configuration is blank as well as the completed public key, I presume that these should be completed in a setup step which isnt being done. Should this happen automatically? Presumably would be completed as part of the step that fails with this warning: [warn] Failed to download PIA json to generate token for wireguard from URL 'https://www.privateinternetaccess.com/gtoken/generateToken' When I open the link I get this: { "status": "ERROR", "message": "no auth data" } And the process then hangs. With Sabnzbd inaccessible.

I also tried to switch to wireguard which generates the wg0.conf is created which as per the wiki defaults to the Netherlands but it will never connect. I have also attached the logs for that. Not sure what is going on... Will just run using the default ssl link with the Newshosting service for now until someone cleverer than me can spot something. piawireguard.rtf

I have been running 7.2.0 for a while with no issues. Noticed that none of my docker images were reporting there was an update available including this one which at the time was over 8 months old. Checking the binhex docker repo said there was a version released a few months ago but I couldn’t see it. Sabnzbd was also complaining it wasn’t up to date when I used it. I updated to Unraid version 7.2.3 hoping this would resolve the Docker update, but it didn’t. Decided to take the executive decision to manually update it by changing the container setting to point at binhex/arch-sabnzbdvpn:4.5.5-1-01 repository. Clicked apply and let the container run through its scripts. Sabnzbd launched fine I could hit the web server but whenever I tried to download anything I would get a handshake error with the news hosting server. “Errno 111] _ssl.c:1011: The handshake operation timed out” Checking the container logs and nothing seems to be reporting an obvious issue. I didn’t change any other setting and I double checked the OpenVPN files were still in their original location. I did change the name server settings as advised in the post above to just show 1.1.1.1,1.0.0.1 but the same result. If I disable the VPN then everything works fine so I know it is down to that configuration but I considering it was working last night and after manually updating the docker container it isn’t then something seems to be retaining some information but I don’t know what. I also tried an updated ovpn file downloaded directly from from my PIA profile but nothing seems to change. It is the same error. piaovpn.rtf If it isn’t broke… don’t fix it. Was something I should have just applied but we are where we are.

Ah that makes sense then. Thanks for clarifying.

Are you kidding me... how did I miss that. I obviously changed it when I set it up the first time as I didnt have this issue originally, but when I had to remake them I missed changing that option. Odd that it works when dont have the vpn active, or does that config setting only get used when the vpn is set to yes? I have changed it and it works now. Thanks... feeling stupid now.

Doh well that would have saved me a bit of time. At least it was practice more than anything. And yes I have posted on the main support for sabznzb and hopefully I can get that resolved.

Hi thanks for the reply. 192.168.0.10 is the ip address of the unraid. I have tried access it from my PC (chrome) which is 0.2 and my MacBook (safari) which is 0.204. Both just time out. If I start it with the argument for the VPN set to no then it is instantly available.

So yes I created a bit of a mess for myself in that I accidentally deleted a number of shares that I didnt think were being used as there was nothing stored in them. I clearly didnt look very hard. I read warnings of the file manager app being able to cause damage and I removed a number of key files whilst I was trying to work out what was causing the drives to remain active. Long and short I did accidentally delete a number of the shares unknowingly when posting that file that the dockers need. When I started the dockers all their contents and configurations had been lost which I noticed about 5 mins after doing it with a lot of swearing. I have now recreated the system share entirely on the cache and recreated all my docker images again after deleting them. What was meant to be a quick tidy up of some files has now meant spending a good number of hours rebuilding things. Lesson learnt I guess. Plus side is that the drives have remained spun down during all of this. System share is now present when I run the command and all the dockers have loaded. Downside is I am getting a weird behaviour with the binhex-sabnzbdvpn docker that wont load its gui when the vpn is set to yes in the docker settings, but it functions correctly even with the vpn active I just cant access it, I have posted elsewhere with that issue. shield-diagnostics-20240616-1311.zip

Hi I had to reinstall my docker containers and since then I have been unable to access the sabnzbd webgui with the vpn active. Sabnzbd seems to start and sonarr and radarr can access sabz as downloads are passed between the dockers however the GUI is never accessible. If I turn off the vpn and restart the docker then I can access it instantly. I cant see any errors in the log nor nothing seems to fail to start. "2024-06-16 12:13:08,503 DEBG 'watchdog-script' stdout output: [info] SABnzbd process is listening on port 8080" I have looked through help articles and havent found an answer as most indicate that the webgui wont start if there is an issue with the vpn connection, which there isnt in this case as the services start, I just cant access the webgui. I have provided a log output of the supervisors, and obfuscated the IP addresses. One thing that I have noticed is that the vpn start takes a few attempts before establishing, however all seems to start successfully after a few minutes, I just cant access the webgui. supervisord.log

I have read a number of differing posts about this and peoples solutions seem to be different. I started using unraid about 2 weeks ago and have finally got all my data on the system and the parity built. However in that time Disk 1 has never spun down on its own. I had it set to spin down after an hour, but have dropped that to 30 mins to see if i could get it to stay, but as soon as it spins down it spins immediately back up. I have a number of dockers that are set to use my drive cache (originally when i set the dockers up i had them using the array as that was how it was set by default. I then followed a forum post, moved appdata to the cache and changed the share to use the cache and restarted the dockers. Functionally this worked. If i stop all the dockers i can keep the drives spun down but i have gone through all the settings and share usage and i cant see what is set to write or read a load of data from the array and not from the cache. I have installed file activity and the only data stored there is the iCloudpd docker writing an update to the drive cache. As soon as i start a docker image then disk 1 will spin back up and start a number of reads and writes to the drive, this slows down after initial start up but nothing is recorded in the file activity plugin. Is there something i have missed in moving when i moved my docker images. Happy to take a backup and completely rebuild them if that is what is needed. I have attached the diagnostics and would really appreciate the help here more for my own understanding of how the shares and cache even operates. shield-diagnostics-20240616-0827.zip