Messages

I experienced the same issue after updating to 23.7.2. However, after installing the latest version (1.14.4) of Zenarmor, everything is functioning properly again. Thank you for the quick repair.

I'm trying to configure the ACME Client (3.14_1) to work with the TransIP API v6. Within my control panel at TransIP I can generate a pair of keys, but I don't see an option to define those. There is an option for the API key, but when I enter the generated key, it doesn't work.
So when I try to issue a certificate, the ACME client isn't able to generate a valid token to access the API I suppose.

When I take a look at the log file this is the point where the error occurs.

Key file doesn't seem to be a valid key: /var/etc/acme-client/configs/63af090cca32f5.16942203//secret.key
Error add txt for domain:_acme-challenge.21next.nl

Does anyone have an idea how to make it work?

Good news! Today the solar inverter got online on its own. The previous state was dropped so a new connection could be established this morning. Thanks again for this tip.

Thank you for the suggestion. I've changed the setting into 'aggressive' and I'll let you know if it helps.

Because of the solar inverter shuts down every day and wakes up the next morning, I'm assuming that the state should be dropped otherwise in this case it's preventing the solar inverter to properly establish a (new) connection the next day. It only makes a good connection after I've manually dropped the previous connection (state). Only then the inverter is showing up in Solax Cloud.

In my local network I've put the inverter for the solar panels in it's own vlan with only access to internet and dns. It is perfectly able to connect to the internet and transmit data to Solax Cloud. But I've to reset it's state every day otherwise won't able to talk to Solax Cloud again. Once I've reset it's state 'let out anything from firewall host itself' the connection is reestablished.
Does anyone know how to fix this behavior?

Dat heb ik overwogen, maar de documentatie geeft aan dat het meestal geen zin heeft om IPS te activeren op de WAN interface
https://docs.opnsense.org/manual/ips.html#choosing-an-interface

Het probleem heb ik kunnen traceren. IDS/IPS en Sensei gaan niet samen. Ze maken op vergelijkbare manier denk ik aanspraak op dezelfde netwerk interfaces. Sensei had die al in gebruik voor packet inspectie.

Sinds kort overgestapt van pfSense op OPNsense. Bevalt prima, ik krijg alleen IDS met IPS niet aan de praat.
Ik was een webinar aan het volgen en kwam niet verder dan https://youtu.be/_yIq3GM4gjA?t=1150 met het instellen.
Een alert genereren zoals in de video lukt wel (IDS).
Zodra ik IPS mode inschakel, start Suricata niet meer op.
OPNsense draait niet op een VM, maar op een mini PC i5-7200U met Intel I210-AT netwerk interfaces.
Hardware offloading staat allemaal uit.
Interface is LAN.
Logfile geeft aan [ERRCODE: SC_ERR_NETMAP_CREATE(263)] - opening devname netmap:igb1/R failed: Device busy