Revision as of 15:29, 23 November 2011 by Anders (Created page with "You probably read this article because something went wrong with your configuration. You have several options, depending on what have happened, and what you like to do. # Can y...")
You probably read this article because something went wrong with your configuration. You have several options, depending on what have happened, and what you like to do.
- Can you still access it using HTTPS? In that case, go to the Configuration > Revision management, select the previous revision, press Checkout, remove the uuid line (in the system scope), and commit it by pressing Apply. This does not require a reboot.
- Can you still access it using SSH or console? In that case, login to the CLI, run configure, run log to find a good configuration revision number (probably the second-last), and finally run rollback X where X is a known working revisions. This does not require a reboot.
- Do you have "physical" console access to it? In that case, reboot it (possibly by disconnecting the power), wait for it to start booting, when you see Press any key for recovery... do so, and run default-config which will commit a new configuration revision. Your old configuration revisions are saved; once accessing the normal administration, you can rollback to one of those.
- As a last resort, reboot it, and press f when prompted right before it boots, and run reset. This of course requires a reboot, and will destroy all previous configuration revisions.