OpenVPN not working

KOM

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?

manjotsc

@KOM 2.4.4-RELEASE-p3 (amd64)
built on Wed May 15 18:53:44 EDT 2019
FreeBSD 11.2-RELEASE-p10

KOM

Strange. And what happens when you delete all that and try with your other provider, PureVPN? Exact same symptoms and error?

manjotsc

@KOM ya same thing

KOM

It's suspicious that it fails the same way with a different config and provider.

I don't have any other suggestions, sorry.

manjotsc

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.

KOM

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.

manjotsc

@KOM so did it solve the problem?

KOM

No, it turned out to be a DNS issue.

manjotsc

@KOM I am having same issue, DNS stops working, when connected to OpenVPN

KOM

I think I had to specify a gateway under General Settings - DNS Servers.

manjotsc

@KOM I tired that, same thing dns stops working.

KOM

DNS fails for all of pfSense (not just LAN clients) when you bring a tunnel up? You can't resolve via Diagnostics - DNS Lookup?

manjotsc

@KOM Is it a bug?

KOM

I doubt it. Config problem 99.9% of the time. What about my questions?

manjotsc

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

KOM

I asked:

DNS fails for all of pfSense (not just LAN clients) when you bring a tunnel up?
You can't resolve via Diagnostics - DNS Lookup?

manjotsc

DNS fails for all pfsense WAN, LAN, and can't be resolved under Diagnostic, DNS Resolver, when the open VPN is up.

KOM

And you're using Resolver? You have it set to listen on all interfaces, and use all outgoing interfaces? Maybe try setting Outgoing to WAN alone.

manjotsc

@KOM It's already set all, issue still persist.