I don’t feel bad at all :)

Happy to help :)

I do not agree with the general political stance of the administration of that instance.

Yep, thanks! Pushed the fixed config

I’m an admin of the lemmy.cafe instance. Literature.cafe is another instance on the same network.

lemmy.cafe is defederated from lemmy.ml

You made me took at this now :D Found the problem. Missing restart: always

It starts just fine, just doesn’t come up on its own after boot. If you’re interested - have a look https://gitlab.com/MithrilFoundation/lemmy.cafe/

It’s probably something obvious like a missed anchor, but it just doesn’t happen often enough for me to assign mental capacity to this.

This was a first for me in ~7 years I’ve been using them. I’ve always found them really good, albeit expensive. And with the ever growing database for lemmy - I’m starting to consider other options.

I’m not actively looking, but I am open to the idea. What I’ve found, though, is that usually people are not cool with what they find at https://lemmy.cafe/instances

I… am not entirely sure this message was intended to come my way, but just in case it was - I have nothing to do with literature.cafe. I remember suggesting keeping it alive as the admin was moving on, but that never materialised. Not sure who’s running it now.

Things should be back.

There’s a problem I never got to figure out where the internal nginx container - sitting between anubis and UI containers - does not come back up after a restart.

The VM this was running on had a fault on DigitalOcean side and got moved to another host. This included booting it back up, which did not bring that nginx container up. API worked, so all apps worked. It’s just the standard, photon and voyager UIs were down.

Apologies.

Ui seems to have gone down. API is still functional. Gimme a minute, will have a look at what’s going on.