Messages

So I guess there is no problem after all.  I put in a rule to allow connection to that URL after doing setup for failover and apparently it just took some time to function properly with my monitoring software.  Not sure why but when I came in the next morning, it was working.

Hi,

I am still running 22.1.10_4 on a Protectli FW4B with 2 WAN interfaces (Starlink and a local wireless ISP).

I use PeakHour 4 as a bandwidth monitor.  I used to get great high resolution graphs of my bandwidth usage using a UPNP monitoring target at this address (http://192.168.191.1:2189/rootDesc.xml).  I'm not sure why this no longer works.  I can still pull that address up fine in my browser but don't see any bandwidth counters.  It seems that it does talk to it as it pulls up "FreeBSD router" as the device name but the rest says:

Responding to queries - no
Reporting bandwidth - no
High-Capacity counters -no

I am able to monitor via SNMP but the graphing is much less detailed than it was over UPNP.  Was functionality removed at some point?  Is it ever going to come back?

I see settings to add a v3 user but don't see anywhere to disable v1 or v2 use?

Gotcha.  That make sense. Thanks.

FWIW, still had the issue under the new version for me.

Thx, will check it out.  Yes, it now uses HTTPS by default with a self signed cert which is fine, but under Catalina, that is now much harder when using Chrome than it used to be under Mojave.  Check out the link I posted for the Google support forum about this topic.  Interesting.

I guess b/c I'm new to OPNsense and didn't know what to do and just wanted to log in to the GUI using my normal browser so I could start looking at configuration options.  Do you have step by step instructions for doing the Lets' Encrypt plugin and replacing web GUI cert?

I figured it out.  It has to do with Catalina OS on my Mac and Chrome.

https://support.google.com/chrome/thread/9253301?hl=en

The above link had some options.

- You can click anywhere on the warning page in whitespace somewhere and literally type in "thisisunsafe" and then you will go to the login page

- You can make OSX/Chrome trust the cert by doing this (from the above link).  Download user cert from System > Certificates

1. Download the Certificate to Desktop
2. Double click the certificate and enter the login credentials to install the certificate in the keychain
3. Once done. Open the Keycahin > Categories > Certificates
4. Double click the installed the certificate and click 'Trust' expander.
5. Select  When using this certificate to : 'Always Trust'
6. Restart the Chrome . Now you will see the 'Proceed to Unsafe Mode'.

I'm having the same problem.  Any suggestions.  FFX lets me bypass the warning, but not Chrome which is my default browser.