As per title.
Wondering if anyone else here has had any experience with the self-hosted version of OneUptime? And specifically, has anyone had any luck setting it up behind Nginx Proxy Manager?
I’ve managed to set it up, but I’m honestly not 100% happy with how you have to essentially have two servers to host it (one being a reverse proxy for the admin interface, the other being the application core).
Don’t get me wrong, it’s neat and definitely full featured, but there is still a long way to go with it. For my use case, I wanted a public status page that people can subscribe to for updates. I’d come from UptimeKuma which was fantastic but lacked the subscriber feature. I used to use Cachet back in the day before it became abandonware (the original owner bought the rights back for it and has rebooted development for it, though!).
atzanteol@sh.itjust.works 10 months ago
What do you not like about that? Looking at their docker compose files it seems they start like a dozen services and nginx forwards different paths to each.
iKill101@lemmy.bleh.au 10 months ago
When I say two servers I mean two VMs to get the system to work effectively.
From memory, the admin interface doesn’t get an SSL certificate issued to it. It perpetually stays HTTP. If you don’t set up another server as a reverse proxy, it won’t let you log in due to CORS issues. Add another server as a reverse proxy, and it’ll come good and let you log in.
Hopefully that makes sense?