Repository navigation
IVPN won't connect, setup previously worked with Mullvad #3523
|
I switched from Mullvad to IVPN this week and went to make the switch in my Gluetun compose file. I tried both Wireguard and OpenVPN but both threw errors. I disabled firewalld on the host which had no effect, I also tried opening port 2049 on the modem and in firewalld which did not have any effect either. Previously, I did have port 51820 open for Mullvad, although now I question its need. I have masquerading on in the public zone and I turned it on for docker as well (it wasn't previously enabled when Mullvad was working). I also tried a few older tags but outcomes were the same. And, I also tried updating the server list a couple of times. Other Wireguard configs I generated are working elsewhere. The host is an up-to-date EndeavourOS install. I can't really think of much else, but I searched everything I could think of before deciding to post. Thanks to anyone who has some insight. The OpenVPN compose I tried: Logs for OpenVPN: The wireguard config I tried: Wireguard output: |
Replies: 2 comments 6 replies
|
hey, the openvpn one is a config thing. the log says openvpn is trying to prompt for gluetun/internal/configuration/settings/openvpn.go Lines 108 to 113 in 156ccc2 OPENVPN_PASSWORD=ivpn and it should get past that.
the wireguard log doesnt actually show an error btw, pmtud failing just means nothing got through the tunnel. if u want wg, maybe try another |
|
also please flag that msg as the answer if that helped to close the thread |
no, nothing to open on ur side. wireguard here is outbound udp from gluetun to the ivpn server, replies come back through the same nat mapping, so the 2049 forward on the modem isn't doing anything and u can remove it. gluetun's firewall drops unsolicited incoming traffic anyway.
one thing i'd try: ur config has a
PresharedKeyline and u only set the private key and address. gluetun does support it viaWIREGUARD_PRESHARED_KEY(https://github.com/qdm12/gluetun-wiki/blob/main/setup/options/wireguard.md) and afaik if the server expects a psk the handshake just silently never completes, which looks exactly like a healthcheck that keeps failing with no error.PublicKeyandEndpointfrom the fi…