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

    Sync not working

    Scheduled Pinned Locked Moved HA/CARP/VIPs
    4 Posts 3 Posters 1.1k 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.
    • D
      dark.fibre
      last edited by

      Hi,
      I set up a pair of new pfsenses and want one of them to sync aliases, rules etc. to the second one.

      The sync-NICs are connected with a bridge cable, they can ping each other, IP are 192.168.0.1 and 192.168.0.2.

      Second FW has a rule at Sync for TCP/UDP Port 443, Destination: WAN-ADRESS

      User admin´s password is set at System: High Availability Sync of Master-FW and identic with admins pw at the Slave.

      But Master always give me "… Communication error occured while attempting XMLRPC sync with username admin https://192.168.2:443

      What is my mistake?

      Fred

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        But Master always give me "… Communication error occured while attempting XMLRPC sync with username admin https://192.168.2:443

        Is this really the URL?

        192.168.2 is not a valid IP address.  You probably want 192.168.0.2.

        Check your settings in System > High Avail. Sync

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • D
          dark.fibre
          last edited by

          Sorry: of course i forgot the "0" in my post.

          The two Sync-NICs own  192.168.0.1 and 192.168.0.2

          Best wishes
          Fred

          1 Reply Last reply Reply Quote 0
          • V
            viragomann
            last edited by

            @dark.fibre:

            The sync-NICs are connected with a bridge cable, they can ping each other, IP are 192.168.0.1 and 192.168.0.2.

            Second FW has a rule at Sync for TCP/UDP Port 443, Destination: WAN-ADRESS

            What is my mistake?

            If you have separated sync-NICs, why do you allow traffic to WAN address for syncing?

            Just add a rule on both boxes on sync interface to allow traffic from any to any and it will be done.
            The sync packets uses pfsync protocol, not TCP nor UDP!

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