-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error reaching selfhosted instance - Bad Docker image or a configuration issue? #799
Comments
Honestly, I have a very hard time dealing with docker. I need somebody from the community to help with this. But give me a day or two and hopefully I can figure this out :/ |
I can relate to the struggle you're facing with Docker. It's not always easy to get everything working smoothly. If you're still stuck after taking some time, don't hesitate to reach out. |
Hey @jelveh ! Any news? :) |
I need @KernelDeimos to help with this. I'm bad at Docker |
@jelveh Thanks for your answer. Then I hope this problem will be solved soon. A few issues have already been opened about this. @KernelDeimos |
@dennysubke does the official docker-compose file work? This looks like an issue with domain configuration. Take a look at these: |
As some people have already pointed out, there is something wrong with the Docker image. Attached is my docker-compose.yml:
The config.json file looks like this:
After installing everything is fine according to my logs. Here's an excerpt:
The app URL should be http://umbrel.local:4100
After running I get the login screen with the following error message:
The image used here is this: sha-ec31007
Since the image was already more than 6 months old, I also tried a newer one (2.4.1). Then I got the following error message:
The logs attached:
umbrel_denny-puter_2024-10-11_19-21.log
I've really tried everything and I'm at the end of my knowledge. Can someone from the developers take a look at this?
Apparently there is actually something wrong with the Docker image.
@KernelDeimos @jelveh
Thank you!
The text was updated successfully, but these errors were encountered: