-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
All apps missing from "list" #224
Comments
Just to note that this was one of several issues I had trying to do a simple upgrade from 0.9.4. I assumed it was some left over state from a previous version, but couldn't figure out what it was. Given it was a 3 day old release of letsencrypt and running on a live server, I ended up reverting to 0.9.4. |
Does re-adding the cron make it "work" again? Seems like the switch to letsgo broke this because the filepaths changed, but I think this is fixable by adding support for the old and new style. |
re-adding the cron via |
I just wanted to chime in that I was having the same issue and had to re-enable both apps using the letsencrypt command |
A potential fix was released as part of 0.11.4. I'll leave this ticket open for a week in case someone can confirm/deny the latest version fixes the problem for them. |
I experienced the same problem. My monitoring once again reported, that the certificates are going to expire, but now I can't even renew manually, because After installing 0.11.4 I could see them all again. Thank you! :) |
JFI: Because I think that it also has to do with the same changes:
|
Hopefully I've fixed that in the latest release @arusa. Try 0.11.5 now. |
I've faced with the same issue. I have anew enabled my apps and just a moment before upgraded to UPD 0.11.6: when I'm trying to enable |
Still an issue in I was able to downgrade by using the following command:
|
It worked in 0.11.5 again, but after upgrading to 0.11.6 the |
Thanks @benwinding
|
Ah feck I realize what I did wrong here, let me fix it and will release it in 0.11.7. |
This is what I get for not having comprehensive integration tests for this plugin... I really should roll this into the core and have it tested there... |
Alright we're in business, @arusa mind checking if 0.11.7 does the trick? I think it should fix it for both old and new setups. |
Pinning the update to 0.11.5 maybe wasn't the best idea. I can't find out how to unpin it. I updated (and pinned) it to 0.11.7 now and the
|
How are you triggering a renewal? Seems like one side is responding with |
I'll be offline for a few hours, but if you can hop on to our slack channel during the afternoon/evening EST, that would be great. |
All good, thanks for the updates @josegonzalez and I appreciate your work and quick reaction time! Cheers, |
First I tried it with Where can I find the slack channel? I am in CEST (UTC+2), but maybe we can find the right time ;-)
|
Link here: https://glider-slackin.herokuapp.com |
I just installed 0.11.7 (for the first time, not an upgrade), successfully enabled it on an app (HTTPS works), but the app isn't listed under
|
Okay, the |
@michaelyork mind verifying 0.11.8 fixes the reboot issue as well? |
Looking good! Thanks so much for the quick fix @josegonzalez. |
0.11.8 seems to fix the app listing for me, too. Thanks. |
Unfortunately I still can't renew or create letsencrypt certificates :-( I still get this error:
As you can see above #224 (comment) |
I'm on 0.11.8v, it isn't working for me! I can see the :list but when I do auto-renew it says Can you please advise? |
@rome2o can you enable it for the app first? |
@josegonzalez I've it already enabled, so the reason I got this issue is that certificate expired, the app stopped receiving webhook and client complained. So I went to renew certificate manually through enabling it again. I've setup a staging server to reproduce the issue and yes the issue remain intact. No matter how many times we enable it, it somehow says it's not enabled when we run auto-renew command. Here's the report for the app
|
Mind upgrading dokku to the latest? That's still a few patch versions behind. Additionally, seems like I may have fixed something here for in dokku-letsencrypt 0.11.9. Mind upgrading the plugin to latest? |
It looks like it has fixed this, is there any way to know if a certificate renewal has failed? Just in case. For anyone digging deeper into this, I've updated the dokku to
The issue seems to be resolved! We just have to see it for it to renew as required. I wish there was a way to notify that the certificate is expired! Maybe should look into an alternative link watcher thing that can do the job? Thanks @josegonzalez |
I had dokku 0.26.8 and dokku-letsencrypt 0.12.1 and still had the issue. I was able to fix it by doing |
Description of problem
I'm not sure if this is somehow related to the fix for #215, but all of my let's encrypt apps appear to be missing from
dokku letsencrypt:list
How reproducible
not sure
Steps to Reproduce
I was going through the steps to test the fix for #215 (mostly verifying
dokku letsencrypt:cron-job --add
would execute). After that was successful, I randokku letsencrypt:list
and saw one should auto-renew via cron in a few days.Actual Results
Today when I came to check, none of my apps were listed in letsencrypt and the certificate for the app that would have been scheduled for renew had not been updated.
Expected Results
All of my previously enabled apps would still be in the list.
Environment Information
How (deb/make/rpm) and where (AWS, VirtualBox, physical, etc.) was Dokku installed?:
installed via apt on Azure VM
Additional information
Everything has been working fine for some time. I do try to keep my version of dokku up to date, so it could have been an update with that or some 3rd cause unrelated to the 11.0/1/2 release of this plugin.
The text was updated successfully, but these errors were encountered: