Here is my setup:

I have multiple DuckDNS domains (and subdomains) pointing to my home IP. My home router has port 80 and port 443 forwarded to Nginx Proxy Manager on my home server. Nginx Proxy Manager points to the appropriate docker container and each one is encrypted with Let’s Encrypt.

Am I missing anything here or is this how I’m supposed to be doing it? Every app that has a DuckDNS url has a password in some shape or form.

  • redlemace@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 hours ago

    Well, here is the CPU load:

    And there is no increase on delay’s or jitter compared to what i’m already facing on the WAN itself.

    It keep’s 6000+ hosts with possible harmful intend away from the ports I need/want open to the world. Actually, the router -while still being bored- offloads the services behind it. I really can’t see a reason not to keep doing it. But, sure, it’s a personal choice.

    • non_burglar@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 minute ago

      Didn’t you say you have whitelist of allowed ips? Why don’t you just drop any other inbound traffic?