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

config.xml - The configuration could not be restored.

Scheduled Pinned Locked Moved General pfSense Questions
4 Posts 2 Posters 1.1k Views 3 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.
  • Z Offline
    zauberplume
    last edited by Apr 8, 2020, 6:59 AM

    Hello dear reader,

    I'm trying to restore a config.xml, generated by a version 1.2.2 pfsense, on a version 2.4.5 pfsense and I'm getting following error:

    The following input errors were detected:
    
        The configuration could not be restored.
    

    Due to a missing error code/message I tried looking for errors in different error logs but no luck.
    Does anybody have an idea what I could do next?
    I feel a bit lost.

    B 1 Reply Last reply Apr 8, 2020, 12:56 PM Reply Quote 0
    • B Offline
      bmeeks @zauberplume
      last edited by Apr 8, 2020, 12:56 PM

      @zauberplume said in config.xml - The configuration could not be restored.:

      Hello dear reader,

      I'm trying to restore a config.xml, generated by a version 1.2.2 pfsense, on a version 2.4.5 pfsense and I'm getting following error:

      The following input errors were detected:
      
          The configuration could not be restored.
      

      Due to a missing error code/message I tried looking for errors in different error logs but no luck.
      Does anybody have an idea what I could do next?
      I feel a bit lost.

      Trying to go directly from 1.2.2 (if that is not a typo) to 2.4.5 is a huge jump. I can see how that would fail. If 1.2.2 is the actual version of that firewall, you would probably be far better off to reconstruct the new 2.4.5 installation from scratch. Another option might be a messy series of incremental upgrades saving the new config each time along the way. A big problem with that would be getting all the required install images.

      If the 1.2.2 is not a typo, I would just start from scratch on a clean 2.4.5 install. And this time stay more current ... ☺.

      1 Reply Last reply Reply Quote 0
      • Z Offline
        zauberplume
        last edited by Apr 8, 2020, 2:50 PM

        I thought that this might have been the problem.
        Alright I'm going to manually add all settings.
        Thank you for clearing this up.

        🎺 🐴 🎵 🦐 🥁 🎵 🎷 🐜
        🎵 🎤🐧 🎙 🐍 🎵

        B 1 Reply Last reply Apr 8, 2020, 3:20 PM Reply Quote 0
        • B Offline
          bmeeks @zauberplume
          last edited by Apr 8, 2020, 3:20 PM

          @zauberplume: also note that pfSense now supports ONLY 64-bit hardware. Just mentioning this since with an installed pfSense version that old it's possible the underlying platform is a 32-bit one.

          1 Reply Last reply Reply Quote 0
          4 out of 4
          • First post
            4/4
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
            This community forum collects and processes your personal information.
            consent.not_received