OPNsense Forum

English Forums => General Discussion => Topic started by: mvdheijkant on August 28, 2022, 08:28:22 pm

Title: OPNsense not accessible after restore
Post by: mvdheijkant on August 28, 2022, 08:28:22 pm
After a sudden crash of OPNSense 22.7.2 it did no longer boot.
because I don't know much about linux and freesbd the only solution I could think of was to reinstall and restore the settings.
After the initial install I could reach 192.168.1.1 directly from my laptop, and was able to restore the latest backup from the explorer. After that internet again worked, restoring my iprange to 192.168.178.x. Also dns and dhcp (as it should) worked again after the restore.

problem now i that I cant access opnsense any more throught http://192.168.178.1/index.php or https://192.168.178.1:1443/index.php.

is there any way to configure some rule or setting, by console, to access my opnsense again from my laptop.
Title: Re: OPNsense not accessible after restore
Post by: mvdheijkant on August 28, 2022, 09:29:28 pm
Sorry about this I had to access it with domain:8443 instead of 1443.

what I did notice is that following plugins reported as missing?

os-acme-client (missing)   3.13   700KiB   OPNsense   ACME Client   
os-clamav (missing)   1.7_1   47.5KiB   OPNsense   Antivirus engine for detecting malicious threats   
os-intrusion-detection-content-et-open (missing)   1.0.1   1.53KiB   OPNsense   IDS Proofpoint ET open ruleset complementary subset for ET Pro Telemetry edition   
os-iperf (missing)   1.0_1   24.6KiB   OPNsense   Connection speed tester   
os-nginx (missing)   1.29   911KiB   OPNsense   Nginx HTTP server and reverse proxy   
os-theme-rebellion (missing)   1.8.8   5.20MiB   OPNsense   A suitably dark theme
Title: Re: OPNsense not accessible after restore
Post by: Patrick M. Hausen on August 28, 2022, 10:20:18 pm
Plugins are not a part of the configuration backup, although their settings frequently are. If you reinstall from scratch you need to reinstall the plugins, too.

There's a wizard for that purpose hidden somewhere in the audit function, IIRC.