Messages

Id just needs to be unique. It should not be < 1000 since that are the internal rules. The rest is up to you.

Click on the reconfigure button.

Convert every rule to a main rule (some are likely already there if you import the standard ruleset) and assign them.

Some of those rules are totally nonsense for a default WP installation like blocking phpmyadmin since it is not there unless you install it or blocking file extensions that should not exist in a WP installation.

Das nginx plugin kann alles hosten, was PHP oder ein File ist und keine spezielle config braucht. Du kannst ne kleine statische Website mit der Möglichkeit, das runterzuladen anbieten.

Falls du ne einfache Lösung willst:

Es gibt da fertige Lösungen wie Mail in a Box oder wenn du noch mehr brauchst auch groupware wie OX. Wenn du Emails versenden willst, brauchst du sowieso ne Domain wegen dem MX und SPF record.

Static ARP option is likely the best to go.

Maybe a typo somewhere

Does it actually make sense to use TLS between the upstream server and nginx?

If no, go via HTTP. If yes, use a certificate, OPNsense is trusting or disable certificate validation (advanced option; easy but not recommend) in the upstream.

Yes, it is s entire section in config.xml. If you delete this, it will be gone.

Maybe a bug in the configd template. Are there any log files which would indicate that?

If that is the case, create a bug ticket for OPNsense core. CAs in Trust should work.

You don't need any. Just use the new hostname in the http server and the internal one in the upstream server.

avscan ist ein c-icap Modul. Vielleicht hilft es, das mal mit pkg neu zu installieren.

Das Plugin löschen entfernt dessen config nicht. Die Einträge können immer noch referenziert sein.

The slow part of TLS is the key exchange. This is CPU intense. The other part is only possible to accelerate if your hardware has acceleration like AES-NI.