iKill101

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

For my non-Aussie friends, the ATO = Australian Taxation Office.

She was asleep like this, but as I picked my phone up she woke up... still with tongue out.

What happened?

Our SSL certificate expired, which rendered our instance unusable - that is, no content would load.

Why'd it happen?

We're not 100% sure. NGINX Proxy Manager is supposed to renew the certificate automatically, but it didn't. I'm suspecting this has something to do with how I've set it up. I'll need a bit of time to investigate further.

Why'd you take soo long to fix it?

Busy with IRL work, and didn't notice it. I haven't had time to jump onto Lemmy in the last 24 hours.

What steps are you taking to ensure this doesn't happen again?

I'll be adding the Lemmy instance to my UptimeKuma server to monitor the cert expiry, and give me notice before it expires. If I can't figure out why it's not renewing automatically, I'll renew the certificate before it expires again.

Unfortunately, some people have decided to post CSAM on remote instances. The moderators of the communities have been very proactive, but because of the federated nature of Lemmy, it means the material had federated.

So like most instances are doing, we've initiated a purge on the pictrs database/filesystem to delete ALL images from the last 24 hours.

Images may appear broken. I'd like to apologise for the inconvenience, but as Lodion said best on his post in [email protected] - "... this is pretty much the nightmare scenario for an instance. I’d rather nuke all images ever than to host such content."

It's pretty disgusting.

For fellow Lemmy admins who are curious, the script to delete is:

sudo find /srv/lemmy/example.com/volumes/pictrs/files -type f -ctime -1 -exec shred {} \;

Be sure to modify the path to point to your pictrs directory!

As per the title, 0.18.4 was released a few days ago and we'll be updating to it in the next hour.

As usual, attached is an overview of the (new) server! Barely a scratch so far. Everything is running optimally.

Thanks for all your support! ❤️

Kinda. There are a few small issues to still figure out, but for the most part we're back and should be federating.

I'll be working over the coming hours to finalise things and fix the niggly errors.

If you notice any errors, please message me or post here.

Cheers!

Hopefully you won't notice much downtime, because it's going to be a relatively simple migration. But if you do notice, apologies in advance!

I plan on doing the migration within the next 24 hours. Possibly sooner. Can't give an exact time at the moment, but check the comments. I'll post updates here.

As per the title, we've just upgraded the instance to 0.18.3. Hopefully this'll fix the database taking up enormous amounts of space!

I've also attached some graphs of the instance's status for the nerds out there.

If you notice any issues, please let us know!

Thanks ❤️