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

    Restore 1.2.3 Config to 2.1 fails "The Configuration Could Not Be Restored"

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    23 Posts 3 Posters 4.6k 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
      DLeVasseur
      last edited by

      No, this is a standalone box with nothing by my laptop connected.

      So here's what I did that managed to get it working.  I changed the address from .1.1 to .44.1, this allowed me into the webconfigurator on port 80.  I then created a security certificate and changed the webconfigurator over to https and port 443.  I then changed the address back to the original .1.1 and was able to get in using the original address.

      Not sure why but the box just will not accept a port 80 connection if it's IP is the .1.1  443 connection is fine.

      I ran a port scanner and the port is open.  Anyway, 443 should be what is used anyway, so I think all is fine now.

      1 Reply Last reply Reply Quote 0
      • L
        lfph
        last edited by

        Hi everyone,
        i guess i'm on the right section of the forum as me too cannot use my xml file from 1.2.x to 2.1 and i get "The Configuration Could Not Be Restored", not really familiar with xml so i just put it as an attachment if someone has the time to look at it.
        Thanks for the help,
        S.

        pfsense_xml.txt

        1 Reply Last reply Reply Quote 0
        • D
          DLeVasseur
          last edited by

          I'm not sure if it is the cause, but I noticed at the bottom of your XML there is a bunch of package information.  I believe the Wiki states to export the 1.2.3 configuration without package data.  Package data cannot be imported.

          1 Reply Last reply Reply Quote 0
          • L
            lfph
            last edited by

            thanks,
            i have 2 backups 1 with package and 1 without, none are working; here is the one without (i think)

            pfsense_xml1.txt

            1 Reply Last reply Reply Quote 0
            • D
              DLeVasseur
              last edited by

              The steps outlined by Phil earlier in the post worked out beautifully to find the error.  It's really simple, just copy, paste (change the file name), run.

              1 Reply Last reply Reply Quote 0
              • L
                lfph
                last edited by

                i'm sure it does but i don't understand it :-(

                1 Reply Last reply Reply Quote 0
                • D
                  DLeVasseur
                  last edited by

                  The file even fails basic XML validation.  What options are you using when you export it?

                  1 Reply Last reply Reply Quote 0
                  • L
                    lfph
                    last edited by

                    diagnostics - backup

                    1 Reply Last reply Reply Quote 0
                    • D
                      DLeVasseur
                      last edited by

                      You might want to start a new thread.  Did you maybe open the file in another program before trying the import?  They should have come out with .xml extensions not the .txt files you have posted.  The export is a mess there's back slashes after every line and incorrect data in the header.

                      1 Reply Last reply Reply Quote 0
                      • L
                        lfph
                        last edited by

                        Thank you,
                        i will do that! (i have the .xml but just posted .txt).
                        S.

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