this post was submitted on 09 Jul 2023
13 points (88.2% liked)

Selfhosted

40394 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 2 years ago
MODERATORS
 

Hey guys,

I posted this and a bunch of info in the Nextcloud help forum https://help.nextcloud.com/t/nextcloud-aio-freezes-have-to-manually-stop-all-containers-to-get-it-responsive/165826/1

But i thought id plug it here too in case anyone has a solution... Tried all kinds of things but cant prevent nextcloud from timing out

Thanks guys!

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 1 year ago (2 children)

@beppi

I had the same issue last week (was my first installation)

I managed reinstalling it after a purge, and now it works good. The only difference is now i did not activate server side crypt module. I'm running NcAIO on Debian 11.

@selfhosted

[–] beppi 2 points 1 year ago (1 children)

I decided not to use server side encryption, as its just running on a comp at home. But maybe a fresh reinstall would work. Did you do anything special when purging?

[–] [email protected] 0 points 1 year ago

Hi there! Looks like you linked to a Lemmy community using an URL instead of its name, which doesn't work well for people on different instances. Try fixing it like this: [email protected]