l3gion

Booom, that worked Thank you very much @binhex.

Hi @binhex, Yes, the screenshot is from inside sabnzbd. I also tried setting the VPN parameter to "no" in the docker settings, and that let's sabnzbd resolve the nameserver/DNS lookup, definitly something fishy in the VPN, maybe PIA changed something? Thanks.

@binhex I'm having issues connecting again. Lost access a couple a days ago. I have tried different servers and have followed Q22 from the FAQ:| https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md Anything changed in the recommended setup? Thanks. supervisord.log

Kinda the same issue here. Test seem to be failing all the time.

PIA needs to get their stuff in order, thanks will try that fix Best.

Hi, What do you mean by "your actual PIA user name"? I'm using my PIA user name already. I Reverted to my previous container version using a backup and it's working again. Best.

Hi all, I'm also unable to get connected to PIA servers anymore. I keep getting this warning: 2020-11-07 16:21:21,750 DEBG 'start-script' stdout output: 2020-11-07 16:21:21 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-128-cbc' to --data-ciphers or change --cipher 'aes-128-cbc' to --data-ciphers-fallback 'aes-128-cbc' to silence this warning. I tried several OVPN config files from PIA, with different ciphers and none is working now. Attached log and redacted PIA info and IPs. Best. supervisord_redacted.log

Ok, today had some time to clean the server, was a bit dusty inside. It's beep up now for 5 hours and it's still holding at 1gb speed.

Thanks for the suggestion, but I'm not that is the cause, as a reference my cpu sits around 35-40ºc and the array drives 25-28ºc, so temperature is pretty low in general inside the case.

I'm looking into it. Different cable and diffent hub port have the same result. I'll try to get an add in network NIC to see if the problem goes away. Thanks guys.

HI, My server is randomly drops my network speed from 1gb to 100Mb, today I caught it on the log: "vnstatd[6095]: Detected bandwidth limit for "eth0" changed from 1000 Mbit to 100 Mbit." My network is the Motherboard integrated one, from a Fujitsu D3417-B2 I also didn't used to have this drops in speed, I think they only started since upgrading to 6.8.0 If I restart the server the speed is back to 1gb, but having to restart every couple of days would be pretty annoying.... Anyone else has this issue too? Any idea what it could be? Thanks. diagnostics-20200223-2217.zip

Also updated from 6.8.0 here, all up and running here

Thanks mate, this was GOLD

Thanks

Hi, Can't seem to get the path to work, I'm using a path in /mnt, but it still errors: I also tried to disable restrictive validation, but the same occurs. Best.

I have the same error after updating too.

Not automatically, I have to run "./manage.py document_consumer" in the docker console. But I don't know why or how to run it at start automatically.

No problem :) did you get the consume process to run automatically?

Hi, Just run ./manage.py createsuperuser in the docker console.

Sorry for the super late response, I figured out what it was, I usually check this but I guess I missed it this time, was a port conflict. Best.

Hey, I wanted to try out Rapid Photo Downloader but after install I'm having an "execution error" and the docker log is empty. Any ideia what could be causing this? I'm running unRaid 6.7.2

Update on this topic. So I returned the Corsair drive and the seller sent me a replacement unit, another Corsair MP510. This second drive had the same exact problem has the first one, same TRIM issues, fortunately the seller agreed to also have this second drive returned and return what I payed for it. I now got a new drive, a Samsung 979 Evo plus, zero problems with this one.

Thanks for the suggestion, I'll be returning it then.

hmmm, bummer But is this something ok to live with? Or you would just return the drive? Thanks.

Just tried that, plugged the drive in to my Windows machine and ran the Corsair ssd utility, firmware is the latest available. Also tried to switch the 2 nvme drives, connecting the Corsair drive to the motherboard nvme port, and the TRIM errors are still there :( Is the drive faulty? Everything else is working as expected. Could it be related to the cache drives have different sizes?