OpenVPN not working
-
Ok let me check the order
-
It's newest entry on top, followed by old ones
-
OK, so @Rico was bang on the money.
Some Google-Fu shows that this error can happen if you give it a password-protected private key to use. The suggested fix is to run your key through openssl like this:
openssl rsa -in YourPrivateKey.pem -out NewPrivateKey.pem -
@KOM how do I do that?
-
Never mind. That advice only applies if you were making a private key with password-protection. It doesn't apply for a client-connection to a public VPN where you don't use a client cert.
This is really weird. The error message is complaining as if either you need a user/pass and didn't supply one, or it doesn't want a user/pass and you did supply one.
What version of pfSense is this?
-
@KOM 2.4.4-RELEASE-p3 (amd64)
built on Wed May 15 18:53:44 EDT 2019
FreeBSD 11.2-RELEASE-p10 -
Strange. And what happens when you delete all that and try with your other provider, PureVPN? Exact same symptoms and error?
-
@KOM ya same thing
-
It's suspicious that it fails the same way with a different config and provider.
I don't have any other suggestions, sorry.
-
I found the problem and it's working now, my pfblocker has the same subnet ip as the purevpn was trying to obtain. Only issue now is when I am connect to openvpn, the dns stops working ex: youtube.com when typed, but if I type the ip of youtube "172.217.13.206" manually on address bar it works.
-
Funny you should mention that. I just got an SG-1100 and was configuring it last night. I have 3 VPN connections defined, and when I bring one up in particular, everything dies. I also have pfB loaded. I was about to spend time today researching the problem but you may have just solved it for me.
-
@KOM so did it solve the problem?
-
No, it turned out to be a DNS issue.
-
@KOM I am having same issue, DNS stops working, when connected to OpenVPN
-
I think I had to specify a gateway under General Settings - DNS Servers.
-
@KOM I tired that, same thing dns stops working.
-
DNS fails for all of pfSense (not just LAN clients) when you bring a tunnel up? You can't resolve via Diagnostics - DNS Lookup?
-
@KOM Is it a bug?
-
I doubt it. Config problem 99.9% of the time. What about my questions?
-
I did, specified a "DNS" for gateway of VPN and for WAN_DHCP, but it doesn't seem to work. It won't resolve to anything it just keep loading forever, even under Diagnostics - DNS Lookup. It kill WAN, LAN
