I’m new to selfhosting, I’ve installed Turnkey nextcloud on my proxmox server, and done the basic setup, now I’m faced with this.
Any advice?
Turnkey images are usually built on popsicle sticks and chewing gum; they use old packages, their configs are often really janky and they do not like being updated.
I’m not kidding you, you’d be better off building nextcloud in a generic debian container.
As for the errors, as others have mentioned these are more or less easily fixed one at a time.
Tear down nextcloud and use discrete services instead of a shitty monolith
I need to sync pictures from iPhone to server. What should I use?
Immich and photoprism are the two big players, immich is the better of the two IMO. At least for android. I assume it works the same on iPhone.
Some of them can be fixed, though you don’t necessarily need to do all of them. Easiest thing is ignoring them as long as everything works.
I do not know any Turnkey, so perhaps they have some specific documentation about what to do after installing.
The first time I installed Nextcloud, I did it on bare metal in Debian, following the LearnLinuxTV guide. It went through things like how to configure the Opcache, which is one of the warnings you have. If you’re not following a guide, you’ll have to find one, or search each message individually and research a solution.
Eventually I decided to reinstall with NextcloudPi because they know a lot more about systems administration than me, and had sane defaults set for most things. My first installation had some bugs that were probably from default configurations or mistakes I made perhaps. But I’ve had a good experience with ncp.
One last thing you’ll learn while researching the messages: some may be from bugs in the software that will be solved over time with nextcloud updates. Some will have clear solutions. Some may be generalized messages arising from network instability (like if Nextcloud is trying to sync over a weak Wi-Fi signal sometimes) or a hardware problem that can be tricky to track down, but might not be important. Just make sure you are doing good backups and you’ll be fine.
Thank you, this is a solid answer.
I was hoping to find some kind of guide or at least reassurance that I’m going down the right path. It looks like it
As others have said. The errors are easily fixed and documented if annoying. Some will require console access but are usually pretty safe.
One at a time?
I came to say this. And not flippantly. Each one of these takes a dive into the documentation to resolve. Sometimes they are related and you can solve some issues with one change, but each one is a challenge to be solved.
OP, focus on Security first, Errors second, and warnings third. Often the warnings are not a huge deal to having an operational nextcloud, but might impact performance or excessive logging for example.
Yep, exactly this.
This is the way
You could read the documentation that each link points to, you might need to have console or SSH access to the server
People here will hate me for this but I type each error into Copilot and ask it how to fix it.
Most fixes are very straightforward and don’t require much changing around of things.
i mean, what’s any different from putting it in quotes and searching on google? other than the possibility that it’ll tell you to eat rocks or something…
It can take less time when using an LLM for simple procedural things like fixing a single well-documented Nextcloud config error.
It also takes less cognitive load to get to the answer. I’m not suggesting one fully uses LLMs instead of search engines, but for this specific issue that OP has, I’ve found that LLM takes me less time and concentration than searching it and manually parsing through threads and forums.
please don’t interpret my sardonic reply as criticism. look on the bright side - your query probably consumed enough energy to power a small home for a while :P
I get that you don’t like the technology and that is fine. It’s overused in applications it shouldn’t and its useful applications are overshadowed by marketing hype.
That said, if you use more efficient models (like deepseek), you will use significantly less energy per query.
Respectfully, I won’t engage any further. I expected this sort of objection but it doesn’t contribute to OPs original question anymore.
i didn’t downvote you, and i hope people here know that the vote buttons aren’t like buttons here.
i’m only fucking around. playing with ideas. doing what i think people should do in discussion fora.
but trying to play the high ground for using microsoft’s “ai” scam is a new thing to me. all good, though, i hope your prius kisses you back :P
Your link is malformatted btw 😉
Are you going to use Nextcloud Talk? Disable it if not, and see how much of the repeating errors clear up.
I fixed the link.
I disabled talk for now, I still get the same amount of warnings.
Then just go through error, select the first part of that error, and search it up. It should lead you to fixes.
Seems like you just need to run some updates to fix a few of them.
