Setting up ExpressVPN with OpenVPN
-
Hello everyone,
I am a newbie here. and would like to setup my PFSense to connect to ExpressVPN through OpenVPN.
I already have an account with ExpressVPN. I installed PFSense on a Hyper-V VM and setup everything as mentioned in Expressvpn documentation. PFSense is not able to connect to ExpressVPN.
I went through the current topics in the forum but cannot find a similar case to the issue I am experiencing.
I have been almost daily in contact with ExpressVPN support to fix this issue, but they are not able to fix it so far.
Any Advice?
Thanks!! -
@hkohila you will have to provide more information for anyone to help you.
How did you set it up, which tutorial did you follow (the ExpressVPN one is for pfSense version 2.4.5, it states on their website)? What is the error message you get? Does you pfSense installation work correctly, when not using VPN?
-
@hkohila said in Setting up ExpressVPN with OpenVPN:
I already have an account with ExpressVPN. I installed PFSense on a Hyper-V VM and setup everything as mentioned in Expressvpn documentation. PFSense is not able to connect to ExpressVPN.
I just did the same thing. Nearly the same thing, as I don't have a VM, I've a dedicated router device.
I got my user and password, and the ovpn client config file (for a connection to Paris (France).
Two observation :
Not all ExpressVPN locations may be available for manually configured connections.
And instead of using this :

I used this :
remote-random; comp-lzo no; verify-x509-name Server name-prefix; key-direction 1; route-method exe; route-delay 2; tun-mtu 1500; fragment 1450; mssfix 1450; sndbuf 524288; rcvbuf 524288Clicked Save, and back on the main dashboard :

Note that I'm not using it right now, I'm not pushing any traffic through it. It's just connected.
@hkohila said in Setting up ExpressVPN with OpenVPN:
I have been almost daily in contact with ExpressVPN support to fix this issue, but they are not able to fix it so far.
The ExpressVPN exists for helping you with phone, pad and PC/MAC app issues.
They can't be aware of the thousands of different router models out there.
The 'manual' method exists with a condition : You can use it, but you're on your own.I re read the entire setup from here.
It's still valid.
I did change some final Custom settings, see above. -
@Gertjan
Hello,
I downloaded PFSense 2.4.5 and did all the configuration from expressvpn documentation on their website, and applied the changes you posted. Still didn't work.
I also tried all of that on PFSense 2.9. Still not working.
Obviously, I am missing something which is preventing it from connecting.
I have attached the openvpn log file for your review.
PFSense2-4-5 Log 10-8-26.txt
NOTE:
PFSense itself is working seamlessly without OPNVPN. all the issues I have is with OPNVPN.

I am open to any suggestion/recommendation to get this up and running.
Thanks!! -
@patient0
I followed the document published on expressVPN website. I also downloaded the version you mentioned and applied the configuration as in the document. but still no luck.
Attached is the LOG file from PFsense for opnvpn for your review.

Any recommendation?
PFSense2-4-5 Log 10-8-26.txt -
Oct 8 15:44:57 openvpn 29824 TLS: Initial packet from [AF_INET]149.19.196.104:1195, sid=460b6b4c 7d50d597 Oct 8 15:45:56 openvpn 29824 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)I presume that "149.19.196.104" is the resolved IP of an express VPN server.
Here is the file "my_expressvpn_france_-paris-_1_udp(1).ovpn" I downloaded Express :
dev tun fast-io persist-key persist-tun nobind remote france-paris-1-ca-version-2.expressnetw.com 1195 remote-random pull comp-lzo no tls-client verify-x509-name Server name-prefix ns-cert-type server key-direction 1 route-method exe route-delay 2 tun-mtu 1500 fragment 1300 mssfix 1200 verb 3 cipher AES-256-GCM auth SHA512 sndbuf 524288 rcvbuf 524288 auth-user-pass <cert> -----BEGIN CERTIFICATE----- MIIDTjCCAregAwIBAgIDKzZvMA0GCSqGSIb3DQEBCwUAMIGFMQswCQYDVQQGEwJV UzELMAkGA1UECBMCQ0ExFTATBgNVBAcTDFNhbkZyYW5jaXNjbzEVMBMGA1UEChMM Rm9ydC1GdW5zdG9uMRgwFgYDVQQDEw9Gb3J0LUZ1bnN0b24gQ0ExITAfBgkqhkiG ...... qzp4aKuQ6j61c6k1UaQQL0tskqWVzslSFvs9NZyUAJLLdGUc5TT2MiLwiXQwd4Uv H6bGeePdhvB4+ZbW7VMD7TE8hZhjhAL4F6yAP1EQvg3LDA== -----END CERTIFICATE----- </cert> <key> -----BEGIN RSA PRIVATE KEY----- MIIEpAIBAAKCAQEAqzmLfyjotrjAxnr96V4PI9UjuCf+BFVgxe7yXCq9o62Zag/8 7gBcdltWFr8Lpjzujyh+D1PettWjXYrpmlJL/0aZQn85558aqG4SbkxNqAPq0tWz ..... Uhl5sCGfMKkLShiON5P2oxZa+B0aPtQjsdnsFPa1uaZkK4c++SS6AetzYRpVDLmL p7/1CulE0z3O0sBekpwiuaqLJ9ZccC81g4+2j8j6c50rIAct3hxIxw== -----END RSA PRIVATE KEY----- </key> <tls-auth> # # 2048 bit OpenVPN static key # -----BEGIN OpenVPN Static key V1----- 48d9999bd71095b10649c7cb471c1051 .... 7aed27125592a7148d25c87fdbe0a3f6 -----END OpenVPN Static key V1----- </tls-auth> <ca> -----BEGIN CERTIFICATE----- MIIGqjCCBJKgAwIBAgIUfTu1OKHHguAcfIyUn3CIZl2EMDcwDQYJKoZIhvcNAQEN BQAwgYUxCzAJBgNVBAYTAlZHMQwwCgYDVQQIDANCVkkxEzARBgNVBAoMCkV4cHJl .... tRTiqYxB9QAqs7u5WZ82XiYOImN3SgrTcJQPHXWtbUmsx6pxCkHelMMgWCfPSkWG BQCYm/vuOx6Ysea22jH0zuy8GCTYASy7w6ks9JBe -----END CERTIFICATE----- </ca>Here :

you should have this :

You can create the 'CA' certicate with everything you found between the
<ca> -----BEGIN CERTIFICATE----- MIIGqjCCBJKgAwIBAgIUfTu1OKHHguAcfIyUn3CIZl2EMDcwDQYJKoZIhvcNAQEN BQAwgYUxCzAJBgNVBAYTAlZHMQwwCgYDVQQIDANCVkkxEzARBgNVBAoMCkV4cHJl .... tRTiqYxB9QAqs7u5WZ82XiYOImN3SgrTcJQPHXWtbUmsx6pxCkHelMMgWCfPSkWG BQCYm/vuOx6Ysea22jH0zuy8GCTYASy7w6ks9JBe -----END CERTIFICATE----- </ca>I've called it "CA ExpressVPN 2".
You use it here : VPN > OpenVPN > Clients > Edit

Here :

you add a certificate :


Here you copy the two entries :
<cert> -----BEGIN CERTIFICATE----- MIIDTjCCAregAwIBAgIDKzZvMA0GCSqGSIb3DQEBCwUAMIGFMQswCQYDVQQGEwJV UzELMAkGA1UECBMCQ0ExFTATBgNVBAcTDFNhbkZyYW5jaXNjbzEVMBMGA1UEChMM Rm9ydC1GdW5zdG9uMRgwFgYDVQQDEw9Gb3J0LUZ1bnN0b24gQ0ExITAfBgkqhkiG ...... qzp4aKuQ6j61c6k1UaQQL0tskqWVzslSFvs9NZyUAJLLdGUc5TT2MiLwiXQwd4Uv H6bGeePdhvB4+ZbW7VMD7TE8hZhjhAL4F6yAP1EQvg3LDA== -----END CERTIFICATE----- </cert> <key> -----BEGIN RSA PRIVATE KEY----- MIIEpAIBAAKCAQEAqzmLfyjotrjAxnr96V4PI9UjuCf+BFVgxe7yXCq9o62Zag/8 7gBcdltWFr8Lpjzujyh+D1PettWjXYrpmlJL/0aZQn85558aqG4SbkxNqAPq0tWz ..... Uhl5sCGfMKkLShiON5P2oxZa+B0aPtQjsdnsFPa1uaZkK4c++SS6AetzYRpVDLmL p7/1CulE0z3O0sBekpwiuaqLJ9ZccC81g4+2j8j6c50rIAct3hxIxw== -----END RSA PRIVATE KEY----- </key>"Certificate data" and "Private key data", so everything between <cert> and </cert> and <key> ... </key>.
You use this certificate here :

In the "my_expressvpn_france_-paris-_1_udp(1).ovpn" file you also found :
<tls-auth> # # 2048 bit OpenVPN static key # -----BEGIN OpenVPN Static key V1----- 48d9999bd71095b10649c7cb471c1051 .... 7aed27125592a7148d25c87fdbe0a3f6 -----END OpenVPN Static key V1----- </tls-auth>and you copy this part in the VPN Client setup here :

Other TLS related stuff :

Check that you have the 3 "Data Encryption Algorithms" shown.
I presume you've entered your user ID here :

The top part of the config :

If all is copied correctly, no more TLS errors.
edit : setting up a opvn client is no more, and no less as "copy paste things".
-
Hello,
I did everything you suggested connecting expressVPN to my pfsense. nothing worked so far. (To make sure that I have no network issue) I tried the free plan from ProtonVPN. it shows that the interface is up but its not obtaining an ip address. I attached the log file from ProtonVPN on PFSense. for your review.
PFSense-ProtonVPN-10-14-26.txtI even tried a fresh PFSense install on a laptop with 2 NICs and still not able to connect to my expressvpn
I am almost pulling my hair out. I cannot figure out where the issue is coming from.
Am I missing something?
Would you like to remote control the VM maybe you will see something I am not seeing?
Thanks!! -
Your vpn client log file is close to empty.
Here is mine :
<28>1 2026-10-14T13:03:55.566744+02:00 pfSense.bhf.tld openvpn 47928 - - DEPRECATED OPTION: --persist-key option ignored. Keys are now always persisted across restarts.
<28>1 2026-10-14T13:03:55.571481+02:00 pfSense.bhf.tld openvpn 47928 - - WARNING: file '/var/etc/openvpn/client2/up' is group or others accessible<29>1 2026-10-14T13:03:55.571542+02:00 pfSense.bhf.tld openvpn 47928 - - OpenVPN 2.7.5 amd64-portbld-freebsd16.0 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [MH/RECVDA] [AEAD] [DCO] <29>1 2026-10-14T13:03:55.571569+02:00 pfSense.bhf.tld openvpn 47928 - - library versions: OpenSSL 3.5.7 9 Jun 2026, LZO 2.10 <29>1 2026-10-14T13:03:55.571615+02:00 pfSense.bhf.tld openvpn 47928 - - DCO version: FreeBSD 16.0-CURRENT #71 plus-RELENG_26_07-n256584-8183aef9d019: Fri Aug 7 21:32:32 UTC 2026 root@pfsense-build-release-amd64-1.eng.atx.netgate.com:/var/jenkins/workspace/pfSense-Plus-snapshots-26_07-main/obj/amd64/FFp9ankS/var/jenkins/workspace/pfSe <29>1 2026-10-14T13:03:55.572798+02:00 pfSense.bhf.tld openvpn 48112 - - MANAGEMENT: unix domain socket listening on /var/etc/openvpn/client2/sock <28>1 2026-10-14T13:03:55.573206+02:00 pfSense.bhf.tld openvpn 48112 - - NOTE: the current --script-security setting may allow this configuration to call user-defined scripts <28>1 2026-10-14T13:03:55.583116+02:00 pfSense.bhf.tld openvpn 48112 - - WARNING: experimental option --capath /var/etc/openvpn/client2/ca <29>1 2026-10-14T13:04:00.677536+02:00 pfSense.bhf.tld openvpn 48112 - - TCP/UDP: Preserving recently used remote address: [AF_INET]45.91.22.211:1195 <29>1 2026-10-14T13:04:00.677724+02:00 pfSense.bhf.tld openvpn 48112 - - Socket Buffers: R=[42080->524288] S=[57344->524288] <29>1 2026-10-14T13:04:00.677842+02:00 pfSense.bhf.tld openvpn 48112 - - UDPv4 link local (bound): [AF_INET]192.168.10.4:0 <29>1 2026-10-14T13:04:00.677984+02:00 pfSense.bhf.tld openvpn 48112 - - UDPv4 link remote: [AF_INET]45.91.22.211:1195 <29>1 2026-10-14T13:04:00.694531+02:00 pfSense.bhf.tld openvpn 48112 - - TLS: Initial packet from [AF_INET]45.91.22.211:1195, sid=cf69ec9d cfaedd64 <28>1 2026-10-14T13:04:00.694630+02:00 pfSense.bhf.tld openvpn 48112 - - WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this <29>1 2026-10-14T13:04:00.739809+02:00 pfSense.bhf.tld openvpn 48112 - - VERIFY WARNING: depth=0, unable to get certificate CRL: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-12147-2a, emailAddress=support@expressvpn.com <29>1 2026-10-14T13:04:00.739920+02:00 pfSense.bhf.tld openvpn 48112 - - VERIFY WARNING: depth=1, unable to get certificate CRL: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA3, emailAddress=support@expressvpn.com <29>1 2026-10-14T13:04:00.740282+02:00 pfSense.bhf.tld openvpn 48112 - - VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA3, emailAddress=support@expressvpn.com <29>1 2026-10-14T13:04:00.741023+02:00 pfSense.bhf.tld openvpn 48112 - - VERIFY KU OK <29>1 2026-10-14T13:04:00.741052+02:00 pfSense.bhf.tld openvpn 48112 - - Validating certificate extended key usage <29>1 2026-10-14T13:04:00.741077+02:00 pfSense.bhf.tld openvpn 48112 - - ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication <29>1 2026-10-14T13:04:00.741099+02:00 pfSense.bhf.tld openvpn 48112 - - VERIFY EKU OK <29>1 2026-10-14T13:04:00.741123+02:00 pfSense.bhf.tld openvpn 48112 - - VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-12147-2a, emailAddress=support@expressvpn.com <29>1 2026-10-14T13:04:00.741140+02:00 pfSense.bhf.tld openvpn 48112 - - VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-12147-2a, emailAddress=support@expressvpn.com <29>1 2026-10-14T13:04:00.764663+02:00 pfSense.bhf.tld openvpn 48112 - - Control Channel: TLSv1.3, cipher TLSv1.3 TLS_AES_256_GCM_SHA384, peer certificate: 4096 bits RSA, signature: RSA-SHA256, peer temporary key: 253 bits X25519, peer signing digest/type: rsa_pss_rsae_sha256 RSASSA-PSS, key agreement: x25519 <29>1 2026-10-14T13:04:00.764713+02:00 pfSense.bhf.tld openvpn 48112 - - [Server-12147-2a] Peer Connection Initiated with [AF_INET]45.91.22.211:1195 <29>1 2026-10-14T13:04:00.764781+02:00 pfSense.bhf.tld openvpn 48112 - - TLS: move_session: dest=TM_ACTIVE src=TM_INITIAL reinit_src=1 <29>1 2026-10-14T13:04:00.764950+02:00 pfSense.bhf.tld openvpn 48112 - - TLS: tls_multi_process: initial untrusted session promoted to trusted <29>1 2026-10-14T13:04:01.808850+02:00 pfSense.bhf.tld openvpn 48112 - - SENT CONTROL [Server-12147-2a]: 'PUSH_REQUEST' (status=1) <29>1 2026-10-14T13:04:01.824739+02:00 pfSense.bhf.tld openvpn 48112 - - PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 10.126.0.1,comp-lzo no,route-gateway 10.126.0.1,topology subnet,ping 10,ping-restart 60,ifconfig 10.126.0.32 255.255.0.0,peer-id 457,cipher AES-256-GCM,protocol-flags cc-exit tls-ekm dyn-tls-crypt,tun-mtu 1500' <27>1 2026-10-14T13:04:01.824961+02:00 pfSense.bhf.tld openvpn 48112 - - Options error: option 'redirect-gateway' cannot be used in this context ([PUSH-OPTIONS]) <27>1 2026-10-14T13:04:01.825061+02:00 pfSense.bhf.tld openvpn 48112 - - Options error: option 'dhcp-option' cannot be used in this context ([PUSH-OPTIONS]) <29>1 2026-10-14T13:04:01.825212+02:00 pfSense.bhf.tld openvpn 48112 - - OPTIONS IMPORT: --ifconfig/up options modified <29>1 2026-10-14T13:04:01.825299+02:00 pfSense.bhf.tld openvpn 48112 - - OPTIONS IMPORT: route-related options modified <29>1 2026-10-14T13:04:01.825384+02:00 pfSense.bhf.tld openvpn 48112 - - OPTIONS IMPORT: tun-mtu set to 1500 <29>1 2026-10-14T13:04:01.825606+02:00 pfSense.bhf.tld openvpn 48112 - - TUN/TAP device ovpnc2 exists previously, keep at program end <29>1 2026-10-14T13:04:01.825841+02:00 pfSense.bhf.tld openvpn 48112 - - TUN/TAP device /dev/tun2 opened <29>1 2026-10-14T13:04:01.825943+02:00 pfSense.bhf.tld openvpn 48112 - - tun/tap device [ovpnc2] opened <29>1 2026-10-14T13:04:01.826037+02:00 pfSense.bhf.tld openvpn 48112 - - /sbin/ifconfig ovpnc2 10.126.0.32/16 mtu 1500 up <29>1 2026-10-14T13:04:01.836010+02:00 pfSense.bhf.tld openvpn 48112 - - /usr/local/sbin/ovpn-linkup ovpnc2 1500 0 10.126.0.32 255.255.0.0 init <29>1 2026-10-14T13:04:01.845524+02:00 pfSense.bhf.tld openvpn 48112 - - Data Channel: cipher 'AES-256-GCM', peer-id: 457, compression: 'stub' <29>1 2026-10-14T13:04:01.845677+02:00 pfSense.bhf.tld openvpn 48112 - - Timers: ping 10, ping-restart 60 <29>1 2026-10-14T13:04:01.845776+02:00 pfSense.bhf.tld openvpn 48112 - - Protocol options: explicit-exit-notify 1, protocol-flags cc-exit tls-ekm dyn-tls-crypt <29>1 2026-10-14T13:04:03.588817+02:00 pfSense.bhf.tld openvpn 48112 - - Initialization Sequence CompletedWe both have this line :
Oct 14 09:48:07 openvpn 36310 UDPv4 link remote: [AF_INET]a.b.c.d:portYour log : no more communication / log lines.
Mine continues withTLS: Initial packet from [AF_INET]a.b.c.d:portand the the rest of my log so you know how it should continue when a connection is established.
Btw :
Options error: option 'redirect-gateway' cannot be used in this context ([PUSH-OPTIONS]) Options error: option 'dhcp-optionMy Client VPN received instructions from the remote ExpessVPN server, and two of them were flagged as an 'error'.
Not really an issue actually.I tend to say : your outgoing connection to "194.180.34.3:5060" (the Proton VPN server) was never reached and/or no info came back.
It's like your uplink 'pfSense WAN' connection is filtered. Like you have an firewall above your pfSense, like an ISP router, ISP itself, etc, you that stops you from connecting to a ... in this case a VPN server.
The good news is : probably nothing is wrong with your local pfSense client VPN setup. The destination vpn server can't be reached.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register LoginPrivacy Policy · Cookie Policy