Liam_Galt

FYI it doesn't work even with just openvpn CLI, so it's definitely not on your end. This is a PIA issue that PIA is asserting is user credentials errors.

Yeah I've been asking support and they just tell me to make sure my credentials are correct. You're definitely not the only one. I think this is on their server side, credentials aren't propagating correctly or something. You can follow my Reddit post for some other info, but there's not anything really helpful there, either lol.

Support told me to ask on reddit :'D I'll loop back here if I figure it out in case someone encounters a similar issue in the future.

Still AUTH_FAILURE, but with deprecated option warnings: 2020-12-03 10:11:47 DEPRECATED OPTION: --cipher set to 'aes-256-gcm' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-256-gcm' to --data-ciphers or change --cipher 'aes-256-gcm' to --data-ciphers-fallback 'aes-256-gcm' to silence this warning.

Here's what I've got. Thanks for taking a look. supervisord.log

This is unfortunately where I started in the first place: Subscribed yesterday, verified that it works with PIA Chrome extension. These are correct. I am using the p****** username, and the password. They work in other PIA clients. It is only alphanumeric. I've tried changing a few times, still no luck. The password is only 16 characters. I downloaded them yesterday. Again, other PIA clients work. I've tried using both Wireguard and OpenVPN but to no avail, still AUTH_FAILED.

Hmm.. created a fresh container, with most recent image, and still AUTH_FAILURE. No idea.

Nah, it's on the order of 20 characters, only alphanumeric.

Yeah, it's the correct username/password. I've triple-checked, and typed it in manually multiple times, but still no luck.

I was using NordVPN for awhile since I already had an account with them, but just switched to PIA. When I try to start Deluge using PIA instead, it just hangs. if VPN_ENABLED is set to false, it's fine. When I start the container with VPN_ENABLED, the web UI just says "refused to connect," and if I try to view logs from the Docker page of Unraid that also hangs. I can connect to the container with no issues, and the deluged.log doesn't seem to show anything spooky. I've got the cert files and a .ovpn endpoint in the openvpn folder, and I've verified that the username + password are correct. I have also updated to the most recent image. Any ideas of what else could be causing the hang? EDIT: Nevermind, found AUTH_FAILED issues. Will try to fix then loop back if I still have issues.

I get massive hanging when running this, I'm wondering what could be causing it. I notice it when I'm downloading via sabnzbd, mostly using my Windows VM (running on a dedicated NVMe SSD passed through). sabnzbd downloads to and extracts from cache drive. I have it pinned to CPUs my Windows VM doesn't use. Any ideas on flags that I could change to try to fix the issue?

I'm setting up Organizr and was wondering how to set up authentication as described on the wiki. It seems to me that this would require an entire custom Nginx config for each subdomain, but I'm not positive. Anyone happen to know?

I just did some testing and hard links appear to be working when created manually, it just seems to be with Sonarr that things aren't working as expected. Feel free to disregard anything here.

I understand that the contents are the same, it's the storage calculation that is the concern. If I create a file and then create a hard link to it, the space appears to be calculated when viewed in both Shares and Main (for whatever disk the file and its link are on). Is this expected behavior? What happens if the calculations of these links exceeds my actual storage space?

I noticed that my Media share (to which Deluge downloads, and Sonarr/Radarr create hard links to corresponding folders for Plex to read in from) was roughly double the size I was expecting it to be when looking at unRAID Web GUI. I looked into it a bit more and it seems that hard links aren't working as expected, and instead are creating new inodes (despite appearing to point to the same file). Example: /mnt/user/Media/Test# touch foo /mnt/user/Media/Test# ln foo bar /mnt/user/Media/Test# ls -li total 0 660391 -rw-rw-rw- 2 root root 0 Dec 22 09:15 bar 660390 -rw-rw-rw- 2 root root 0 Dec 22 09:15 foo It was my understanding that hard links worked fine within a user share, but this appears to be creating new inodes. If I do the same thing on /mnt/diskX/... it works, so is something possibly misconfigured with my share?