Closed BananaAcid closed 1 day ago
[!NOTE] I moved this to the letsencrypt repo
Mind running the following and showing the output of each command?
cat /var/spool/cron/crontabs/dokku
cat /var/log/dokku/letsencrypt.log
$ cat /var/spool/cron/crontabs/dokku
cat: /var/spool/cron/crontabs/dokku: Permission denied
$ sudo cat /var/spool/cron/crontabs/dokku
[sudo] password for admin:
cat: /var/spool/cron/crontabs/dokku: No such file or directory
$ cat /var/log/dokku/letsencrypt.log
cat: /var/log/dokku/letsencrypt.log: No such file or directory
Have you deployed any app since the upgrade?
i believe not. But updated existing apps
just updated dokku version to 0.35.5 ... does that help? Same result with the 2 commands above.
... now after updateing, no domain shows the correct app ... but using letsencrypt:enable seems to fix a single app ... hope I can find a command to redo all apps ... did not expect this to get so messy after updating dokku
Oh looks like your report output says auto renew isn't enabled. Maybe just enable that - the command is in the readme.
oh then must have gotten disabled by the update, thanks for finding it.
just as an addition to fixing all domain <-> app mismatches after last update to dokku 0.35.5:
skip_first=true
dokku apps | while IFS= read -r line; do
if [ "$skip_first" = true ]; then
skip_first=false
continue
fi
dokku letsencrypt:enable "$line"
done
except 1 .. all point to the correct domain... the one using a docker container (instead of the the others using a node bildpack) uses the domains of an random app from the list ...
any idea to about how to fix this?
Not sure what you mean "all point to the correct domain". Do you mean one domain isnt serving the correct app? Mind checking to see if the app containers are actually running?
Any specific command to check it easily, or should I use the docker container commands usally?
Since domains are configured for each app, each domain should show the content of its app. thats what I mean app pointing to the correct domain. Yeah, technically totally wrong.
The container buildpack one does not show up in sudo docker container ls
anymore
How do I get it to work with dokku again?
You can usually check if the app is running as expected via dokku ps:report $APP
.
If it's not running, you can dokku ps:rebuild $APP
to get it going again.
thanks. Rebooting the server worked as well.
Description of problem
Upgraded to dokku version 0.34.6, 3 month ago, no configured apps have renewed certificates.
Manually triggering
dokku letsencrypt:renew <app>
works just fine.Steps to reproduce
Upgrading to dokku version 0.34.6.
Is there some separate service or somthing I can check if it runs or alike?
dokku report $APP_NAME