this post was submitted on 01 Jan 2024
953 points (97.5% liked)

Selfhosted

42670 readers
564 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
 
(page 2) 50 comments
sorted by: hot top controversial new old
[–] fury@lemmy.world 6 points 1 year 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.

[–] gerowen@lemmy.world 5 points 1 year ago* (last edited 1 year ago) (1 children)

I've hosted mine for years on my own bare metal Debian/Apache install and 28 is the first update that has been a major pain. I've had the occasional need to install a new package to enable a new feature, or needed to add new/missing indices to the database, but the web interface literally tells you how to do those things, so they're not hard.

28 though broke several of the "featured" apps that I use regularly, like "Retention". It also introduced some questionable UI changes that they had to fix with the recent .1 update. I'll get occasional errors when trying to move or delete files in the web interface and everything. 28 really feels like beta software, even though we're a point release in and I got it from the "stable" update channel.

[–] mhzawadi@lemmy.horwood.cloud 3 points 1 year ago (3 children)

I've not moved to 28 yet, might wait a bit longer from your post. My 27 is rock solid, I don't understand why so many have issues with nextcloud.

Maybe the docker installs are pants

load more comments (3 replies)
[–] MangoPenguin@lemmy.blahaj.zone 5 points 1 year ago (3 children)

Nextcloud for me too, would break because of updates requiring manual DB updates sometimes, apps would randomly stop working after updating too, or the 2 times it caused total data loss on all my synced devices and the server itself which required a full restore from backups.

After getting rid of it and switching to Syncthing + Filebrowser + SFTPGo for WebDAV I haven't really had anything break since then (about a year now). Stuff also runs much faster, NC was extremely slow even on good hardware with all their recommended settings for performance.

load more comments (3 replies)
[–] njordomir@lemmy.world 5 points 1 year ago

I won't update without first creating an image of the server to roll back to. Like others on here, the web updater almost always fails and goes into maintenance mode and I have to ssh in to fix it.

Having said that, functionally, I have no issues. Only when upgrading does the whole thing shit the bed.

[–] biddy@feddit.nl 4 points 1 year ago (1 children)

I haven't had any issues with Nextcloud yet. But any torrent client refuses to work. I've tried various qbittorrent containers, transmission, deluge briefly, they all work for a while but eventual refuse to do anything.

load more comments (1 replies)
[–] Kalcifer@sh.itjust.works 4 points 1 year ago (3 children)

Well dang, I have Nextcloud installed as a snap (which has been perfectly stable for me when running on Ubuntu Server), but I was thinking of switching over to a docker installation; this thread doesn't exactly fill me with enthusiasm for that idea...

load more comments (3 replies)
[–] art@lemmy.world 4 points 1 year ago (3 children)

The only device running Snap in my house is a Raspberry Pi running the Snap Nextcloud and it's rock solid.

This might be a deployment issue. How are most people running it?

load more comments (3 replies)
[–] neurospice@lemmy.dbzer0.com 4 points 1 year ago

I had TOTP die for one user on my Nextcloud. I tried to disable it, but it "didn't exist". I tried to enable it, but it was already enabled. It would come up when I used occ twofactorauth:state user. I ended up fixing it by (force) disabling the app and re-enabling it. It didn't break any other user's TOTP and it fixed problem-user's TOTP. No idea what went wrong, but I get these random issues with Nextcloud sometimes.

The plus side to this is I've learnt how to use Mariadb and I've gotten better at debugging things.

[–] LordKitsuna@lemmy.world 4 points 1 year ago (1 children)

I didn't realize that next Cloud was so bad, might I recommend people having issues try Seafile? Also open source and I've been using it for many years without issues. It doesn't have as many features and it doesn't look as shiny but it's rock solid

Have a random meme from my instance

https://seafile.kitsuna.net/f/074ad17b12ad47e8a958/

[–] sebsch@discuss.tchncs.de 4 points 1 year ago (1 children)

Nextcloud ist just fine. Using it since more than 7 years now with zero problems

[–] Geert@lemmy.world 3 points 1 year ago

I'm having a hard time believing that.. There is a difference between being able to fix the update issues every time without problems or having no problems at all. But if so, neat.

[–] NegativeLookBehind@kbin.social 3 points 1 year ago (1 children)

I’m not self hosting an instance, but kbin is super fucking broken lately and it’s getting really frustrating. It’s been about a week. I submitted a ticket in their Git repo, but no response.

[–] tal@lemmy.today 4 points 1 year ago

The most-recent release of lemmy dicked up outbound federation pretty badly on the instance I use.

[–] DarkDarkHouse@lemmy.sdf.org 3 points 1 year ago (3 children)

For me it’s Pi-hole. For six months it runs fine, then dies so horribly I resort to snapshot rollback and we both pretend it never happened.

load more comments (3 replies)
[–] NathanUp@lemmy.ml 3 points 1 year ago

Invidious. It's to be expected for something like that though.

[–] SomethingBurger@jlai.lu 3 points 1 year ago

Paperless often randomly stops accepting new documents. I have to wait several hours or restart it.

[–] marble@sh.itjust.works 3 points 1 year ago

I gave up on owncloud just before it became nextcloud because it kept breaking every time I updated it.

Wallabag is similar for me now. I'm stuck on a slightly out of date version because I can't get newer ones to run. Everything else I self host is painless though.

To be honest, no. I run in a Truenas Jail, and its stable for me. Just a bit slow for big files sometimes.

[–] Treczoks@lemmy.world 3 points 1 year ago (7 children)

The very same reason why I gave up on Nextcloud. Too many nasty surprises.

load more comments (7 replies)
[–] butt_mountain_69420@lemmy.world 3 points 1 year ago (3 children)

Currently dealing with this nonsense,

and this accompanying nonsense:

load more comments (3 replies)
[–] rambos@lemm.ee 2 points 1 year ago

Bad stories about nextcloud scare me 😂 I hope Im not gonna jinx myself, but my nextcloud runs super stable for almost a year. I get some errors while updating, but service doesnt stop working and its usually simple fix by following the message it shows.

I removed apps that I dont use (most of them) and web ui became super fast on my budget server

Actually all services are so smooth and almost no issues, maybe beginner luck 😉

[–] virtueisdead@lemmy.dbzer0.com 2 points 1 year ago

Invidious. It got so bad that I just gave up and switched to piped which has been... well, not perfect, but definitely far more consistent.

load more comments
view more: ‹ prev next ›