Selfhosted

39124 readers

479 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

Anyone else had experience with OneUptime? (lemmy.bleh.au)

submitted 8 months ago by [email protected] to c/selfhosted

2 comments fedilink hide all child comments

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!).

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 8 months ago (1 children)

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).

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.

[–] [email protected] 1 points 8 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?