this post was submitted on 01 Jan 2024
3 points (100.0% liked)

Selfhosted

39167 readers
381 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 1 year ago
MODERATORS
 
top 19 comments
sorted by: hot top controversial new old
[–] leraje@lemmy.blahaj.zone 1 points 8 months ago* (last edited 8 months ago)

In my own personal experience, Nextcloud;

  • Needs constant attention to prevent falling over
  • Administration is a mess
  • Takes far too long to get used to its 'little ways'
  • Basics like E2EE don't work
  • Sync works when it feels like it
  • Updating feels like russian roulette
[–] phoenixz@lemmy.ca 1 points 8 months ago (2 children)

Am i the only one left who doesn't want a snap docker Kubernetes container and just installs nextcloud in a normal way and never had any problems?

[–] rummagefibre@lemmy.world 1 points 8 months ago

Same here. I'm just installing it normally, and my nextcloud instance is just chugging along.

[–] PlexSheep@feddit.de 0 points 8 months ago

I like having stuff in containers, it's like a black box which I don't need to touch and only set some higher level configs.

[–] Lem453@lemmy.ca 0 points 8 months ago* (last edited 8 months ago) (1 children)

I've been running nextcloud since before it was nextcloud. Was owncloud then moved to next cloud.

Another user put it best. It always feels 75% complete. Sync isn't fast, gives errors that self correct when restarting the all. Most plugins are even more janky or feel super barren.

I wanted to like it so much but I stopped being able to trust most plugins which meant I had dedicated apps for those things and used nextcloud only for file sync.

If you only want file sync then seafile is vastly superior so that's what I now have.

[–] Sibbo@feddit.de 0 points 8 months ago

Also, syncthing.

[–] MentallyExhausted@reddthat.com 0 points 8 months ago (1 children)

I run it and mariaDB in docker and they run perfectly when left alone, but everything breaks horribly if I try to do an update. I recently figured out that you need to do updates for NC in steps, and docker (unRAID’s, specifically) defaults to jumping to the latest version. I think I figured out how to specify version now so fingers crossed I won’t destroy it the next time I do updates.

[–] atmur@lemmy.world 0 points 8 months ago (1 children)

This is probably what I'm doing wrong. I'm using linuxserver's docker which should be okay to auto update, but it just continuously degrades over time with updates until it becomes non-functional. Random login failures, logs failing to load, file thumbnails disappearing, the goddamn Collabora office docker that absolutely refuses to work for more than one week, etc.

I just nuke the NC docker and database and start from scratch every year or so.

[–] agressivelyPassive@feddit.de 0 points 8 months ago

The problem is, that there are at least two, completely separate update processes going on.

NC updates its internal file structure from time to time, which should be done by NC itself, but isn't activated by default, so you have to run an upgrade script yourself.

Separate from that is the database. I'm not sure, how mariadb handles it, but postgres definitely needs a entirely offline upgrade script on every update.

Absolutely bonkers, if you ask me.

[–] Czeron@lemmy.world 0 points 8 months ago (1 children)

Installed Nextcloud-AIO using the docker script, took about 4 - 5 terminal commands. Practically zero issues! Hopefully someone else can provide some help in the thread!

[–] PlexSheep@feddit.de 0 points 8 months ago

I use nextcloud aio too, it's pretty alright, but the office server does not work.

I'll be phasing out nextcloud, as I have proton ultimate for email hosting anyways and they can guarantee a much higher degree of stability, uptime and security than I can Selfhosting nextcloud.

[–] butt_mountain_69420@lemmy.world 0 points 8 months ago (1 children)

Dude- it's like you're reading my mind. I've installed Nextcloud 4 different times, the most recent being on docker desktop in Win11. I've resorted to using chatgpt to help me with the commands. LITERALLY EVERY STEP RESULTS IN AN ERROR. The Collabora office suite (necessary to view or edit cloud docs without downloading them) WILL NOT DOWNLOAD. The "php -d memory_limit=512M occ app:install richdocumentscode" chatgpt and Nextcloud suggest is not recognized by the terminal. You can't just download Collabora, cuz fuck you, i guess, and you can't access Docker's actual file system from windows explorer.

I've typed nonsense into various black screens for upward of 20 hours now, and nextcloud is "working" locally. I can access my giant hard drive from my android nextcloud app, but it's SLOW AS FUCK.

I can't imagine how many man-hours it would take to open the server to the internet. Makes me want to fucking barf just thinking about it.

I've been fucking with Linux since 2005 and have yet to get a single thing to work correctly. I guess I'm the only one who thinks an (mostly) invisible file system in incomprehensible repetitive folders, made of complete nonsense commands might not be the best way to operate a computer system.

I'm really frustrated if you can't tell.

On another topic, trying to get Ollama to run on my Lubuntu VM was also impossible. I guess if everyone knew it was going to force you to somehow retroactively configure every motherfucking aspect of the install nobody would bother. You can sudo all day and it still denies me permission to do things LISTED IN THE MOTHERFUCKING DOCUMENTATION.

Is this all just low-effort poorf** bullshit that doesn't actually work?

[–] PlexSheep@feddit.de 0 points 8 months ago

I mean it can be bad but not that bad, do you typically host stuff in windows with docker? Because I'm pretty sure few projects officially support that.

[–] Heavybell@lemmy.world 0 points 8 months ago (1 children)

I dunno what you guys are doing that makes your nextcloud die without touching it. Mine runs happily until I decide to update it, and that usually goes fine, too. I don't use docker for it, tho.

[–] MaxHardwood@lemmy.ca 1 points 8 months ago

I dunno what you guys are doing that makes your nextcloud die without touching it

Mine runs happily until I decide to update it

[–] excitingburp@lemmy.world 0 points 8 months ago (1 children)

This has been a serious concern of mine. In the event that I prematurely die I have everything set up with automatic updates, so that hopefully my family can continue to use the self-hosted services without me.

Nextcloud will not stop shitting the bed. I'd give it a few months at most if I died, at which point my family would likely turn back to Google Drive.

I'm looking for a more reliable alternative, even if it's not as feature-rich.

[–] colebrodine@midwest.social 1 points 8 months ago

I've told my wife and family that if something happens to me, they need to start migrating all their stuff off my self-hosted services to cloud services because its a matter of time before something fails and nobody's around who knows or cares to fix it.

[–] Pechente@feddit.de 0 points 8 months ago

It used to be like that for me, so I switched my Nextcloud hosting to Hetzner.

I know this community is for selfhosting stuff but in this case was a good choice to let others deal with it.

[–] buedi@feddit.de 0 points 8 months ago* (last edited 8 months ago)

I see a lot of Nextcloud here, but I can not share the same experience anymore. I ran it for years on a shared webhosting instance (Hetzner Shared Level 4) which surprised me that with the limited resources it has here, Nextcloud was still working flawless. Unless I ran an update. In 8 out of 10 attempts it caused issues and it being a shared webhosting infrastructure, I had limited ways to intervene when something went wrong. As I said, that Level 4 has very limited resources in any way you can think of, so I never blamed Nextcloud for it.

Since a year or so I self-host at home and run Nextcloud in Docker compose (Nextcloud Community Image (not AiO, not LSIO), Mariadb, Coturn) and never had issues. It obviously runs much faster than on the shared webhosting instance and I never had issues updating. It´s just a matter of docker compose up -d after Watchtower tells me that there is a new version and I´m done. We would not know what to do without NC here at home. We use it extensivele for Contacts, Calendar, Talk and Files from inside and outside our network with various devices (Windows, Android, iOS) and various Applications (Nextcloud, Talk, Notes, DavX, Webclient) for many many years and we are very happy with it.