Messages

This is a good hint!
I'm using Firefox 130.0.1. After clearing all cache in Firefox under Setting > Privacy & Security > Clear data (everything) and restarting the browser, opened a new tab on OPNsense webpage, installing plugin still doesn't work. But when opening a new private window in Firefox, I was able to install plugins. Also tried with a different browser and it works too. So in the end it seems to be related to old browsing cache from previous OPNsense webpage version but I still don't get why after clearing my cache it won't work.
At least I now have a "workaround".

In the System > Firmware > Plugins page I can see the list of available plugins but when I try to install one by clicking on the '+' button (on the right side of a plugin item), nothing happens and the selected plugin is not installed.
(Also clicking on the 'i' button doesn't display anything)

Hi,

I just installed OPNsense 24.7.4_1 and cannot install any plugin over the web interface.
(OPNsense is installed on a proxmox VM)
Also after one night, clicking on the '+' button still doesn't install anything.
I try several mirrors but doesn't help.
Installing manually over shell with

Code Select Expand


pkg update
pkg install os-qemu-guest-agent

works but in the plugin web-page it appears with

os-qemu-guest-agent (misconfigured)

I don't see any errors in any logs and rebooting doesn't help neither.
What else could I check?

Thanks for helping.

Hi,

great example thanks!

This works on windows PC but unfortunately this classless static routing doesn't seems to work on android device (DHCP client) :(

Hi,

this topic is quite old, but since I didn't found any "integrated" solution and got the same issue between gmail and postfix, I decided to share my solution.
My postfix setting I needed to add in its main.cf file is always_add_missing_headers = yes
In order to make that setting persist a reboot I created a new file named 90-postfix in /usr/local/etc/rc.syshook.d/start with the following content:

Code Select Expand

#!/bin/sh

echo -n "Adding postifx custom configuration 'always_add_missing_headers = yes'..."
echo 'always_add_missing_headers = yes' >> /usr/local/etc/postfix/main.cf
echo -n "Postifx custom configuration changed."

Now each time opnsense will reboot, it will add that specific line to the postfix main.cf file.

Hope that solution will help somebody one day.

I already heard that update to 107.31 makes AGH stopping. Solution was reinstalling AGH and restore configuration file from backup.

Two days ago version 0.107.30 was released, which has turned out to be buggy, yesterday version 0.107.31 was released, which fixes the bugs of the previous version and works great.

I have opnsense v23.1.11 and AGH v0.107.32 and still have AGH that stops after a few hours / days.
In my setup I actually have 2 opnsense instances as master/backup (CARP) and it happens on both instance.
Also to mention, I use one docker container ghcr.io/bakito/adguardhome-sync for synchronizing the AGH configuration between both instances (each running on the master and backup opnsense instance). Maybe this is related somehow?
In my setup I also checked the new option "Primary DNS" since AGH is running on port 53 and Unbound DNS on another port.

Should I try what tiermutter suggested by reinstalling AGH and restore its configuration file from a backup?

Thanks for any advice.

Edit: I catch one time the moment when it crashes. It seems that the CPU consumption get very high:
https://drive.google.com/file/d/1Bq23bpAMBmBV8xU3hd_CZLb7Ck4pL0m6/view?usp=sharing

After killing the process with kill -9 74662 I could restart the AGH service and it runs again for some days (max 48h)

Update: since updating to AGH v0.107.34, the crashes on both opnsense instances are gone.

I already heard that update to 107.31 makes AGH stopping. Solution was reinstalling AGH and restore configuration file from backup.

Two days ago version 0.107.30 was released, which has turned out to be buggy, yesterday version 0.107.31 was released, which fixes the bugs of the previous version and works great.

I have opnsense v23.1.11 and AGH v0.107.32 and still have AGH that stops after a few hours / days.
In my setup I actually have 2 opnsense instances as master/backup (CARP) and it happens on both instance.
Also to mention, I use one docker container ghcr.io/bakito/adguardhome-sync for synchronizing the AGH configuration between both instances (each running on the master and backup opnsense instance). Maybe this is related somehow?
In my setup I also checked the new option "Primary DNS" since AGH is running on port 53 and Unbound DNS on another port.

Should I try what tiermutter suggested by reinstalling AGH and restore its configuration file from a backup?

Thanks for any advice.

Edit: I catch one time the moment when it crashes. It seems that the CPU consumption get very high:
https://drive.google.com/file/d/1Bq23bpAMBmBV8xU3hd_CZLb7Ck4pL0m6/view?usp=sharing

After killing the process with kill -9 74662 I could restart the AGH service and it runs again for some days (max 48h)