this post was submitted on 02 Aug 2023
132 points (91.2% liked)

Selfhosted

49365 readers
484 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
132
submitted 2 years ago* (last edited 2 years ago) by midas@ymmel.nl to c/selfhosted@lemmy.world
 

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!

(page 2) 38 comments
sorted by: hot top controversial new old
[–] TCB13@lemmy.world 2 points 2 years ago* (last edited 2 years ago)

Well, I'm amazed you didn't get downvoted to hell by saying NC is bad. Some of my experiences with NC are described in detail at https://lemmy.world/comment/1571886 and https://lemmy.world/comment/346174

[–] archy@lemmy.world 2 points 2 years ago

Do you have 2 redis containers by any chance? I'm asking because you mentioned Immich, and that one has redis as part of its stack

[–] fraydabson@sopuli.xyz 2 points 2 years ago

I just implemented authentik SSO for Nextcloud and other apps and it’s made my life easier.

[–] LordKitsuna@lemmy.world 1 points 2 years ago

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

[–] M4rkF@fosstodon.org 0 points 2 years ago (1 children)

@midas Were you self-hossting or using their hosted service?

[–] midas@ymmel.nl 1 points 2 years ago
[–] Secret300@lemmy.world 0 points 2 years ago
[–] notfromhere@lemmy.one -3 points 2 years ago (1 children)

Are you exposing it to the Internet? Weirdness like that might be from someone exploiting your instance.

[–] midas@ymmel.nl 1 points 2 years ago (1 children)

Yeah - don't see any evidence of that in the logs + why would it work again after a restart?

[–] notfromhere@lemmy.one 1 points 2 years ago

How do you have your auth working? Is it basic user/password managed on Nextcloud (external database connected?), is it external auth against something like Okta, or is it user/pass that you define from docker-compose?

If via docker-compose then a restart would clear anything an attacker would have done and it would reload from the docker-compose process I think? I’m not too familiar with the specifics on that as I’m not a security researcher, but generally some attacks are resident in memory only and a restart can clear them only for it to crop up again later either due to a running process that was set to rerun an exploit or someone monitoring your system externally and retrying the exploit remotely again.

Or it could just be some bug in Nextcloud or unique to your environment. Personally I’m only hosting things that are internally accessible via VPN anymore. Tailscale makes that super easy these days.

load more comments
view more: ‹ prev next ›