Gerald Vogt writes:
Why would you double book port 80? That's really a bad idea and causes issues like the one you see...
When I read that I assumed that nginx would resolve in favor of the narrower interface:port declaration. If double-booking is happening, nginx should be issuing an error, or (nginx being pretty picky in my experience) even refusing to start.
Anyway, OP should look for messages about problems binding to ports in the nginx and uwsgi logs.
Your "INTERNAL" server binds to 127.0.0.1 port 80, only.
That's not quite true. Normally the WSGI service will bind to another port for Postorius/HyperKitty, typically 8000.
-- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan