Messages

After reading this thread, I got prepped and braced to deal with whatever.  Snapshotted, backed up, already ssh'd in, etc.  But when I went to update...it just updated, no errors, no need to recheck for updates and was on 25.7.6 with no issue?  I also use the mimugmail repo.

I believe it's the traffic graph.  Thats what I see crash out most and first.

Uninstalled the os-cpu-microcode-intel microcode & rebooted to make sure it took effect.

Ran the upgrade to 25.7 device hung, power cycled it and it came up OK so removing the microcode did improve the situation. Unfortunately I'm running this router headless so could not see any errors on screen - I have to take it out of the rack to attach a monitor to it.

I'm going to continue running it without the microcode installed and see how it goes. Following on from Franco said earlier I will look it there is a BIOS update available, it's a small fan less PC so may need to do some research to find it.

PS big thank you to Franco for you extremely rapid and helpful suggestion, I love this community.

I highly recommend using a PIKVM for this type of situation.  I also run my servers headless but still need console from time to time.  Works flawlessly.

Yup this has been happening to me after they did the UI overhaul.  I can only refresh the page, assuming it doesn't hang, to get everything back.

I was under the impression that this functionality was deprecated by Google, so have changed my backup method to Oxidized.

It's going to be and I believe a plugin is what will be suggested.

https://github.com/opnsense/core/issues/8343

Just keying off your use of "instance"...Are you virtualizing it?

You shouldn't need to bridge the interfaces. If the VLANs are all setup correctly, traffic should be routable so a few firewall policies should be all you need. Check the users Windows firewall is configured, too.

Have a read of the Steam FAQ regarding the requirements:
The network transfer happens on TCP port 27040 and it needs to be allowed by local firewall software. You also need to open UDP ports 27031-27036 for client discovery.


Are you able to add in a network diagram?

This!

A few things you can check:

- Encryption Password Mismatch
If you've set a password for encrypting the backups in OPNsense, but it's missing or incorrect during the backup process, the system may still create the file but fail to write the actual config data. Double-check that the password is set and confirmed correctly in System → Configuration → Backups.
- Service Account Permissions
Make sure the Google Drive folder is shared with the service account email (not just your personal Google account). The service account must have Editor access to the folder, or it won't be able to write the file contents—even if it can create the file shell.
- P12 Key or Client ID Issues
If the P12 key is invalid, expired, or mismatched with the service account, authentication may partially succeed (enough to create a file) but fail silently when uploading the actual data. Try re-generating the key and re-uploading it to OPNsense.

Someone else filed a bug in git hub but not sure if it's due to the above or an actual bug.  Mine are backing up fine, I just had one go last night and I'm on the latest version.
https://github.com/opnsense/plugins/issues/4731

Sure thing:

First Create a new Monit Service Test. Image 1.
Then create a Service and point to the Service Test. Image 2


https://imgur.com/a/3klgQ7M

I have the same issue, it's usually because the USB connection isn't ready yet by time it wants to start.  So I just made a monit process check so it starts it up after boot.

That video is from 6 years ago.  The UI has been changed quite a bit since then.  Follow the instructions I provided and it SHOWS you the historical data across the x axis of the graph.

You simply switch the Granularity and then take a look at the x axis.  you'll notice the history goes back months if you use 24 hours.  It doesn't mean show me the last 24 hours, it means each tick represents 24 hours.

You should also consider turning on Hybrid outbound NAT.

Do you have the Thermal Sensors option configured appropriately for your hardware?  Under System:Settings:Miscellaneous.

Just double checked on mine and CPU reporting is still working with my 24.7.7.  Tried repairing or resetting the data in settings?