Messages

Bei Nextcloud musst du in der config hinterlegen, dass der nginx ein vertrauenswürdiger Proxy ist und das Plugin setzt den Header nach Spezifikationen als Kette von Quell-IP-Adresse und allen Proxies dazwischen. Wenn damit nicht umgegangen werden kann, kannst du X-REAL-IP verwenden. Dann kriegst du nur den nächsten Client, der halt wieder ein Proxy sein kann.

X-REAL-IP delivers the source IP address of the connection to nginx.

DNS-Problem?

You can use a trusted one or you can open the advanced settings.

You are likely not scanning OPNsense but some kind of an embedded device.

You can use a port forwarding rule for exclusion.

Go to the user and generate a key.

There is an API in the background.

In the portal solution or with a few hacks not supported on OPNsense

Die Verknüpfung ist nicht für die Weboberfläche da, sondern zum Beispiel für OpenVPN.

Wenn du eines der beiden großen Proxy-Plugins installiert hast, kann das ein Zertifikat verlangen.

The hosting capability is very restricted as the nginx plugin is running on a firewall appliance. For example, you may not get a database driver you need etc.

It can serve static files or PHP files with not that many PHP extension requirements. So the best thing is to forward the connection to your apache httpd you have already prepared using the nginx reverse proxy. Usually you have to set one or two values on a page and leave the rest at the defaults.
And yes, you could also use nginx on the backend server instead of apache httpd. But that is your application server, you are going to configure and does not matter from OPNsense's point of view.
If OPNsense cannot reach your apache httpd, then check the following:

* does the target host have its own firewall and is it properly configured (allows access from OPNsense to the target application) -> nftables / iptables on linux
* does the apache httpd listen on the correct IP address and port?

Sure you can use any port but QUIC is only used by HTTP 3 in the HTTP context which forces encryption using QUIC so it is HTTPS by default. Other ports for HTTPS than 443 are uncommon.

QUIC is only available via HTTPS, not with HTTP so only UDP/443.

os-ftp-proxy installieren und konfigurieren:

auf feste IP verbinden -> FTP server eintragen rest nach bedarf einstellen.

Dann DNAT regel auf WAN auf den FTP Proxy machen und die verbindung erlauben.

Das wars dann auch schon.

not restart - that will *NOT* regenerate the config. It will do what service control is expected to do - restart only.
The reconfigure button is *ALWAYS* on the bottom of the pages or it will be done when clicking the apply button.