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

    config backup failure

    Scheduled Pinned Locked Moved General pfSense Questions
    8 Posts 4 Posters 1.3k 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
      davidstoll
      last edited by davidstoll

      I have been getting regular notifications regarding my automatic configuration change backup

      An error occurred while uploading the encrypted Netgate pfSense Plus configuration to https://acb.netgate.com/save 
      (Failed to connect to acb.netgate.com port 443 after 141 ms: Couldn't connect to server
      

      I'm not sure what to check/fix? They seem to be listed/populated ok in the restore tab.

      Thank you for any direction you can give me.

      1 Reply Last reply Reply Quote 0
      • bmeeksB
        bmeeks
        last edited by

        What type of configuration change are you making that triggers this message?

        I've noticed on my system, as I was experiementing with getting IPv6 working, that whenever I saved a change that resulted in the WAN interface being cycled I would see this message. Then shortly thereafter the change would appear to get saved okay.

        I think what's happening is a type of race condition. The automatic save is attempted before the WAN interface is completely back up and ready. Because the WAN is "down briefly" due to my change (fiddling with DHCPv6 prefix delegation), the attempt to communicate out will naturally fail. Then the WAN interface completes its restart and things are fine.

        D 1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          The ACB backups are queued and should eventually succeed when the connection returns.

          bmeeksB 1 Reply Last reply Reply Quote 1
          • bmeeksB
            bmeeks @stephenw10
            last edited by

            @stephenw10 said in config backup failure:

            The ACB backups are queued and should eventually succeed when the connection returns.

            Ah - that's why I see a subsequent attempt that succeeds. Thanks for the explanation.

            1 Reply Last reply Reply Quote 1
            • D
              davidstoll @bmeeks
              last edited by

              @bmeeks Here is what appeared to have fixed it....I disabled the backup in the auto config backup tab/page (unchecked it), saved, and re-checked it (re-enabling it), saved. Seems to have fixed it.

              Something just needed to get reset I guess?

              bmeeksB 1 Reply Last reply Reply Quote 0
              • bmeeksB
                bmeeks @davidstoll
                last edited by

                @davidstoll said in config backup failure:

                @bmeeks Here is what appeared to have fixed it....I disabled the backup in the auto config backup tab/page (unchecked it), saved, and re-checked it (re-enabling it), saved. Seems to have fixed it.

                Something just needed to get reset I guess?

                Possibly, but what kinds of changes were you making before when it was "broken"?

                My experience was that anything that might cause the WAN interface to "cycle" would result in at least one failure of the automatic backup because I think it was trying to save the change before the WAN was back up. But as @stephenw10 pointed out, the algorithm queues up "config backups" and will continue attempting to execute them until successful. In my case, once the WAN was fully up, the config backup would succeed and clear the queue.

                If yours was failing for other types of config changes that were not cycling the interface outbound traffic was using, then you likely did have a different problem.

                D 1 Reply Last reply Reply Quote 0
                • D
                  davidstoll @bmeeks
                  last edited by

                  @bmeeks that is a great question. I was just changing rules (enabling/disabling) my kids access in the firewall rules. However, now I don't get those errors when I make those same changes.

                  1 Reply Last reply Reply Quote 0
                  • JonathanLeeJ
                    JonathanLee
                    last edited by

                    I had that same issue it seemed to resolve itself after a package reinstall for me.

                    Make sure to upvote

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