@viragomann I can access the destination when I use other OpenVPN client machines (including windows and android), so it is not a permissions things.

@pfsenseuser2020 Edit your OpenVPN server and scroll down to the Advanced Configuration section. You add reneg-sec 36000 to the Custom Options field.

@pfsenser_ca said in OpenVPN client fatal error: Our OpenVPN client is set to use "BSD cryptodev engine" currently This is definitely not a problem, at least I never met that (we have 100 - 120 OpenVPN clients- with BSD crypto) Try even these steps: NCP disabling (if it is checked) cipher change AES-256-GCM (GCM is faster and safer anyway, in principle) [image: 1610529442864-a2491c83-bc56-4fbe-86bc-87945afd831b-image.png]

@aperez said in Slow certificate-related pages: 200 certificates and 20 revoked certificates Yeah, that one is known. Admins start to become red if certs have to be revoked. This is just another reason. Glad you know why now.

If your trying to use ovpn file with openvpn on centos.. That is not the way you do it ;) So yeah your going to have problems.. Something like this would be more like it openvpn --config client.ovpn

Let the user get the latest OpenVPN version: https://community.openvpn.net/openvpn/wiki/OpenvpnSoftwareRepos

@leonardo-fernandes You are my hero. Thank you very much. My OpenVPN with AWS works perfectly now

@viragomann That works as expected! Thanks a lot! Now I have another problem -> new thread.

It's a UDP tunnel fyi, not TCP

@johnpoz Wow...I was staring right at it. Regardless, thanks for the fast reply...will simplify the needed editing. Thanks again!

Try to post log as a text file. sanitized-log.txt

Found it. Either this thread can be deleted or we can see if others would see the error. Hint: I would have had assumed that with this error, nothing would have had worked, but instead it did - even with mediocre speed ;-)

No idea what directory you are talking about, can you specify the question? -Rico

@webstaff Google foo.. Just pop this in Server custom options. push "route 0.0.0.0 0.0.0.0" https://forums.openvpn.net/viewtopic.php?t=27321 Seems to do the job.. If anyone wants to give me some Karma so I can post without getting hit as a spammer that would be great. Regards Dave

@meaglerick I think, that is the wrong place to ask this. Possibly you have luck in the OpenVPN community forum. We are just following here the guides provided by Netgate: https://docs.netgate.com/pfsense/en/latest/recipes/openvpn-s2s-psk.html https://docs.netgate.com/pfsense/en/latest/recipes/openvpn-s2s-tls.html

Solved : I change the IPV4 Tunnel Network CIDR to 172.16.40.0/24 and everything is working again.