-
Is this urgent?Kinda Host OSMac OS Monterey 12.1, Ubuntu TSL 20.04 CPU archx86_64 VPN service providerCustom What are you using to run the containerdocker-compose What is the version of GluetunRunning version latest built on 2022-03-22T08:54:52.426Z (commit c6f68a6) What's the problem 🤔I have a Premium subscription in Hotspot Shield VPN provider and I'd like to utilize its OpenVPN config file to establish a VPN connection through gluetun. The desired goal is to have other containers connecting to the network via gluetun. The problem I'm seeing is that I'm getting TLS-related errors, it looks like the gluetun container is unable to establish any TLS connection. Share your logsShare your configurationversion: "3"
services:
gluetun:
image: qmcgaw/gluetun:latest
container_name: gluetun
cap_add:
- NET_ADMIN
volumes:
- ./data/HotspotShield_AM_v4.ovpn:/gluetun/config.conf:ro
environment:
- VPN_SERVICE_PROVIDER=custom
- OPENVPN_USER=my_user
- OPENVPN_PASSWORD=my_pass
- OPENVPN_CUSTOM_CONFIG=/gluetun/config.conf
- DOT=off |
Beta Was this translation helpful? Give feedback.
Replies: 12 comments 6 replies
-
|
Ok I think I sort of get why... To get your public IP address information, two calls are made:
Now oddly, the first call worked (since it found your IP address Now you can see the download of large web responses such as the Github release And a tiny response, which is the healthcheck (a simple TCP dial to github.com:443 without any handshake or anything) works ( My conclusion is there is something splitting or blocking large network packets. Maybe have a look at This is not a bug, probably just a misconfiguration on your end or the VPN server end so I'll convert this to a discussion 😉 |
Beta Was this translation helpful? Give feedback.
-
|
I have the same errors with the same vpn provider (Hotspot Shield) I'm not sure what I should change. You mentioned checking mss / mssfix. Currently mssfix is set to 1450, though I'm not sure what this means or what it should be set to. |
Beta Was this translation helpful? Give feedback.
-
|
Again, that's not a Gluetun problem, you should reach out to your provider support. There is something (vpn server or intermediary i. e. ISP) dropping large packets, usually it's firewalls. You can check out options such as mssfix at https://openvpn.net/community-resources/reference-manual-for-openvpn-2-4/ but changing the values you have might not help. Have you tried with openvpn outside docker? |
Beta Was this translation helpful? Give feedback.
-
|
Hotspot Shield is a fairly popular vpn, I'm suprised it's not included in the list of pre-configured vpns tbh. |
Beta Was this translation helpful? Give feedback.
-
|
Feel free to create an issue for it, or implement it yourself: https://github.com/qdm12/gluetun/wiki/Add-a-provider (also development setup page https://github.com/qdm12/gluetun/wiki/Development) There is already a huge backlog of providers to add so it'll take some time for me to get to it. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, sorry to break it to you but it actually seems to be an issue with gluetun I'm also using HS through OpenVPN, and I'm currently using a custom image of transmission with openvpn client included (https://github.com/haugene/docker-transmission-openvpn) I wanted to setup gluetun with my openvpn conf file, but i'm also running into the same issue The thing is, it works perfectly fine with the custom transmission image I'm currently using, so why not gluetun with the exact same conf? MTUs & I can't get why it does not work compose: version: "3.9"
services:
gluetun:
image: qmcgaw/gluetun
container_name: gluten
cap_add:
- NET_ADMIN
ports:
- 8024:8024
volumes:
- /opt/docker/gluetun/spain.ovpn:/gluetun/config.ovpn:ro
environment:
- VPN_SERVICE_PROVIDER=custom
- VPN_TYPE=openvpn
- OPENVPN_CUSTOM_CONFIG=/gluetun/config.ovpn
- OPENVPN_USER=...
- OPENVPN_PASSWORD=...
- OPENVPN_CIPHERS=AES-128-CBC
- OPENVPN_MSSFIX=1450 |
Beta Was this translation helpful? Give feedback.
-
|
I experience identical behavior when using Hotspotshield with Gluetun. On the other hand, I can reliably use OpenVPN with the Transmission-Openvpn container. Additionally, I have successfully used Hotspotshield with Gluetun a few times, although it sometimes requires multiple container restarts before it functions without any other changes. |
Beta Was this translation helpful? Give feedback.
-
|
I have been testing Gluetun with HS shield and I am still not convinced this is MTU/MSS issue. I am guessing this could be an OpenSSL issue. What I have noticed is that HTTP (80) works. But not 443 (SSL). Also for some reason, https://www.google.com works fine. https://ipinfo.io does not work. but http does. I dont see any MTU/MSS warnings in the logs. These are the only warnings/errors I am getting: |
Beta Was this translation helpful? Give feedback.
-
Can confirm that I have the same behavior. |
Beta Was this translation helpful? Give feedback.
-
|
Same here. |
Beta Was this translation helpful? Give feedback.
-
|
also use hotspot shield preimum and would like to see it supported out of the box if possible |
Beta Was this translation helpful? Give feedback.
-
|
Having the same issue overall with Hotspot Shield. Thanks for the input guys, any news on this? Tried many fixes but nothing worked. |
Beta Was this translation helpful? Give feedback.
-
|
is adding HS on the roadmap at all? i'm paying for mullvad purely to make gluetun work, but it's a waste of money when I already get hotspot shield premium free with a dashlane subscription |
Beta Was this translation helpful? Give feedback.
-
|
I've been struggling on and off with Hotspotshield VPN and gluetun for months now. Sometimes it works, sometimes it doesn't. Every now and then I'll re-grab the ip for domain-info.us and update my custom.conf and it seems to work some of the time. But then it won't. Reset NAS, might fix it, might not. Re-deploying the stack sometimes work. Getting errors like the below:
Not sure if anyone has managed to get it working but if they have, please share! Otherwise I'll be keeping my fingers crossed that Hotspotshield VPN becomes a supported provider. |
Beta Was this translation helpful? Give feedback.
-
|
I encountered similar problems while configuring Gluetun as a sidecar in my Kubernetes cluster. After a good amount of trial and error, what worked for me, particularly with HotSpot Shield, was configuring the FIREWALL_OUTBOUND_SUBNETS to my cluster IP. I also left DNS_KEEP_NAMESERVER turned off, and now everything's running smoothly. Hope this tip can be of use to others and maybe save you some time! Edit: Well I may have too excited, but not sure I have the full picture yet. Setting FIREWALL_OUTBOUND_SUBNETS did resolve issues for me, but when recreating the service brought me back to the same issues. I turned FIREWALL to off initially and that must have saved what was needed locally. Everything works fine if i turn FIREWALL to on after the initial load. I'm unsure what ports i need to add to the firewall rules to have this work after delete and re-creating the service. I'll update if I figure it out |
Beta Was this translation helpful? Give feedback.
-
|
Wow... never have I ever felt so understood! I've been struggling with this for a week at least, tearing my hair out, and everyone here has the same problem as I do 😅 None of my attempts to solve this have worked. It seems this is an unsolvable problem, or at the very least requires deep knowledge. As I understand it, HotSpot shield is unlikely to ever be supported because some of the requirements to be a provider are behind the premium pay wall? At the very least it's good to know that I can stop trying with HS. @crispybegs was Mullvad easy enough to configure and did it work well enough? Looking for something that just works haha. |
Beta Was this translation helpful? Give feedback.
-
|
having the same issue with hotspotshield. i can sometimes connect successfully but if the vpn becomes unhealthy I start seeing the https eof errors once the vpn is restarted. below is my docker-compose with credentials omitted |
Beta Was this translation helpful? Give feedback.
-
|
The above works consistently for me now on startup but the vpn auto healing doesn't seem to work. If the vpn is restarted by the auto healer then I see the route add failure and timeouts to the DoT server below. (note log entries are in descending order) |
Beta Was this translation helpful? Give feedback.
Ok I think I sort of get why...
To get your public IP address information, two calls are made:
https://ipinfo.iowhich returns only your IP address45.137.106.205https://ipinfo.io/45.137.106.205to get extra JSON formatted information about this IP addressNow oddly, the first call worked (since it found your IP address
Public IP address is 45.137.106.205), but the second one failed...Now you can see the download of large web responses such as the Github release
cannot get v…