18
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 14 Aug 2023
18 points (87.5% liked)
Self Hosted - Self-hosting your services.
11587 readers
19 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
- No harassment
- crossposts from c/Open Source & c/docker & related may be allowed, depending on context
- Video Promoting is allowed if is within the topic.
- No spamming.
- Stay friendly.
- Follow the lemmy.ml instance rules.
- Tag your post. (Read under)
Important
Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!
- Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate.
Cross-posting
- !everything_git@lemmy.ml is allowed!
- !docker@lemmy.ml is allowed!
- !portainer@lemmy.ml is allowed!
- !fediverse@lemmy.ml is allowed if topic has to do with selfhosting.
- !selfhosted@lemmy.ml is allowed!
If you see a rule-breaker please DM the mods!
founded 3 years ago
MODERATORS
I can't troubleshoot your exact issue, as you seem to not see what is happening in the background and are relying solely on error pages. We need to get to the container logs.
Did you remove the old containers and volumes?
Clean up unused containers, networks, images, and volumes
DANGER ZONE LOSS OF DATA IF YOU DONT HAVE BACKUPS
That will give you a clean environment to start over with your compose files.
If youre still having issues, inspect the live container logs to find the errors.
Then post the errors.