Scott

Untrue. I work for a global enterprise company that transacts hundreds of millions of dollars via LE certs.

SELinux

The reason is “asymmetric routing”. The return ping packets are traveling a different route on the way out than on the way back.

https://immich.app/

It would mean you’re entrusting the entire security of your network to Dockge’s authentication system.

… and for that reason, I’m out.

I use Rallly.

Ahhh… very good. I avoided all this by running Pihole on its own IP on the LAN using a bridged interface from the host.

This post from Stack Exchange might help you, switching 80 for 53, of course.

You don’t need UDP on port 80 forwarded through. HTTP is TCP only.

Nextcloud does all of this.

E2EE chat.

AudioBookshelf ticks all those requirements.

I’m wrong? You’re saying that IP addressing is one of the most complicated things about computers/networking?

There’s a difference between corporate IT and being a computer geek.

I agree that many IT careers are relatively simple support jobs.

They mentioned computer geeks which implies, to me, people who are deep into computers. In that light, if you’re struggling with concepts of IP addressing then the more-complicated facets of computers and networks will preclude you from an engineering role.

I’m not gate-keeping. I’m simply suggesting that IP addressing is one of the less-complicated things when it comes to computer-geekery.

If you’re a computer geek (even a professional one) and struggle with IP addressing, you won’t be having much of a career.

Wrong type of POST.

Yes, you can.

Without going into specifics, you need to share the network of your DB stack with the stack of the client containers.

Rather than NFS, perhaps iSCSI would be a better fit.

Use a single reverse proxy on that one port… it can then route the requests to the various back ends.

You probably want something that’s Docker-native like Traefik or Caddy.