Self Hosting Issues

[Agalvez]

Hi Everyone,

I am trying to self host using nginx. I have my internal IP configured to my public domain but when I try to access it I get a 404 Not Found error from Apache. Am i missing a config in Admidio?

[pboosten]

Best to look in the apache logs to see what your browser actually tries to find.

[dylanperez91]

If Apache is returning the 404, it might mean the request is reaching Apache instead of nginx. You may want to double check your reverse proxy or port configuration in front of nginx.

[soleboast]

Hi Everyone,

I am trying to self host using nginx. I have my internal IP configured to my public domain but when I try to access it I get a 404 Not Found error from Apache. Am i missing a config in Admidio?

You’ll want to check your server setup and make sure Nginx is actually listening on ports 80/443 and that Apache isn’t conflicting or still serving that domain. This is likely a web server configuration issue rather than something specific to Admidio.

[pboosten]

Could you please describe your setup? I read nginx and I read apache. Are you using nginx as a reverse proxy?

To get things started, I drew a simple drawing showing my setup (using nginx on both accounts, btw)

https://devnull.boosten.org/admidio/setup.png

[segolden]

Hi Peter,

From what I can see, it looks like you're indeed running nginx as a reverse proxy in front of another nginx instance, which is a pretty clean and efficient setup. Just to confirm: is the front-facing nginx handling SSL termination and forwarding requests internally? Also, are both instances on separate servers or just different containers on the same host? That detail might affect how headers and ports are managed.

[pboosten]

From what I can see, it looks like you're indeed running nginx as a reverse proxy in front of another nginx instance, which is a pretty clean and efficient setup. Just to confirm: is the front-facing nginx handling SSL termination and forwarding requests internally? Also, are both instances on separate servers or just different containers on the same host? That detail might affect how headers and ports are managed.

Hi segolden,

I wasn't the one having problems here, I wanted to reignite the discussion with Agalvez, who didn't respond anymore.

But to answer your questions: the reverse proxy indeed terminates the SSL connection and forwards plain http to the internal servers. They are actually 3 different jails running on one physical FreeBSD machine, but it really doesn't matter whether or not they run on the same machine or not, if your reverse proxy is configured correctly. I actually terminate several sites (with different domains) on that same reverse proxy.