this post was submitted on 21 Feb 2025
-40 points (15.5% liked)

Selfhosted

42719 readers
578 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
 

Added the only actions I did in the comments.

top 33 comments
sorted by: hot top controversial new old
[–] TheFANUM@lemmy.world 7 points 18 hours ago

Don't bother asking for help without including the EXACT command you ran and the EXACT error you received.

[–] JustAnotherKay@lemmy.world 5 points 23 hours ago (1 children)

What port do you have SSH set to? What ports did you change the services to? Is the SSH port open?

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

SSH is standard port 22. The services were 3000, 5000, 8888, and something abnormal I think 5675. 3000 and 8888 were taken. First time it said 8888 was taken so I edited to 8188. Second time it said 3000 was taken so I edited to 3001. Then I lost SSH.

[–] JustAnotherKay@lemmy.world 2 points 9 hours ago

Have you hit it with anything to check if your ports are still open? There are a handful of tools for the task

[–] HybridSarcasm@lemmy.world 9 points 1 day ago

We don’t have any rules about low quality posts. So, I dont’t have cause to remove this. Though, I also won’t lock it because I want everyone to downvote it into oblivion.

OP: you can save this post by actually adding details in an edit.

[–] fuguOne@lemmy.ml 13 points 1 day ago

Based on the data that you provided, I think you need to check the flux capacitor.

[–] JustEnoughDucks@feddit.nl 3 points 1 day 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 1 points 9 hours 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 1 points 9 minutes ago

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.

[–] Coldmoon@sh.itjust.works 14 points 1 day ago (1 children)

Could you give us even the slightest bit of detail? What containers? Did you try pinging the device?

[–] crusa187@lemmy.ml 9 points 1 day ago

You say you changed port configs in the yml, but then refuse to share said yml when people ask to see configs.

If this is some sort of trolling attempt, going to have to rate it 0/8.

Let this be a lesson to you - don’t modify port settings unless you’ve triple checked the documentation. It’s easy to mix them up with docker. And don’t ever use a known port value for a service like ssh, that’s just asking for trouble. Docker provides other ways to access the virtualized cli.

[–] JASN_DE@feddit.org 12 points 1 day ago (2 children)
[–] just_another_person@lemmy.world 10 points 1 day ago* (last edited 1 day ago) (1 children)

Details please.

I'm assuming you forced a port conflict somehow.

[–] ComradeMiao@lemmy.ml -5 points 1 day ago (1 children)

I tried to run hanabira via cli. There were port conflicts but I changed them in the yml.

[–] just_another_person@lemmy.world 5 points 1 day ago (1 children)

I don't think you changed them in the right way, or didn't restart. Post configs.

[–] ComradeMiao@lemmy.ml -5 points 1 day ago (1 children)

So I already removed those two containers. What can I share with you?

[–] just_another_person@lemmy.world 4 points 1 day ago (1 children)

Like everyone else is saying. POST CONFIGS.

[–] miss_demeanour@lemmy.dbzer0.com 9 points 1 day ago (1 children)

Did you unplug it and plug it back in?

[–] ComradeMiao@lemmy.ml -3 points 1 day ago