5 Ways to Boot pfSense into Safe Mode (Troubleshooting Guide)

2025-04-08

howtokge

pfSense Safe Mode Booting pfSense into Safe Mode

Experiencing a sudden system hiccup with your pfSense firewall can be unnerving, especially when critical network operations hang in the balance. Perhaps a recent configuration change caused unexpected issues, or a problematic package update has thrown things into disarray. Whatever the culprit, regaining control and stability is paramount. Fortunately, pfSense offers a robust safety net: Safe Mode. This powerful feature allows you to boot your firewall with a minimal configuration, providing a stable environment to diagnose and rectify problems without risking further damage. Booting into Safe Mode is often the first crucial step in troubleshooting and restoring your firewall to its optimal state. In this guide, we’ll walk you through the precise methods for accessing Safe Mode, regardless of your access method, whether it be through a direct console connection or remotely via SSH. Moreover, we’ll explore the various options available within Safe Mode and how to effectively utilize them to pinpoint and resolve issues, ultimately restoring your network’s security and performance.

First and foremost, accessing Safe Mode requires a slightly different approach depending on your connection method. If you have physical access to your pfSense firewall, you can initiate Safe Mode directly from the console. During the boot process, watch carefully for the boot menu prompt. Typically, you’ll have a short window of opportunity, often just a few seconds, to interrupt the normal boot sequence. Press the highlighted key, typically ‘8’ or ‘S’, to enter the boot menu. From there, you should see an option specifically for Safe Mode; select it to proceed. Alternatively, if you manage your pfSense firewall remotely via SSH, the process differs slightly. After logging in via SSH, you can use the command reboot -s to trigger a reboot directly into Safe Mode. This command effectively bypasses the need for manual intervention during the boot process, streamlining the procedure for remote administrators. Additionally, understanding the nuances of each access method is crucial for efficient troubleshooting. Whether you’re physically present at the firewall or managing it remotely, knowing how to quickly and reliably enter Safe Mode will significantly reduce downtime and facilitate swift problem resolution.

Once you’ve successfully booted into Safe Mode, you’ll be presented with a streamlined version of the pfSense interface. Here, only essential services are running, minimizing potential conflicts and providing a clean environment for troubleshooting. Within Safe Mode, you have several options at your disposal. You can revert to a previous configuration backup, a particularly useful step if a recent change is suspected to be the root cause of the problem. Furthermore, you can diagnose and uninstall problematic packages that might be interfering with the system’s stability. Safe Mode also provides an opportunity to examine system logs for clues about the issue, offering valuable insights into the events leading up to the malfunction. Finally, after implementing the necessary fixes, rebooting from Safe Mode back into normal operation is straightforward. Simply choose the “Reboot” option from the Safe Mode menu, and pfSense will restart with your applied changes. By strategically utilizing the tools and options available within Safe Mode, you can effectively isolate, diagnose, and resolve a wide range of issues, ultimately ensuring the robust performance and security of your network infrastructure. Remember to document any changes you make while in Safe Mode for future reference and troubleshooting.

Getting your pfSense firewall into safe mode starts with accessing the boot menu. This menu gives you different options for how your firewall starts up, including the coveted safe mode. There are a couple of ways to get to this menu, and the method depends on whether you’re using a physical machine or a virtual one. Let’s break it down.

For a physical pfSense box, you’ll need to be quick on the draw during the initial boot sequence. As soon as you power on the device, keep a close eye on the screen for a message that tells you which key to press to enter the boot menu. This message usually flashes by pretty fast, so you might miss it if you blink. The specific key varies depending on the hardware you’re using. Common keys include “Esc,” “Del,” “F2,” “F10,” “F12,” or even “Enter.” Your hardware’s documentation should specify the correct key. If you’re unsure, try each of these common keys one by one until you find the right one.

If you’re running pfSense in a virtual machine, things are a little different. The method for accessing the boot menu will depend on the virtualization software you’re using, such as VMware, VirtualBox, or Hyper-V. Generally, you’ll need to open the virtual machine’s console window and watch for a prompt during the boot process. For example, in VirtualBox, you would typically press “F2” or repeatedly press the “Esc” key to enter the boot menu. With VMware, you might need to click inside the virtual machine window as it starts and then press “Esc.” Again, consult the documentation for your specific virtualization software for the exact steps.

Once you successfully enter the boot menu, you’ll be presented with several options. These might include booting from different hard drives, CD/DVD drives, or USB devices, as well as the option to boot into pfSense safe mode. Use the arrow keys on your keyboard to navigate through the menu and select the desired option. Usually, “Safe Mode” is clearly labeled. Sometimes it might be listed as “Boot with Safe Mode Options,” “Boot with verbose logging,” or similar. Once you’ve highlighted the correct option, press “Enter” to select it.

Here’s a handy table summarizing the key differences between physical and virtual pfSense installations for accessing the boot menu:

Environment	Method	Typical Keys
Physical Hardware	Watch for on-screen prompt during boot.	Esc, Del, F2, F10, F12, Enter
Virtual Machine (VM)	Access VM console and watch for prompt. Varies depending on the virtualization software.	Esc, F2 (Consult VM software documentation)

Troubleshooting Tip

If you’re having trouble catching the boot menu prompt on a physical machine, try restarting the machine several times. Each attempt gives you another chance to spot the message and press the right key. You can also try connecting a different monitor or keyboard, sometimes peripheral issues can interfere with capturing the boot menu prompt.

Identifying the Safe Mode Option

So, you’re having some trouble with your pfSense firewall and you think booting into Safe Mode might be the solution. That’s a smart move! Safe Mode starts pfSense with a minimal configuration, disabling most third-party packages and services. This can be incredibly helpful for troubleshooting issues caused by a misconfigured package or a problematic service. Finding the Safe Mode option is the first step, and it’s pretty straightforward, depending on how pfSense is showing its boot menu. Let’s walk through the different scenarios.

Most pfSense installations will greet you with a simple text-based menu during boot. This menu usually pops up fairly quickly after the system starts. Look carefully for an option labeled “Boot pfSense in Safe Mode.” It might be worded slightly differently, like “Safe Mode” or “Boot with Safe Mode,” but the core idea will be the same. Once you locate it, use the arrow keys on your keyboard to navigate to the Safe Mode option and then press Enter to select it. pfSense will then proceed to boot in Safe Mode.

Okay, let’s dive a little deeper into using the text-based boot menu. You’ll usually see this menu for a brief period, so keep an eye out right after your computer starts. If you miss it, you’ll need to reboot your pfSense system to try again.

The menu typically presents several numbered options, with one specifically for Safe Mode. Use the up and down arrow keys on your keyboard to move the highlight to the Safe Mode option. Don’t use the left or right arrow keys, as they typically won’t do anything in this menu. Once the correct option is highlighted, press the Enter key to select it. Your pfSense firewall will then begin the boot process in Safe Mode. This might take a little longer than a normal boot, so be patient.

Sometimes, the menu might show other options for booting from different devices or with different configurations. Don’t worry if you see options related to VGA or serial consoles – these are just alternative ways to interact with the boot process. Just focus on finding and selecting the Safe Mode entry.

Here’s a quick visual representation of what you might encounter:

Menu Option	Description
1. Boot pfSense	Starts pfSense normally.
2. Boot pfSense in Safe Mode	Starts pfSense in Safe Mode.
3. Boot from USB	Boots from a connected USB device.

In this example, you would use the down arrow key to highlight option 2 and then press Enter.

Some pfSense setups, particularly those running on newer hardware or virtual machines, might use a graphical menu during boot. This menu is visually more sophisticated than the text-based version. In this case, look for a section or tab related to “Boot Options” or something similar. Within that section, you should find an option for Safe Mode. Selecting this option and confirming your choice should boot pfSense into Safe Mode.

Selecting Safe Mode with Networking

When your pfSense firewall encounters issues, Safe Mode can be a lifesaver. It boots the system with a minimal set of drivers and services, allowing you to troubleshoot problems without the complexity of a full boot. Often, you’ll need network access while in Safe Mode to research solutions, download updates, or access configuration backups. That’s where “Safe Mode with Networking” comes in handy.

To get started, you’ll need to access the pfSense boot menu. This menu appears briefly during the system startup. If your system boots too quickly to see it, you might need to adjust the BIOS settings to pause the boot process or repeatedly press a key (often Esc, Del, or F2) as the system powers on. The exact key depends on your hardware. Consult your motherboard or system documentation if you are unsure.

Choosing the Right Option

Once the pfSense boot menu appears, you’ll see several options. Look for an entry specifically labeled “Safe Mode with Networking” or something similar. The wording can vary slightly depending on the pfSense version. Typically, the options are numbered, and you’ll use the corresponding number keys on your keyboard to select the desired option. After selecting “Safe Mode with Networking,” press Enter to confirm your choice and begin the boot process in this mode.

Troubleshooting Network Connectivity in Safe Mode

Once pfSense has booted into Safe Mode with Networking, the next crucial step is verifying your network connection. The most straightforward way to check this is by trying to access the pfSense web interface. Open a web browser on a computer connected to the same network as your firewall and navigate to the pfSense appliance’s IP address. The default IP address for pfSense is usually 192.168.1.1, but this might be different if you’ve changed it previously. If you cannot remember the IP address, you might need to check the DHCP leases on your network’s router or use a network scanner tool.

If you can access the web interface, congratulations, your network connection is working as expected. However, if you encounter difficulties connecting, several troubleshooting steps can help. Firstly, ensure that your network cables are securely plugged into both the pfSense firewall and your computer. A loose cable can easily disrupt the connection. Next, verify the network settings on your computer. In Safe Mode with Networking, pfSense typically acts as a DHCP server, automatically assigning IP addresses to devices on the network. Make sure your computer is configured to obtain an IP address automatically. This is usually the default setting, but it’s always good to double-check.

If you’re still experiencing connection issues, try pinging the pfSense firewall’s IP address from your computer’s command prompt (or terminal on macOS/Linux). A successful ping indicates basic network connectivity. If the ping fails, examine the network configuration on the pfSense webConfigurator (if accessible) or review your network hardware for any potential problems. Occasionally, a problematic network card or switch can cause connectivity issues even in Safe Mode. Finally, if none of these steps resolve the issue, consult the pfSense documentation or community forums for further assistance. Troubleshooting network issues can be complex, but methodical troubleshooting and readily available resources can help you pinpoint and resolve the problem.

Common Network Issues in Safe Mode and Their Solutions

Issue	Solution
Cannot reach webConfigurator	Check IP address, network cables, and computer’s network settings.
Ping to pfSense fails	Examine network hardware, review pfSense configuration.
Limited network access	Check firewall rules in Safe Mode, ensure necessary services are running.

Selecting Safe Mode without Networking

Sometimes, network issues can prevent you from accessing your pfSense firewall entirely. In these situations, booting into safe mode *without* networking allows you to troubleshoot and resolve configuration problems that might be causing network connectivity failures. This mode loads a minimal set of drivers and services, excluding the network stack, giving you a chance to diagnose and fix the problem locally.

Why Choose Safe Mode without Networking?

Choosing safe mode without networking is particularly useful when a misconfigured network setting renders the pfSense web interface inaccessible. Imagine scenarios like an incorrect IP address assignment, a problematic VLAN configuration, or issues with a newly installed network card. By bypassing the network stack entirely, safe mode without networking provides a clean slate to rectify these issues without being hindered by the very problem you’re trying to solve.

How to Boot into Safe Mode without Networking

Booting into safe mode without networking on pfSense is a straightforward process, accessible directly from the boot menu. Follow these steps to access this troubleshooting environment:

Access the pfSense Boot Menu: As your pfSense system starts up, watch closely for the boot menu prompt. This usually appears briefly on the screen. The exact key to press varies depending on your hardware but is often displayed on the screen (e.g., “Press Esc for boot menu”). Common keys include Escape (Esc), Delete (Del), or one of the Function keys (F1, F2, F10, F11, or F12).
Navigate the Boot Menu: Once the boot menu appears, you’ll see several options. Use the arrow keys on your keyboard to navigate through the listed boot choices.
Select Safe Mode (without Networking): Locate the entry labeled “Safe Mode” or sometimes “Safe Mode (without Networking)”. The precise wording can vary slightly depending on your pfSense version. Highlight this option using the arrow keys.
Confirm Your Selection: After highlighting the “Safe Mode (without Networking)” option, press the Enter key to confirm your selection and begin the boot process in safe mode. Your system will now load a minimal environment without networking enabled.

Once in safe mode without networking, you can access the pfSense console using a directly connected monitor and keyboard. From there, you can utilize command-line tools to diagnose and resolve network configuration issues, examine logs, or revert to previous configurations. Remember, after resolving the issue, reboot your pfSense system to resume normal operation with networking enabled.

Here’s a table summarizing the keys commonly used to access the boot menu on various systems:

Manufacturer	Key
Generic PC	Esc, Del, F1, F2, F10, F11, F12
Dell	F2, F12
HP	Esc, F9, F10
Lenovo	F1, F2, F12, Enter

Remember to consult your specific hardware documentation for the exact key if you are unsure.

Troubleshooting Boot Issues in Safe Mode

Safe Mode is your best friend when your pfSense firewall is acting up. It’s a stripped-down version of the operating system, loading only the essential services and drivers. This helps isolate problems that might be caused by conflicting services, faulty drivers, or misconfigurations. If your firewall won’t boot normally, Safe Mode can be a lifesaver.

Accessing Safe Mode

Accessing Safe Mode in pfSense is pretty straightforward. During the boot process, you’ll see a menu presented. One of the options will clearly be labeled “Safe Mode”. Simply select it using the arrow keys and press Enter. Your firewall will then boot into this stripped-down mode.

Common Issues Resolved in Safe Mode

Safe Mode can help you address various problems. Think of issues like recent package installations that messed things up, configuration changes gone wrong, or even driver conflicts. By booting into Safe Mode, you can often revert these changes or uninstall problematic packages, getting your firewall back on track.

Navigating the Safe Mode Interface

The Safe Mode interface is basically the same as the standard pfSense interface, but with fewer options available. You’ll still have access to the command line and the web configurator, allowing you to troubleshoot and make necessary changes. Remember, only the core services are running, so some functionality will be limited.

Troubleshooting Specific Issues in Safe Mode

Let’s say you recently installed a new package, and now your pfSense firewall refuses to boot normally. Here’s a breakdown of how Safe Mode can help you pinpoint and fix the problem:

1. Package Conflicts: Booting into Safe Mode disables recently installed packages. If your firewall boots successfully in Safe Mode, there’s a good chance the issue lies with a recently installed package or a conflict between packages. From the Safe Mode web interface, you can remove the suspect package(s).

2. Configuration Errors: Incorrect firewall rules, misconfigured network settings, or other faulty configurations can also prevent a normal boot. Safe Mode lets you access the web configurator, where you can revert to a previous configuration backup or manually correct the problematic settings.

3. Driver Issues: Sometimes, a faulty or incompatible driver can cause boot problems. While less common, this can occur after a system update. In Safe Mode, you can use the command line interface to investigate and potentially remove or reinstall the problematic driver.

4. Investigating Logs: Examining system logs is a powerful troubleshooting technique. Even in Safe Mode, logs are still generated and can provide valuable clues about what went wrong during the regular boot process. Access the logs through the web configurator or the command line.

5. Restoring a Backup: If all else fails, Safe Mode provides a safe environment to restore a previous working configuration backup. This is a crucial step to get your firewall back online quickly. The restore process can usually be initiated through the web configurator.

Troubleshooting Step	Action in Safe Mode
Package Conflict	Uninstall recently installed packages through the web configurator.
Configuration Error	Revert to a previous configuration backup or manually edit settings through the web configurator.
Driver Issue	Investigate and remove or reinstall drivers using the command line.
Log Investigation	Access system logs through the web configurator or command line.
Restore Backup	Restore a previously saved working configuration through the web configurator.

Exiting Safe Mode

Once you’ve resolved the issue, simply reboot your firewall. It should boot normally. If you continue to experience problems, repeat the Safe Mode process and investigate further.

Performing Configuration Restores in Safe Mode

Safe Mode in pfSense provides a stripped-down environment perfect for troubleshooting and recovery. One of the most common uses for Safe Mode is restoring a previous configuration backup, especially when a recent change has rendered the firewall unusable or unstable. This section will walk you through the process of restoring your pfSense configuration while operating in Safe Mode.

Accessing the Configuration Restore Options

Once you’ve successfully booted into Safe Mode (as detailed in previous sections), you’ll be presented with a limited menu of options. Navigate to the option that allows you to restore a configuration. The wording might vary slightly depending on the pfSense version, but generally look for options related to “Restore config” or “Configuration restore”.

Understanding Configuration Backup Options

Before initiating the restore process, it’s important to understand the different backup options available. pfSense typically offers the ability to restore from a local backup stored on the firewall itself or from a remote location, such as a connected USB drive or an external server via a protocol like SCP or FTP. Having multiple backup locations significantly enhances your recovery options, especially in scenarios where the firewall’s internal storage might be compromised.

Choosing the Right Backup File

If you have multiple backups, select the appropriate one. Consider the date and time of the backup and any relevant notes you might have made when creating the backup. Choosing the correct backup is crucial to ensure you revert to a stable and functioning configuration. A common mistake is restoring an older backup which might be missing critical configurations or contain outdated settings.

Navigating the File System

Depending on where your backups are stored, you might need to navigate the file system to locate the specific backup you want to restore. The Safe Mode interface typically provides a basic file browser allowing you to browse directories and select files. Familiarize yourself with the file system structure to quickly find the desired backup file. Pay close attention to file extensions, ensuring you select the correct file format for a pfSense configuration backup.

Verifying Backup Integrity

While not always feasible in Safe Mode, if possible, verify the integrity of the backup before restoring it. Checking the file size and date modified can provide some assurance that the backup file is valid. Corrupted backups can lead to further issues and should be avoided if possible. Ideally, test your backups periodically in a controlled environment to confirm they are functioning as expected.

Initiating the Restore Process

Once you’ve selected the desired backup file, confirm your choice and initiate the restore process. pfSense will then begin overwriting the current configuration with the selected backup. The duration of this process can vary based on the size of the configuration file and the hardware specifications of the firewall. Ensure you do not interrupt this process, as doing so can lead to a corrupted configuration and potentially brick the device.

Monitoring the Restore Progress

The Safe Mode interface usually displays the progress of the restore operation. Observe this progress indicator to gauge the estimated time remaining. If the process stalls or encounters errors, consult the pfSense documentation for troubleshooting steps.

Post-Restore Configuration

After the restore completes, pfSense might automatically reboot, or you might need to reboot manually. Upon reboot, the firewall should now be running with the restored configuration. It’s highly recommended to thoroughly test the firewall functionality after a restore to ensure everything is working as expected. Pay close attention to network connectivity, firewall rules, VPN configurations, and any other critical services you rely on.

Common Restore Issues and Troubleshooting

Issue	Possible Cause	Solution
Restore process fails	Corrupted backup file	Try a different backup file or attempt to repair the corrupted file if possible.
Firewall doesn’t boot after restore	Incompatible configuration	Restore a known good configuration backup.
Network connectivity issues after restore	Incorrect network settings in the restored configuration	Verify and correct network settings in the restored configuration.

Updating Packages and Drivers in Safe Mode

Safe Mode in pfSense offers a controlled environment, ideal for troubleshooting and resolving system issues. One crucial task you can perform in Safe Mode is updating packages and drivers. This can be particularly helpful if a recent update caused instability or if a driver conflict is suspected. While in Safe Mode, pfSense operates with a minimal set of services and drivers, reducing the chances of conflicts and allowing you to pinpoint problematic components.

Why Update in Safe Mode?

Sometimes, a faulty package or driver update can lead to system instability, making it difficult to boot normally. Safe Mode provides a way to revert these changes or install updated versions that address the issue. By booting into Safe Mode, you bypass the potentially problematic driver or package, allowing the system to function in a basic state where you can make necessary adjustments. Think of it as a clean room where you can perform system surgery.

Accessing the pfSense Shell

To update packages and drivers, you’ll need to access the pfSense shell. From the Safe Mode menu, select option 8, “Enter a shell”. This will drop you into a command-line interface where you can execute various commands. Don’t worry, it’s not as intimidating as it sounds. The commands you’ll need are straightforward.

Updating Packages with pkg

pfSense uses the pkg command for package management. The first step is to update the package repository information. This ensures you have access to the latest package versions. Use the following command:

pkg update

Once the repository is updated, you can upgrade all installed packages using:

pkg upgrade -y

The -y flag automatically confirms the update process, saving you from having to manually confirm each package. This is particularly useful when updating multiple packages. After the upgrade process completes, reboot your system to apply the changes.

Updating Drivers (if necessary)

Driver updates are less common than package updates in pfSense. However, if you suspect a driver issue, you can often find updated drivers on the Netgate website or through the FreeBSD Ports collection (pfSense is based on FreeBSD). Consult the pfSense documentation for specific instructions on installing drivers, as the process can vary depending on the driver in question. It is generally recommended to handle driver updates with caution and ensure compatibility before proceeding.

Rebooting After Updates

Once you’ve finished updating packages or drivers, it’s crucial to reboot your system. This applies the changes and allows pfSense to load with the updated components. After rebooting, monitor your system to ensure the updates resolved the initial issue and didn’t introduce any new problems.

Troubleshooting Package Update Issues

Sometimes, package updates might encounter issues. Here’s a simple troubleshooting table to help you:

Issue	Solution
“pkg: No packages available to update”	Ensure your system has internet connectivity in Safe Mode and try running ‘pkg update’ again.
Errors during package download	Check your internet connection and retry the update. Consider using a different DNS server if the issue persists.
System instability after update	Boot back into Safe Mode and try reverting the package to a previous version or uninstalling it.

Additional Tips

Before updating packages or drivers, especially in Safe Mode, it’s a good practice to back up your pfSense configuration. This provides a safety net in case something goes wrong during the update process. You can restore your configuration from the backup if necessary. Additionally, always double-check the compatibility of any drivers you intend to install to avoid potential conflicts. Be sure to consult the official pfSense documentation for the most up-to-date information and best practices.

Understanding the Limitations of Safe Mode

Safe Mode in pfSense is a powerful troubleshooting tool, offering a stripped-down environment to diagnose and fix issues. However, it’s essential to understand that this minimalist approach comes with certain limitations. While Safe Mode can help pinpoint problems, it’s not intended for regular operation and shouldn’t be used as a long-term solution.

Functionality Restrictions

In Safe Mode, pfSense operates with a minimal set of services and drivers. This means many features you rely on in normal operation will be unavailable. For instance, packages you’ve installed for added functionality, like intrusion detection systems (IDS) or VPN servers, won’t be loaded. This allows you to isolate potential issues stemming from these add-ons. Think of it like a doctor performing a targeted exam – they focus on the core systems first before considering external factors.

Network Configuration Changes

While you can make changes to your network configuration in Safe Mode, these changes are generally temporary. Any modifications made in Safe Mode might not persist after a reboot back into normal mode. This is because Safe Mode often uses a different configuration file, prioritizing a known good state to ensure stability. This is helpful for testing configuration changes without permanently affecting your system, allowing you to roll back easily if something goes wrong.

Limited Package Access

As mentioned, packages are generally disabled in Safe Mode. This is a deliberate choice to prevent potential conflicts and streamline troubleshooting. Accessing the package manager is restricted, and you won’t be able to install, uninstall, or update packages while in Safe Mode. Imagine trying to fix a car engine while simultaneously adding new parts – it’s best to isolate the core problem first.

Reduced Performance

While not always noticeable, pfSense may exhibit reduced performance in Safe Mode. This is due to the limited resources being utilized. The focus is on stability and essential functions, not maximum throughput. Consider it like putting your computer in power-saving mode – it’s functional, but not at its peak performance.

Monitoring and Logging Restrictions

Some monitoring and logging functionalities might be limited in Safe Mode. This is because certain logging services might be disabled to conserve resources. While basic logging might still function, detailed analysis might be hampered. Think of it like having a simplified health report instead of a comprehensive medical examination.

Service Unavailability

Certain services essential for day-to-day operations, like DNS resolution or DHCP server functionality, might operate differently or be completely disabled in Safe Mode. This further emphasizes the temporary nature of Safe Mode and its focus on troubleshooting core system functions. It’s like checking the foundation of a house before worrying about the plumbing or electrical systems.

Troubleshooting Focus

Safe Mode’s primary purpose is troubleshooting. It’s designed to help identify and resolve issues related to core system functions, driver conflicts, or problematic configurations. While it can provide clues about issues related to packages, its primary focus is on the base pfSense system itself.

Impact on Existing Connections

Entering Safe Mode can disrupt existing network connections. Because services are disabled or running in a limited capacity, active connections might be dropped. It’s like briefly turning off the power to reset a circuit – there’s a temporary disruption but it allows for a cleaner restart.

Temporary Configuration

Safe Mode utilizes a separate, streamlined configuration. This temporary configuration is loaded to minimize potential conflicts and provide a stable environment for troubleshooting. As such, any changes made to the configuration in Safe Mode, such as network settings or firewall rules, are generally not saved after rebooting back to normal mode. This ensures your primary configuration remains untouched during the troubleshooting process. This temporary setup isolates any changes you make in Safe Mode from your regular setup, protecting your system from unintended consequences.

Feature	Safe Mode Status
Packages	Disabled
Some Services (e.g., DHCP, DNS)	May be disabled or limited
Configuration Changes	Generally not persistent
Performance	Potentially reduced
Monitoring/Logging	May be limited

Booting pfSense into Safe Mode

Booting pfSense into Safe Mode provides a crucial troubleshooting mechanism when encountering issues like misconfigured settings, problematic package installations, or other software-related malfunctions. Safe Mode loads pfSense with a minimal set of drivers and services, allowing you to diagnose and rectify problems that prevent normal operation. This controlled environment facilitates restoring previous configurations, uninstalling problematic packages, or addressing other issues without the interference of potentially conflicting services.

Accessing the pfSense Boot Menu