Topics

I'm running the latest version of OPNsense on a MiniPC, directly connected to a PON from my ISP. It's working fine.

I'm now trying to set up port forwarding to a local Ubuntu 24.04 server at IP 192.168.1.229 (a VM running on Proxmox). I want to run Nextcloud AIO in Docker on that server. Docker is already running, and other services like SearXNG and Vaultwarden are working well. But in this case, I can't get it to work—it seems (I'm not a networking specialist, this is just a hobby) that port forwarding isn't functioning. I'm probably overlooking something or made a silly mistake.

I created a port forwarding rule as shown in the screenshot "Port Forwarding NextcloudAIO.png". The alias NextcloudAIO in the "Redirect target IP" field points to 192.168.1.229. Additionally, a floating rule was created, as shown in "Firewall Floating Nextcloud AIO rule.png".

On the Ubuntu server, to keep testing simple, I installed socat, which is listening for incoming traffic on port 8443 using:

socat -v TCP-LISTEN:8443,fork EXEC:/bin/cat

Then, on an external PC connected via 5G, I run:

curl http://<my external IP>:8443

But nothing happens. Even when I check Firewall > Log Files > Live View in OPNsense and filter by the IP address of the 5G connection or filter on port 8443, I don't see any traffic coming in.
What am I missing or doing wrong? Any help is greatly appreciated!

Ik heb de laatste versie van OPNsense draaien op een MiniPC, direct aangesloten op een PON van mijn provider. Werkt prima.
Ik probeer nu port forwarding op te zetten naar een lokale Ubuntu 2404 server op IP 192.168.1.229 (een VM op Proxmox). Ik wil daar Nextcloud AIO in een docker draaien. Docker loopt al op die server en andere services zoals SearXNG en Vaultwarden werken goed. Ik krijg in dit geval het niet voor elkaar en 't lijkt (ik ben geen netwerkspecialist, dit is een hobby) erop dat de port forwarding niet werkt. Waarschijnlijk zie ik iets over het hoofd, of heb ik iets stoms gedaan.

Ik heb een port forwarding aangemaakt zoals getoond in screenshot 'Port Forwarding NextcloudAIO.png'(het alias NextcloudAIO bij 'Redirect target IP' verwijst naar 192.168.1.229.
Daarbij is een Floating Rule gecreëerd zoals te zien is in screenshot 'Firewall Floating Nextcloud AIO rule.png'

Op de Ubuntu server heb ik, om het testen simpel te maken, socat geinstalleerd, die met

Code Select Expand

socat -v TCP-LISTEN:8443,fork EXEC:/bin/cat luistert naar binnenkomend verkeer op poort 8443

Op een externe PC, verbonden via 5G, draai ik vervolgens

Code Select Expand

curl http://<mijn externe IP>:8443
En dan gebeurt er niets. Ook als ik in OPNsense onder Firewall - Log Files - Live View filter op het IP adres van die 5G verbinding of op poort 8443 zie ik geen verkeer.
Wat zie ik over het hoofd of heb ik verkeerd ingesteld? Alle hulp zeer welkom!

I' ve been running OPNsense for a couple of monthes now an have been using Caddy for a while. Thanks to help from Monviech, Caddy ran fine, but since my update to 24.7.10 Caddy seems to be out of order.

The widget itself shows no errors, but going to the configured URL's now shows error 400 for the domains accessible from the outside and error 502 for the OPNsense URL.

While searching this forum I found: https://forum.opnsense.org/index.php?topic=44440.0.
However, I'm not sure this applies to me as I have no wildcard domains configured

In var/db/caddy/data/caddy/certificates/acme-v02.api.letsencrypt.org-directory I have several folders

Configured domain: name1.domain.nl
Folder: name1.domain.nl

Configured domain: name2.domain.nl
Folder: name2.domain.nl

etc.

Am I overlooking something?
If I need to post more details; please advise.

I'm completely new to OPNsense, just came from Arista NG, who are throwing their Home-users out.
So, apologies if this is a very newbie question

I've installed OPNsense on a miniPC, internet is running fine. I would like to make my Plex Media Server, running on a VM, available to the outside.
I've tried to follow tutorials / YT videos, but I think I'm still missing something.

- Ping to <URL of Plex server> points my external IP address

- Online port check shows that port 32400 is open

- <internal IP addres>:32400 shows PMS is running fine

- Firewall - NAT - Port forward
   Interface: WAN
   TCP/IP Version: IPv4
   Protocol: TCP
   Source: Advanced
   Destination: WAN address
   Destination port range: from 32400 to 32400
   Redirect target IP: Single host or network; <internal IP address>
   Redirect target Port: 32400
   Pool options: Default
   NAT Reflection: Use system default
   Filter rule association: Pass

- Firewall - Rules - WAN
   Action: Pass
   Interface: WAN
   Direction: in
   TCP/IP version: IPv4
   Source: WAN address
   Source port range: from 32400 to 32400
   Schedule: none
   Gateway: default

This does not seem to work; <URL of Plex server>:32400 leads to a time out. Am I overlooking something or doing something stupid?
To quote my robot vacuum; 'I'm stuck, please help'.