Proxy, docker compose, or doc is wrong

[thenitai]

Hi there,

This app looks very promising. However, the instructions for using a proxy server are either incomplete or wrong.

It says that OneUptime doesn't do SSL certificates, but then it tries to get the cert, and one can set the LetsEncrypt vars in the config file.

When one tries to add a proxy service, we need to change the OneUptime ports. However, changing the HTTP port (80) and status port (443) to something else doesn't work, i.e. the app doesn't start (or times out forever). Hence, adding Caddy is not possible (at least not on the same server).

Of course, I could also miss something. Any help would be appreciated. Thank you.

[torstenhoegel]

indeed OneUptime’s current SSL implementation for status pages creates challenges when using a reverse proxy like Caddy or Nginx. The recommended approach is to handle all SSL termination at the reverse proxy level and forward HTTP traffic to OneUptime’s containers. Additionally, clarifying documentation on port changes and SSL expectations would help avoid confusion for users. I personally was not successful until now on how to also resolve the status page correctly without making it port 443 and remove the reverse proxy, which makes it impossible to use the dashboard with ssl.

[simlarsen]

Looking into this.