view the rest of the comments
Selfhosted
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
@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
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?
@beppi
https://github.com/nextcloud/all-in-one#how-to-properly-reset-the-instance
After that, fresh install, no encrypt, everything ok.
Might have to try squeezing out a backup and giving it a go
@beppi
Ehi, just to feed my curiosity, has it worked?
Was meant to get back to you, sorry
Didnt work for me unfortunately.. maybe some setting in the backup was carried over and thats the problem. But i think the actual problem is hardware/setup based rather than config/software. Might invest in a less shit computer soon haha
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: !selfhosted@lemmy.world