-
-
Notifications
You must be signed in to change notification settings - Fork 92
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
LetsEncrypt inside Docker; 502
error.
#274
Comments
I fixed it by using older version 0.17.0 |
|
@satalsky that isnt older than what he is using. Are you sure you're describing this issue and not something else? |
Hello! I am having same issue. I tried to debug it, here is log with trace enabled. I tried to debug it, it seems like proxy is working just alright, but nothing listens from another side. It is possibly because dokku is ran inside docker, not on the host machine. EDIT: Oh, it seems that this time it failed due to validation limit. Previous failure was because of 502 engine proxy failure as in first report:
|
@c4lliope did you ever solve this? |
I am currently experiencing the same issue, any solutions? |
same issue, not inside a docker. |
I'll try and revisit the Pr for docker support this week. |
Description of problem
A
502
error upondokku letsencrypt:enable #{app}
,meaning the ACME process ends up issuing a
403
error.Logs included herein.
Reproduce
on a Fedora CoreOS machine, on an
arm64
processor./var/lib/dokku/plugin-list
to repair Unable to create directory for account (dokku in docker) #235:letsencrypt: https://base.assembled.app/code/dokku-letsencrypt.git # or letsencrypt: https://github.com/c4lliope/dokku-letsencrypt.git
~/.ssh/config
to use port 3022.letsencrypt
.Actual Results
Expected Results
SSL should be enabled on application's domains.
Environment Information
dokku report APP_NAME
dokku ps:inspect $APP
The text was updated successfully, but these errors were encountered: