-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Issues getting letsencrypt section up and running. #4144
Comments
Okay, update My compose file now looks like this:
my .env now looks like:
and my containers all show as up and running now: But there's nothing I can enter to see a webui still. Any guesses? |
There are some odds in your docker-compose file.
Why using a different port number for mysql? |
Alright lots of changes made here, decided to give up on letsencrypt. I was trying to use a duckdns address, then tried an address I had on namecheap. Neither of them wanted to pass a DNS test from letsencrypt. Honestly just want to see Monica with my own eyes at this point. Here's my compose file:
Here's my new .env (thank you for pointers on db host btw):
I am getting all green boxes now, going to monica.b.box gets me nothing, going to b.box gets me a 503 Service Temporarily Unavailable |
I hope you managed how to run this image now |
This issue has been automatically locked since there |
Describe the bug
Trying to get Monica with letsencrypt up and running via docker compose, monica_proxy_1 and monica_letsencrypt-companion are failing.
Screenshots
Which version are you using:
I am doing this on Docker for Windows, as you can see in the screenshot I am attempting to use a different port for my webui as the default is already taken.
I have tried various settings for the port mapping, for both mysql and the webui.
No matter my settings I run into an error saying:
Here's my docker compose:
and my .env:
This is my current and closest iteration, I know the fact that it's a windows attempt complicates things with paths, but I am hoping someone can offer some advice.
Thank you.
The text was updated successfully, but these errors were encountered: