KinkyBanjo

I did consider spending the time bringing it up to VPNUnlimited. But if deluge's vpn docker and the OpenVpn client connect without issue using this exact same configuration file it makes it harder to convince them its something on their end.

I have tried a new config file and a new endpoint with no luck. My openvpn config file works with the OpenVpn windows client and my Deluge docker. I am confident this occured because of a change from the last update. 2022-11-16 16:17:11,633 DEBG 'start-script' stdout output: [debug] VPN remote configuration options as follows... [debug] VPN remote server is defined as 'fr.vpnunlimitedapp.com' [debug] VPN remote port is defined as '1194' 2022-11-16 16:17:11,633 DEBG 'start-script' stdout output: [debug] VPN remote protocol is defined as 'udp' [debug] VPN remote ip is defined as '195.154.222.168' 2022-11-16 16:17:11,633 DEBG 'start-script' stdout output: [debug] OpenVPN command line:- /usr/bin/openvpn --reneg-sec 0 --mute-replay-warnings --auth-nocache --setenv VPN_PROV 'custom' --setenv VPN_CLIENT 'openvpn' --setenv DEBUG 'true' --setenv VPN_DEVICE_TYPE 'tun0' --setenv VPN_ENABLED 'yes' --setenv VPN_REMOTE_SERVER 'fr.vpnunlimitedapp.com' --setenv APPLICATION 'qbittorrent' --script-security 2 --writepid /root/openvpn.pid --remap-usr1 SIGHUP --log-append /dev/stdout --pull-filter ignore 'up' --pull-filter ignore 'down' --pull-filter ignore 'route-ipv6' --pull-filter ignore 'ifconfig-ipv6' --pull-filter ignore 'tun-ipv6' --pull-filter ignore 'dhcp-option DNS6' --pull-filter ignore 'persist-tun' --pull-filter ignore 'reneg-sec' --up /root/openvpnup.sh --up-delay --up-restart --cd /config/openvpn --config '/config/openvpn/DE93AA06-787F-4A83-8574-D28934ABE1CE_fr_openvpn.ovpn' --remote 195.154.222.168 1194 udp --remote 62.210.38.83 1194 udp --remote 195.154.221.54 1194 udp --remote 195.154.189.212 1194 udp --remote 195.154.189.85 1194 udp --remote 195.154.209.149 1194 udp --remote 62.210.211.73 1194 udp --remote 195.154.199.175 1194 udp --remote-random [info] Starting OpenVPN (non daemonised)... 2022-11-16 16:17:11,639 DEBG 'start-script' stdout output: 2022-11-16 16:17:11 DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'AES-256-CBC' to --data-ciphers or change --cipher 'AES-256-CBC' to --data-ciphers-fallback 'AES-256-CBC' to silence this warning. 2022-11-16 16:17:11,640 DEBG 'start-script' stdout output: 2022-11-16 16:17:11 OpenVPN 2.5.8 [git:makepkg/0357ceb877687faa+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Nov 1 2022 2022-11-16 16:17:11 library versions: OpenSSL 3.0.7 1 Nov 2022, LZO 2.10 2022-11-16 16:17:11,640 DEBG 'start-script' stdout output: 2022-11-16 16:17:11 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 2022-11-16 16:17:11,641 DEBG 'start-script' stdout output: 2022-11-16 16:17:11 OpenSSL: error:0A00018E:SSL routines::ca md too weak 2022-11-16 16:17:11 Cannot load inline certificate file 2022-11-16 16:17:11,641 DEBG 'start-script' stdout output: 2022-11-16 16:17:11 Exiting due to fatal error

Yes. And I think I might be experiencing the same thing... Since Nov 13th it appears my OpenVPN has not been working causing the docker to be unreachable. The docker goes into an infinite loop of trying to process the VPN and never crashes, biggest symptom was the docker's UI being inaccessible. I tried pulling in a new VPN config from my provider but no luck. I also confirmed the ovpn file is good by loading it into the openvpn client on my Windows. I have attached my debug log (Captured two loops, but this loops indefinitely). qbitorrentdebuglog_openvpnerror.txt

Anyone?

I am getting a similar issue with port 80. I am moving from Apache-PHP to Nginx and after stopping the Apachage-PHP docker Nginx still throws an error that port 80 is already mapped. I need to use port 80 for webhosting.

Hi folks! I am having a 'No space left on device' error that makes no sense to me and I am hoping to find some understanding. This error occurs when manually deleting one of the files on a torrent and then re-check that download in the qbittorrent web UI to trigger re-downloading that file. The only way I seem to be able to resolve this is by restarting the binhex-qbittorrentvpn docker. Error: File error alert. Torrent: "blah-file". File: "/PlexMediaShare/Downloads/tv-sonarr/blah-file.r18". Reason: blah-file file_write (/PlexMediaShare/Downloads/tv-sonarr/blah-file/blah-file.r18) error: No space left on device I have over 10 TB of free space on my PlexMediaShare and I am not using cache in this instance. I have searched a reason for this error and the only thing people seem to mention is bad directories and downloads being stored in the docker image. I doubt that's the case, wouldn't other issues be showing up? This so far has only occurred when I manually delete a file to be re-downloaded. Any help or understanding would be appreciated, thanks!

This also happens to me. I can only create boot images when the settings are default and I want to try the UEFI boot option but can't.