Messages

Just a follow up, I RDP'd into a Windows Server 2019 machine on my network and it's displaying the graph just fine.  It seems to be narrowed down to Windows 11 having issues with the graph.

It's messed up for me too in 25.1.3, where it was working properly before. 
I've tried removing, saving, re-adding etc.  And multiple browsers Brave/Firefox/Edge (barf).  The graph is only half populating.

Apparently the only way to get this working again was to delete the /var/lib/vnstat.db and restart.

When I select 2 WAN interfaces in VnStat, I no longer get any results.
I tried running it for a couple of days and still nothing.  Any ideas to get it working with multi-wan?

Using Brave and just leaving the dashboard (24.7.5) up for several hours causes it to run out of memory as well.
Any way to help troubleshoot this for you?

I can't even get all the widgets to line up to each other. The firewall widget blinks every time it updates which seems out of place.  The CPU widget is, well, busy.  I hope in the future that can be configurable to just show total cpu, or we can get line graphs back like the previous dashboard layout.  Don't mean to pile on, I appreciate the hard work going into this project. 

Widgets are working in Brave for me.  I just updated this morning.

So if not running PPOE at all, and I have 2 gateways (dual WAN provider), should I be checking upstream gateway at all or on both or just one?

Who runs the Twitter account for OPNsense?

You can add an alias for the mac address of the device that is using Netflix.  Then add a LAN rule, direction in, source [ Alias device you just added ], the select whichever Gateway you have for the primary wan.  Make sure rule is high up enough to match.

This is how I force certain Roku's to go out a Spectrum WAN connection so that I can use the Spectrum app and get all the appropriate channels.

Thanks for that.  I went into Google Cloud Console at https://console.cloud.google.com/iam-admin and grabbed one of the service account passwords I had setup for this and re-entered it.  That resolved the issue.

I wonder what happened on 5/25, which was the last successful backup.  Perhaps when I updated to OPNsense 22.1.8_1.

Either way, thanks for the idea!

I'm probably the only one that uses this, but backups to Google drive started failing for me recently.
Has been working for a long time, not sure if something changed on Google's end or what.

Error message:

[29-May-2022 01:00:01 America/New_York] PHP Fatal error:  Uncaught Google_Service_Exception: {
"error": {
  "errors": [
   {
    "domain": "global",
    "reason": "wrongUrlForUpload",
    "message": "Uploads must be sent to the upload URL. Re-send this request to https://www.googleapis.com/upload/drive/v3/files?uploadType=media"
   }
  ],
  "code": 400,
  "message": "Uploads must be sent to the upload URL. Re-send this request to https://www.googleapis.com/upload/drive/v3/files?uploadType=media"
}
}
in /usr/local/share/google-api-php-client/src/Google/Http/REST.php:118
Stack trace:
#0 /usr/local/share/google-api-php-client/src/Google/Http/REST.php(94): Google_Http_REST::decodeHttpResponse(Object(GuzzleHttp\Psr7\Response), Object(GuzzleHttp\Psr7\Request), 'Google_Service_...')
#1 /usr/local/share/google-api-php-client/src/Google/Task/Runner.php(176): Google_Http_REST::doExecute(Object(GuzzleHttp\Client), Object(GuzzleHttp\Psr7\Request), 'Google_Service_...')
#2 /usr/local/share/google-api-php-client/src/Google/Http/REST.php(58): Google_Task_Runner->run()
#3 /usr/l in /usr/local/share/google-api-php-client/src/Google/Http/REST.php on line 118

I just ran into this issue as well on version 22.1.4_1-amd64. 
Enabled statistics for an Alias and boom.

I repeated my steps after rebooting and it crashed again.

Searched here and found this. Also submitted the crash.

How would you go about removing ports and src to free the disk space back up?

I see that this isn't so much a bug in OPNsense as it is a misunderstanding in the GUI.  You can select each driver from the drop down and select enable/disable it.  I thought just choosing the driver once and ensuring it was selected was enough.  I had to go back through each one and ensure it was de-slected.