Nicholas de Jong

@binhvcom there is a hint in the exception you've provided - somehow you are connecting to port-80 which ordinarily is non-https but the connection is being attempted as a https...

@mkochenough - it sounds like you need to manually restart the `unbound` service to force it to reload the new configuration, try doing a *send_event* with `service restart unbound` as...

@mkochenough - A little more research shows that pfSense actually does a `send_event` using the following input string `service reload dns` - which would seem more likely to address your...

@mkochenough did the [send_event](https://github.com/ndejong/pfsense_fauxapi#send_event) with `service reload dns` resolve your issue?

Hi @Methraton - There are two issues here, the first one is easy, you can issue a `send_event` with POST data `filter reload` to cause the same reload action you...

Yep - the documentation could provide more examples and clear details here If you take a look at the cli help you'll find this hidden in that wall of text...

Confirmed this is somehow an issue. ~~~As best I can tell at this early stage it must have something to do with some kind of change in 18.7.1 because I...

Answering your question:- > Is the range hard-coded into the instance's ip config? Yes and no - what gets added to the OPNsense instance is a syshook script that has...

I suspect there is some kind of race-condition or other timing issue that only presents itself in the region affected which could be happening around the point where the metadata...

Pardon my slow getting back to this, missed your followup question Yes, I've found that using `safety = "safety check"` will cause the full-system Python packages to be included which...