this post was submitted on 23 Feb 2025
42 points (95.7% liked)

Selfhosted

42765 readers
1288 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
42
Need Support: DMZ at home with nginx proxy to LAN (sh.itjust.works)
submitted 20 hours ago by nap@sh.itjust.works to c/selfhosted@lemmy.world
19 comments fedilink hide all child comments
 

Hey,

currently I am at a loss with my setup and can't figure out whats going wrong. I'm preparing a migration of my private root server to my @Home Setup. The idea was to create a DMZ for all those Server with Public Internet Access and put them into a DMZ.

Now I got a Public OPNsense, some Modem from my ISP, a Unifi Dream Machine (that manages LAN and stuff) and another OPNsense inside my DMZ.

There is a Wireguard Tunnel connecting the two OPNsense, the local one got a 0.0.0.0/0 route as Peer Network.

If I now try to access any Website, managed by the Nginx Proxy 192.168.1.1/24, it works fine as long as the Website is inside the DMZ.

My Problem now is to make the green path happen to access stuff inside my LAN over the Public OPNsense.

The proxy is able to curl the LAN Websites and i can Ping and Trace all the IPs but something is broken. I can see the Packages arrive at the LAN website and make it back to the public OPNsense but my browser will always get a "timed out" :'(

you are viewing a single comment's thread
view the rest of the comments
[–] InnerScientist@lemmy.world 3 points 20 hours ago (7 children)

Check DNS, MTU and do a full wireshark capture from the Client using both curl and the browser.

[–] nap@sh.itjust.works 3 points 19 hours ago (1 children)

green boxes are IP, red are FQDN

Curl capture (made first so DNS is captured aswell)

Firefox capture

[–] just_another_person@lemmy.world 6 points 18 hours ago (1 children)

You have a loopback. Says it right there.

From your diagram it looks like you're have two reverse proxies chained together...why?

[–] nap@sh.itjust.works 3 points 18 hours ago (1 children)

Never got the time to learn to read Captures :'(

At a time I tried to use two proxies but I changed it back to one. The host I try to reach is a Docker Host with Immich running. So the only real proxy should be "192.168.1.1".

[–] just_another_person@lemmy.world 2 points 18 hours ago* (last edited 18 hours ago) (1 children)

If it's 192.168.1.1, then your DNS has the wrong address somewhere. It's looking for 35.242

[–] nap@sh.itjust.works 1 points 18 hours ago (1 children)

What? That's totally confusing. Took my Laptop (192.168.35.242), tethered to my Mobile (192.168.35.116) and wiresharked. 192.168.35.0/24 should never ever be a part of my Network.

[–] just_another_person@lemmy.world 3 points 17 hours ago* (last edited 17 hours ago) (1 children)

Read your own screenshot

If you want to simplify things, do this:

  1. Remove all the proxy mess in between the service and network
  2. Make sure it works properly, and you can address it by name
  3. Add proxy back and point to DNS to it
  4. Test again

Then just keep adding things back and find where it's breaking. I'm positive you have a hostname mismatch, or a messed up DNS record if you're using multiple proxies. Curl output would be helpful. Also check dig (hostname) to see what your DNS is responding with.

[–] nap@sh.itjust.works 3 points 17 hours ago

I think I let it rest for a day, I'm confused

load more comments (5 replies)