Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    NordVPN Curiosity with 2.8.1

    Scheduled Pinned Locked Moved OpenVPN
    5 Posts 4 Posters 97 Views 4 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B Offline
      BrucexLing
      last edited by

      I had NordVPN installed in OpenVPN on pfSense 2.7.2 and running just fine in avoiding geoblocks. Before upgrading to 2.8.1 I created a configuration backup. The upgrade concluded normally. Immediately I observed that I was now being geoblocked in the upgraded 2.8.1. I then restored the 2.7.2 configuration to the 2.8.1 installation and normality returned. I have repeated this process twice now with the same result.

      While it seems I have solved my geoblock problem on 2.8.1 I thought I’d raise the above observation in case it helps someone else.

      GertjanG 1 Reply Last reply Reply Quote 0
      • GertjanG Offline
        Gertjan @BrucexLing
        last edited by

        @BrucexLing

        geoblocking is 'WAN' IP based.
        Did your WAN = VPN WAN IP change while using 2.8.1 ?

        @BrucexLing said in NordVPN Curiosity with 2.8.1:

        While it seems I have solved my geoblock problem on 2.8.1 I thought I’d raise the above observation in case it helps someone else.

        How can someone find this helpful ? By telling it solvable ? What about : how did you solve it ?

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        B 1 Reply Last reply Reply Quote 1
        • B Offline
          BrucexLing @Gertjan
          last edited by

          @Gertjan It may help someone if they discover that they have become geoblocked after the upgrade to 2.8.1. It may be that if they then follow my solution of restoring an earlier config backup from 2.7.2 they could possibly resolve their problem. No guarantees, but worth a try.

          Not sure if the WAN IP (or the VPN IP) changed, but it happened as described 3 out of 3 times.

          KOMK 1 Reply Last reply Reply Quote 0
          • KOMK Offline
            KOM @BrucexLing
            last edited by

            @BrucexLing What probably happened is that the OpenVPN link didn't come up after first upgrade. There is no other rational explanation for your problem. Also, I'm surprised that folks are still using OpenVPN when wireguard is easier to configure and faster.

            tinfoilmattT 1 Reply Last reply Reply Quote 0
            • tinfoilmattT Offline
              tinfoilmatt @KOM
              last edited by

              @KOM said in NordVPN Curiosity with 2.8.1:

              Also, I'm surprised that folks are still using OpenVPN when wireguard [ . . . ]

              Because they're not mutually exclusive.

              [ . . .] is easier to configure and faster.

              You know what they say about opinions...

              1 Reply Last reply Reply Quote 1
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.