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

    Migrating OpenVPN from 22.01 to 23.01 failed

    Scheduled Pinned Locked Moved OpenVPN
    3 Posts 2 Posters 686 Views
    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.
    • M
      mr-elamin2
      last edited by

      Hi,
      I have installed a new Pfsense V23.01 Virtual Machin and previously I was using V22.01,
      I am using Site to Site VPN and I have backed up all the setting from V22.01 and I restore it to V23.01, everything has worked perfectly except the OpenVPN client doesn't connect to the OpenVPN server which is running also V23.01.
      whenever I reverted back to the old Virtual Machin with V22.01 and the Site to Site connect perfectly but when shutdown V22.01 and Start V23.01 the connection will fail.
      however I have other clients running V2.6ce connected to the server without any problem.
      I am attaching in here some logs and screen shots, I hope if someone could help in that.
      Thanks a lot
      02b1c205-a3a0-418a-81c3-6a61e660a4e4-image.png

      be0e1a5e-fce5-453d-87bc-c3299006a894-image.png

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        https://redmine.pfsense.org/issues/13350

        tl;dr: Remove the tunnel network from your client config, you probably don't need it anyhow.

        If you absolutely do need it, then apply the commit on that redmine issue via the system patches package.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        M 1 Reply Last reply Reply Quote 1
        • M
          mr-elamin2 @jimp
          last edited by

          Dear @jimp
          Thank you very much for your suggestion,
          the problem was resolved by just removing the tunnel network!

          07e6c93d-99c8-473a-abea-932b70ace8bb-image.png

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