Selfhosted

I'm not done but I'm so tired of just stupid error messages that don't help from developers. I love the open source community but for gods sake devs, handle your errors in a format that makes sense.

Nextcloud or others, it's always the same. I either get a 200 line stacktrace that means absolutely nothing to me because the dev didn't bother to handle the exception (like you submit a form and get a null reference back. It sure would be nice to know what field was null) or of course the infamous "Exception occurred" and nothing else.

My favorite was I tried to submit to Jellyfin a fix for one of their very opaque exceptions, keep the stack trace but rewrite the error message like "x exception occurred, do you have permissions to do that?" Or something and the PR was rejected. I just can't even with that

I almost don’t dare to say this, but I’ve been running the snap for more than a year and have no complaints.

Most likely you got blocked for some time by the brute force prevention. Have a look at your logfiles.

My problem with nextcloud is more the performance of the web interface rather than it's reliability (and that's even with mariadb + redis setup and a decently fast minipc). It's fine if you avoid the web interface, but that's part of the draw of the thing.

What name do you assign the DB for PostgreSQL in Docker and does it by chance happen to match the name of any other containers, possibly in other docker compose files?

I'm only mentioning it because I experienced weird inconsistent issues with a service I was running where it was sometimes having trouble connecting to its DB companion and I eventually realized that it was sometimes connecting to the other container. I was also finding that turning it off and on again was often 'fixing' the issue, at least for a while. Might be worth checking out. I'd also consider viewing the logs for Nextcloud (docker logs -f ) when you're unable to login and see if there are any errors. Frankly I've never had these specific issues with Nextcloud, and given that it's based on PHP (it only 'executes' on an HTTP request), it seems like restarting shouldn't help unless it's something else.

I haven't got this kind of issue with nextcloud, I'm pretty sure you can reset your password using occ via cli

I am using nextcloud for years now with postgres, redis and configured PHP setttings, but I installed it on the host. Never had any problems, Performance is awesome... Almost everytime I read about problems is with the docker images. The new AIO image shall be bad too, but I can not say anything to this, since I don't use it.

I really like docker, but sometimes it is better to install on the host directly or use an LXC if you need isolation. MinIO is the same... Would not want it in a Container

Maybe seafile could be an option for you 🤔

For photos, I'd highly recommend checking out Photoprism.

the "PhotoSync" app available for both android and apple can sync from your phone to photoprism.

But, nextcloud itself, works pretty nice for me. But, I use OIDC-based logon, with Authentik.

In my experience, Immich is way better for Photos.

Maybe try https://github.com/kd2org/karadav if you want to continue using the NC apps for photo backups.

Would be interesting to hear a little more about your setup. I had some issues when I had Nextcloud installed directly on Debian (though nothing this major), have since switched to running it on Docker and it's been very solid.

Maybe Immich might be a fit fit

https://github.com/immich-app/immich

So, now's as good a time as any to ask. Why is everyone using Nextcloud? I've been quietly using Owncloud for a very long time and never had any issues with it. How is Owncloud bad?

Nextcloud is an overkill. Its just too much. I'd say better split down the needed services. Baikal/radicale etc for contacts/calendar. Photoprism/librephotos etc for photos. A webdav server for storage. And so on.

I’ve been running two NC instances for over five years (linuxserver docker images)—one has been issue-free, and the other had sporadic issues like OP is describing... but not for the last year or so, so I assumed the issue had been fixed in an update. Or maybe the problem was the network configuration instead of NC.

use immich for photos.

owncloud ocis works but is very young. is literally just file hosting with something to open office files online.

Thats frustrating

I second the notion that your ip was banned by nc's brute force detection

The silent reconnects of a DAVx client on a phone could easily trigger this

You can whitelist your home routers ip in the config IIRC Maybe not on the LISO container though, IIRC it is less configurable, but doesn't "just work", I'd ditch that not nextcloud

Quick fix could be to "DELETE FROM" (or "TRUNCATE" if you are certain nobody is blocked correctly) the table bruteforce_attempts (or smth similar). Although that "dc up && dc down" worked could indicate another issue, as you do seem to have persistence with your db in a docker volume (cred are still there) which would mean the time penalty ran out during restart or oits somethimg else