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

    XMLPRC version mismatch with Pfsense 2.4.3_1

    HA/CARP/VIPs
    2
    3
    761
    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.
    • P
      pete35
      last edited by

      I have 2 Pfsense with Version 2.4.3_1 ( p1). If i try to configure a CARP Cluster, i got perfect communications on the sync interface but XMLPRC does not sync, because there is a version mismatch on XMLPRC. One site reports 18.1 and the other site 18.0. If i install 2.4.3 on the backup site, it reports version 17.9 mismatch to 18.1.
      So the update from Pfsense 2.4.3 ( XMLPRC Vers. 17.9) to 2.4.3_1 (XMLPRC Vers 18.0) breaks this XMLPRC CARP sync system. How can i update XMLPRC to Vers 18.1 ?

      <a href="https://carsonlam.ca">bintang88</a>
      <a href="https://carsonlam.ca">slot88</a>

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

        If both firewalls are on the same version, they should have the same configuration revision as well. It is possible that something in your configuration isn't upgrading properly to get it to the most recent revision. Both sites should be at 18.0.

        It's possible the site with 18.1 was accidentally upgraded to 2.4.4 and then moved back to 2.4.3, or a similar move to master and back, which may have landed it ahead of the other one. In that case, you would need to fix it manually. Looking at the upgrade code, it should be safe to make a backup and edit the revision to 18.0 and then restore it.

        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!

        1 Reply Last reply Reply Quote 0
        • P
          pete35
          last edited by

          Hi Jimp.

          Thank you, that worked perfectly. Indeed i reverted from 2.4.4 to 2.4.3 and recovered the last configuration, which causes this version mismatch.

          <a href="https://carsonlam.ca">bintang88</a>
          <a href="https://carsonlam.ca">slot88</a>

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