this post was submitted on 01 Jan 2024
989 points (97.2% liked)

Selfhosted

40394 readers
392 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

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

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] fury@lemmy.world 8 points 11 months ago

The problem child for me right now is a game built in node.js that I'm trying to host/fix. It's lagging at random with very little reason, crashing in new and interesting ways every day, and resisting almost all attempts at instrumentation & debugging. To the point most things in DevTools just lock it up full stop. And it's not compatible with most APMs because most of the traffic occurs over websockets. (I had Datadog working, but all it was saying was most of the CPU time is being spent on garbage collection at the time things go wonky--couldn't get it narrowed down, and I've tried many different GC settings that ultimately didn't help)

I haven't had any major problems with Nextcloud lately, despite the fragile way in which I've installed it at work (Nextcloud and MariaDB both in Kubernetes). It occasionally gets stuck in maintenance mode after an update, because I'm not giving it enough time to run the update and it restarts the container and I haven't given enough thought to what it'd take to increase that time. That's about it. Early on I did have a little trouble maintaining it because of some problems with the storage, or the database container deciding to start over and wipe the volume, but nothing my backups couldn't handle.

I have a hell of a time getting the email to stay working, but that's not necessarily a Nextcloud problem, that's a Microsoft being weird about email problem (according to them it is time to let go of ancient apps that cannot handle oauth2--Nextcloud emailer doesn't support this, same with several other applications we're running, so we have to do some weird email proxy stuff)

I am not surprised to hear some of the stories in this thread, though. Nextcloud's doing a lot of stuff. Lots of failure points.