Jump to content

Monday

Members
  • Posts

    1
  • Joined

  • Last visited

Monday's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Hi all, This is my first post here, nice to meet you :) I’ve been using the SABnzbdVPN docker container for a little while now and it’s been working really well. Thanks so much for creating this! I’ve found that my ISP seems to throttle standard tcp/udp VPN connections including connections from this docker container. I use AirVPN and when I run the standalone AirVPN Eddie client natively on Windows, I can set VPN to run through an SSL connection. When I do this on the native client, my VPN speeds are much higher (around 2.5 time faster download) than when running on tcp/udp VPN ports. I’m trying to replicate the above with OpenVPN in this docker container. I believe the correct way to do this is using stunnel. In the SABnzbdVPN container I’ve installed stunnel, copied the ssl config from AirVPN, copied a new set of VPN config files from AirVPN and put them into the openvpn folder and made sure to reference the full path to all the certs and files. To test things, I kill the openvpn process and try running the stunnel binary which seems to start fine. Then when I run openvpn and reference the new config, it does not start. I get the following error which appears to be from stunnel: TIMEOUTconnect exceeded "no more addresses to connect" My guess is that this address cannot be reached, maybe it’s because this docker container is designed to have VPN connectivity established first before allowing any further connections? I’ve also tried editing /root/openvpn.sh and adding stunnel to start before the eval openvpn command but still get the same error. Any help would be much appreciated. I’m happy to provide more info if needed. Thank you.
×
×
  • Create New...