Auth  received control message  auth_failed

Auth received control message auth_failed

Pfsense part 3: configure ldap authentication

Right, I’m using the express vpn-provided unique name and password, not my account name and password. My only guess right now is that I’m not placing the keys in the right place; they’re actually in /etc/openvpn because I’m not sure where else they’d go.
For reference, the keys/certs were included in the ovpn files I last downloaded from ExpressVPN (around a year ago – my account is no longer active, so I can’t check), so there was no need to place them somewhere else on the computer (not like setting up a client). So, try installing a new ovpn from your account and simply changing the auth-user-pass line to point to your credentials file.
Thank you, @VincentR, thank you for your comment. The keys and certificates are also in my ovpn file; I just tried placing them in a separate file, but that didn’t work either; the separate file also gave me an unknown choice error. I’ll reinstall and double-check the settings.

Mrt error 009!!! auth your mrt dongle fail fixed

Nothing has changed on my end, and I’ve waited several minutes for a time-out to ensure there isn’t a dirty disconnect. I’ve also tried connecting to Vega and Omicron via UDP and TCP on ports 80/443, but to no avail.
Your account has permission to connect to all VPN servers. However, we had a minor issue with Vega (the server you attempted to connect to) at the time of your attempted link that did not impact existing connections but prevented new connections from being created. It was resolved in 10 minutes; please let us know if all is working for you now.

Fix pptp vpn not connecting in windows 10

OpenVPN was installed on both Windows 7 and Ubuntu 12.10. I have the same issue in both cases. I have an.ovpn and.crt file that I need to add to the vpn. I have a username and password combination as well. When I use those files to run OpenVPN (in admin/sudo mode), I get the following error: AUTHORITY: The control message AUTH FAILED was received.
My VPN provider had similar issues with me (ProXPN). Despite the fact that I was confident I was using the same user name and password that had successfully signed me into my account on their website, the VPN client kept reporting AUTH FAILED. My password turned out to be 12-characters long, which worked fine on the website. The VPN client linked and authenticated perfectly after I reduced the password to 8 characters!

[solved] unable to connect to the vpn client service

It’s likely that your login attempt was rejected because the username/password entered was wrong, or that the VPN server rejected your authentication attempt for some purpose (for example, most VPN Service Providers limit the number of simultaneous connections you can make – it may think you are already connected).
I can’t get Viscosity to connect; I’ve tried everything, and I’ve even tried deleting the keychain, but Viscosity hasn’t recognized the keychain. So, instead of Private Internet Access, I keep getting Authentification Failed from Viscosity.
I’m afraid you’ll have to contact your VPN provider; they’ll be the only ones who can tell you why their server is refusing your authentication attempt. As previously stated, an OpenVPN server can send an AUTH FAILED message for a variety of reasons, so it’s likely that your configuration is out of date, or that your certificate authentication details have expired.
I believe this material should be included in the installation guide because I wasted a lot of time, and I believe other people are having the same problem, and it became extremely difficult to get the product to work. The help was excellent, but the process for running the software, in my view, should be made simpler.

About the author



View all posts