DAVIDP

Same issue for me - reset my password and now unable to access my local Plex server directly. Tried all the suggested things on the Plex articles to no-avail. Any advice greatly appreciated. Log entry says; ##################################################### # Login via the webui at http://<ip>:32400/web # # and restart the docker, because there was no # # plex token found in the preference file # #####################################################

@orlando500 - Thankyou! adding 'nap-disable' fixed it.

Hi All, My container updated again over-night and its not working. This time, I'm getting the same cipher error as others. Im using PIA. I have done the following with no success; 1) pulled down the latest nextgen openVPN files. replaced all three on my server with new versions. 2) removed the cipher line and replaced it with fallback line from Q22 3) I tried leaving the original cipher line in and adding the fallback line immediately beneath 4) i've tried 3 different endpoints, all with the same error (Singapore, Romania, Perth) 5) i've tried with and without strict port forwarding enabled (PIA tell me all non US nextgen servers are now port forward enabled?) Any suggestions? please

FOUND THE PROBLEM... Seems like it didn't like a 99 character password all of a sudden???? I shortened my PIA password, updated the docker config and it connected instantly..... is there a limitation in the build for password length maybe? i've had the same 99 char password for about 6 months now without incident...

xxDeadbolt - Yes, my main creds, the one i use for the PIA website, not the SOCKS/Proxy ones. Same credits i've been using for ages, the one that starts with Pxxxxxx. same creds i can use to connect to the same end point via a desktop openVPN client.... its so damn odd. I spat it thinking maybe something screwy somewhere, so deleted the whole container, the whole binhex-del.. folder from appdata, etc... and started over. different endpoint this time but same outcome.. I'm at a loss.

Hi All, Im having trouble that i simply can't get past. My container updates overnight, I'm running the latest. Now, the VPN won't connect. the logs are giving me an AUTH_FAILED error. I've checked the FAQ and gone through the suggestions there. i've changed my password, i've tried other endpoints, i've moved over to the next-gen configs (copied the certs an the new ovpn files over), i've removed all special chars from the password, i've forced an update to ensure i was on the latest build (i was/am), etc. etc. It simply will not connect via deluge. I can however connect to the end point via a desktop openVPN client so i know the end point is up and my creds are fine. I've attached a screen shot from the log file - Im not picky at this point as to which server i connect to.. i just can't for the life of me work out whats going on???? any suggestions, idea's? anything? PLEASE HELP

Similar experience here. DelugeVPN updated overnight and i woke to find the container stopped. Tried to manually start the container but UNRAID is giving me the error "Execution Error"... working fine prior to the upgrade. Any suggestions? Update: decided to delete the container and rebuild.. Same issue, the build fails with the following error: "/usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint binhex-delugevpn" Is there an issue with the latest container release maybe? binhex/arch-delugevpn:latest

Hi, I seem to have having the same issue a number of others have had in the past. I've followed all the suggestions and still my deluge downloads are DOG SLOW... i mean 5 KiB/s SLOW.... Same endpoint, via desktop app... ill max out my connection no problem. Im running the latest delugeVPN container, with PIA, via a port forward enabled endpoint. core.conf file attached, any and all help would be appreciated. core.conf