UPDATE: I've been doing some tests trying to know where the problem is and it seems that finally it comes from WAN interface. I configured first WAN but until I configured the IPSEC tunnels the problem didnt appear. Today I reinstall a fresh pfsense and first of all I configured the tunnels with no problems and when I configured the WAN the problem start. If I enable WAN with DHCP or Static IP without a gateway it works everything fine, when I choose a IPv4 Upstream gatewy then return the problem. At this point this topic can be closed.

@gertjan Yesterday, I could change that, now it seems it's working how it should be. Thank you so much for your help.

@noplan said in PFsense 2.5 RC OpenVPN/ExpressVPN problem: @trikki69 said in PFsense 2.5 RC OpenVPN/ExpressVPN problem: so your problem is now solved with this added this to my advanced custom options within the OpenVPN client setup: ;pull-filter ignore redirect-gateway; brNP Yep - works great now, no thanks to ExpressVPN support.

@amarand said in ACME with Siteground: Is that not a feature that Let's Encrypt supports? Your quiet close. It's : @gertjan said in ACME with Siteground: The TXT filed will contain a challenge code to be put into the TXT field. This code is give to the acme script by Letsensrypt. For example : 'bmDWOCHFZRtOOCr_vU-mEfTIqA6i9ib0R3V6-RMF3FE'. This bmD....................RMF3FE thing is generated randomly, and will be unique for every certificate request. This proofs that you control right now - and not some time X in the past. Note that, ones this test passed, it stays valid for one week.