Error encountered while starting OPNsense. Please check your connection and try again.
Error encountered while starting OPNsense. Please check your connection and try again.
Watched a YouTube guide for installing OPNsense on my dual lan minipc. It installed smoothly. Connected it to the network and entered the wizard. After some navigation, the connection froze briefly before dropping. I removed everything and connected the firewall to my monitor to check logs—everything appeared to load properly. Then I reconnected the device but still faced issues. I repeated the same process two years ago and it worked perfectly. What could be going wrong now?
Sorry for the delayed response. I can't reach the firewall. It's located in front of my modem and behind my router. After connecting a monitor, the terminal stays blank with no output. I turned off the firewall and restarted it, but it's now stuck on the BIOS boot screen. I'm starting to suspect the device itself is the issue.
I’m observing another issue—when the drive is plugged in, I can’t reach the BIOS even though I press the escape, F12, and delete keys. But when the drive isn’t connected, I can access the BIOS without any problems.
The router serves to manage network traffic and provide internet access. Often it functions as both a firewall and an access point. In BIOS settings, you can disable the boot sequence to observe what processes are running. When connected via USB, it may start OPNsense in live mode, allowing you to check its behavior. Removing the boot drive, such as a SSD, can help confirm this functionality.
It seems like the boot drive is malfunctioning. After removing the SATA SSD, I can access it via F12 and delete it from the BIOS. I connected the SSD through a USB adapter to check for issues, but Windows doesn't recognize it. Disk management isn't showing anything for the drive. When I run CMD and type "wmic logicaldisk get caption," only my two existing SSDs appear. The USB adapter's activity light just flickers. I tried another SSD, which worked. It looks like the drive itself might be faulty. I'm planning to use the new SSD to test if it boots properly.