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:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Works great for me. I had it running in a snap for awhile, but now I just have it in a proxmox Debian container running a LAMP stack. I have over a terabyte of stuff saved and multiple computers syncing too, so its well used.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| CA | (SSL) Certificate Authority |
| DNS | Domain Name Service/System |
| Git | Popular version control system, primarily for code |
| HTTP | Hypertext Transfer Protocol, the Web |
| LAMP | Linux-Apache-MySQL-PHP stack for webhosting |
| LXC | Linux Containers |
| PiHole | Network-wide ad-blocker (DNS sinkhole) |
| RPi | Raspberry Pi brand of SBC |
| SBC | Single-Board Computer |
| SSH | Secure Shell for remote terminal access |
| SSL | Secure Sockets Layer, for transparent encryption |
| nginx | Popular HTTP server |
10 acronyms in this thread; the most compressed thread commented on today has 10 acronyms.
[Thread #392 for this sub, first seen 1st Jan 2024, 02:35] [FAQ] [Full list] [Contact] [Source code]
I can’t remember the last time I laughed this much
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.
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
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.
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.
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
Nextcloud ist just fine. Using it since more than 7 years now with zero problems
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.
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.
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...
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.
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.
Paperless often randomly stops accepting new documents. I have to wait several hours or restart it.
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.
The most-recent release of lemmy dicked up outbound federation pretty badly on the instance I use.
To be honest, no. I run in a Truenas Jail, and its stable for me. Just a bit slow for big files sometimes.
Currently dealing with this nonsense,
and this accompanying nonsense:
I wish there were an alternative in a sane programming language that I could actually contribute to. For some reason PHP is extremely sparse in its logging and errors mostly only pop up on the frontend. Having to debug errors after an update and following some guide to edit a file in the live env that sets a debugging variable, puts the system in maintenance mode and stores additional state in the DB is scary.
Plus PHP is so friggin slow. Nextcloud takes noticeable time to load nearly anything. Even instances hosted by pros that only host nextcloud are just slow.
You could check out Frappe Drive (and Frappe, the framework it's built on, it's pretty awesome). They aren't accepting contributions at the moment but I'm sure that'll change once it's out of beta like with the other frappe apps. There's also Raven messenger also built on Frappe and you can use the two together (but without any real integration between the two yet, but that's on the roadmap on the Raven side).
I've spent a lot of time researching alternatives and NextCloud is the only one that does everything it does in one place. I've dug into the code a lot to find places to make it work faster and came out confused and mostly empty. It's also federated, and I think it's the only FOSS file sharing platform that is. It''s a very mature application so you'll be hard pressed to find features that are missing, but also to find things that could be further optimized without ripping out major chunks of the application which are likely interconnected with other major chunks of the application. For my personal use NextCloud instance I've resorted to just completely deleting the database and installing everything fresh between major versions, then just rescanning my local folder.
Invidious. It's to be expected for something like that though.
The very same reason why I gave up on Nextcloud. Too many nasty surprises.
The snap version of nextcloud has been pretty solid for me, except for the time that I installed the nextcloud backup app.