Just had NextCloud denying my credentials (not for the first time). I know they weren't wrong because I'm using a password manager. Logs didn't say much. Was about to reinstall (again, not the first time nextcloud went bonkers on me) before I tried a docker compose down && docker compose up. Lo and behold after a restart the credentials worked again.
This stuff is just way too flaky for something so important.
Is OwnCloud good again? My main usecase is saving photos but I don't want them locked away in a database so SeaFile is out.
Edit: I'm going to take the time to reply to you all, bit busy with work and family suddenly. But a little update - I've quickly setup Immich and fired up the CLI to import my library. AFAIK the files are still stored on disk somewhere but metadata is in a database. I didn't realize this before, knowing that I think my mind is made up and Immich is the best solution. Thanks everyone!
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
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 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
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.
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.
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?
Mine has randomly done that for the last few versions now. I also noticed it now maintains several cookies that I have to clear before I can log in successfully again.
I do have Redis configured with it, have never used their AIO image, and previously, the session ID was the only cookie. Haven't kept quite up to date with NC's development, but maybe it's no longer using PHP's session store in favor of its own mechanism?
Unfortunately, I'm too invested in NC to start switching everything to discrete apps, so I guess I just have to put up with it. :shrug:
I also stopped using Nextcloud after it broke a couple of times. As a consequence I also never use :latest tag on any docker container anymore - manual updates only
When I switched to Android phone, I also switched to syncthing. If you have enough storage on your phone, it is amazing! Never looked back
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
I would like to recommend Seafile if immich doesn't work out. I've used it for a long time and it's always been the best self hosted cloud imo. it's not as shiny or pretty looking as some but it's been reliable