this post was submitted on 21 Feb 2025
-46 points (16.2% liked)

Selfhosted

60587 readers
1260 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. 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.

  8. 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:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Added the only actions I did in the comments.

you are viewing a single comment's thread
view the rest of the comments
[–] JustEnoughDucks@feddit.nl 4 points 1 year ago (1 children)

Hey, I had a similar thing happen to me. It turns out the faulty container brought down my entire LAN network. The reason you can't ssh in is likely because your router is stuck at 100% usage trying to figure it out.

At least that is what happened with my old Archer A7 and damn nextcloud.

[–] ComradeMiao@lemmy.ml 0 points 1 year ago (1 children)

Did you try removing the container? What did you do to fix it? I think you’re probably right. I ended up just moving my data, sense I could use the terminal and send files out, and reinstall fedora server.

Thanks for sharing! :)

[–] JustEnoughDucks@feddit.nl 3 points 1 year ago (1 children)

I had to physically log into the server (I am not using a VPS) and docker compose -f ... down the container in order for it to be solved. After a downgrade of nextcloud it was solved and the next upgrade I did, didn't experience the same issue. I ended up ditching nextcloud anyway because after an update ~8-12 months ago, the login page has never loaded since, so it can't be used. I found out I rarely used it anyway.

[–] ComradeMiao@lemmy.ml 1 points 1 year ago (1 children)

Did you switch to Seafile or something similar?

Thanks for sharing! I had to try something similar but it didn’t work sadly.

[–] JustEnoughDucks@feddit.nl 1 points 1 year ago

Nope, syncthing for file syncing things between systems like music and I realized I never really used "cloud" storage.