Thanks for letting me know! Glad it worked out in the end…

Yes my OPNsense guides need a bit of a re-write and more logical structure I think; I’ve received a lot of great feedback on them I need to incorporate.

Enjoy your new firewall ;)

It can be done, just carefully. You can definitely accidentally block yourself out if you set a firewall rule up incorrectly, or in higher precedence of order for example. OPNsense (like almost every firewall known) processes rules in a “top down” order. So you put your blocks at the bottom!!!

Reverse proxy won’t lock you out, essentially that’s just slapping HTTPS on a webserver/service like Jellyfin, so you can access it without requiring a VPN.

Here’s a reverse proxy explainer, pt 2 is the actual setup!

No worries, hope it helps, let me know if you have questions =)

Well hello there!

Yes, the one and only Core Lab Joe, in the digital flesh (packets, tcp-stream!). Thanks for reading and I’m glad it helped you!

I’m picky when writing tech guides and generally will only write (and recommend!) what I run, and what I have experience with, so that would not be traefik.

My entire system/setup is all dockerized as well. I run 50+ dockers, and anything publicly exposed goes through my SWAG instance. It doesn’t matter what reverse proxy you use, or even if the apps are containers or not really, it’s all networking.

That said I’ve got a good Traefik resource for you, FoxxMD Blog and his migrating from SWAG to Traefik post!

One of the things I need to tackle fully myself, understand, break, troubleshoot and then fix is OIDC for myself, so I can write a good guide on it. A lot of apps do natively do it now, but from what I understand for those that do not, you can use Authelia and the like to slap that authentication into (over top) of it.

Never heard of Rayfish but just googled, it’s a mesh VPN so probably wouldn’t want to push that through a reverse proxy to authelia, it would just slow it down…

I personally use wireguard as my VPN, not tailscale or headscale or any of that but I do understand some people need something that can get around CGNAT or other issues.

No I had no issues flipping it over to keydb. I was on redis originally so I stopped the containers, took a backup and simply changed the image I was using for my backend to keydb end it was like a drop in replacement! Didn’t even need to do a dB upgrade or anything complex.

What you could try is an inverse sense of match rule, which by default, allows access to the internet but not to other VLANs. This is what I do and is the standard I think that should be the default!

If you read the LAN rules at the link there, it basically has you setup RFC1918 IP space as an alias, and then setup an inverse option the logic is:

Anything that is NOT Private IP space - ALLOW!

So outbound from that vlan/network/subnet to internet --> Allowed!

Then you make separate rules to actually allow whichever VLAN access to the other, that you want.

Thank you for taking a peek!

Let me know if there’s something you’re looking for. The search function isn’t to bad but sometimes the posts can get buried a bit ;)

This may help as well, and bridges the gap for some with all the changes from v25.x to v26.x.

Core Lab OPNsense upgrade guide

Your rule looks correct at first glance, but I’ll take a peek further. You do need a DHCP pool setup PER VLAN though, so there’s that as well.

Anything that I publicly expose, I have protected with multiple layers up and down my entire stack…

https://corelab.tech/cybersecroadmap/

I’m late to the party, but feel my guides can help. I am biased towards them because I wrote them! ;)

It’s up to date for v26.x with OPN, that said these guides (3 part series) do need a bit of an overhaul but it does cover VLANs, LAGG/Trunks, DNSmasque and DHCP for each VLAN, with pictures etc…

Core Lab OPNsense Guides

It’s literally based off the NAS comparison guide I posted… This is like a text book way to move forward for someone. My solution is like a giant all in one+a NAS, but a lllooottt of people have a decoupled solution.

One of the beautiful things about self-hosting; do what you want.

Welcome to the self-hosting trenches. Don’t worry about the “burning yourself” part - in this hobby, we consider those “tactical lessons.” Everyone has ah, “re-started” things at least a few times!

Actually, your plan isn’t “not very smart”—it’s a classic move we call Decoupling Compute from Storage. It is the most future-proof way to build a Digital Fortress. By separating your “Brain” (HP Mini) from your “Vault” (Asustor), you ensure that if one fails, the other stays standing. This is a great move.

Here’s how I see your planned setup:
**The Command Center: HP Z2 Mini - Xeon and Proxmox **

The Xeon 1245-v5 is a beast compared to that Celeron. Running Proxmox here is exactly the right call.
The Strategy: Use that M.2 drive for your Proxmox “Data” (the LXCs and VM boot drives). Services like Immich and Navidrome rely on fast databases; running them on an SSD on the Xeon node will make them feel lightning-fast.

The Gear: With 32GB of RAM, this is what I’d call an “Elite Node.” You have plenty of head-room to grow.
**
The Vault: Asustor (Celeron N5105) **
TrueNAS SCALE is “Heavy Armor.” Running it on a 2-bay Celeron is like putting tank treads on a scout bike - it’s overkill and eats up the limited RAM that Celeron has to offer.

The OS Choice: I’d strongly suggest OpenMediaVault 8 (OMV) for the Asustor. In my 2026 NAS OS Comparison Guide, I categorize OMV as the “Lightweight Tactical” choice. It’s built on Debian 13, is incredibly lean, and is the best way to turn low-power hardware into a rock-solid network drive. You’ve already tasted the freedom of a custom OS. Going back to ADM now will feel like a “vendor-lock-in” cage. OMV is the perfect middle ground… **
How they talk to each other **
Wipe the Asustor, install OMV, and set up a simple NFS or SMB share. In Proxmox, you “mount” that network share. Your apps on the HP Mini will “see” the Asustor drives as if they were plugged in locally.

Is it a good idea? Yes . If you ever want more drive bays in the future, you just swap out the Asustor “Vault” for something bigger (like a 6-bay DIY build or a UGREEN box), and your HP Mini “Command Center” never even has to go offline.

I recently broke down the “Battle Card” for why OMV is the king of low-power storage nodes in 2026. You might find the comparison table helpful for your specific hardware: NAS OS Comparison