Skip to content
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

How to get version 1.6 of certbot? Snap lists 1.32 as latest. #82

Closed
acesuares opened this issue Dec 12, 2022 · 7 comments
Closed

How to get version 1.6 of certbot? Snap lists 1.32 as latest. #82

acesuares opened this issue Dec 12, 2022 · 7 comments
Assignees
Labels

Comments

@acesuares
Copy link

How to get version 1.6 of certbot? Snap lists 1.32 as latest.

@VojtechMyslivec
Copy link
Owner

Hello,

certbot version 1.6 is the minimum version needed for letsencrypt-zimbra to work. I hope it is clearly noted in the README.

I am not aware of any breaking changes in the certbot, so 1.32 should work well.

V.

@acesuares
Copy link
Author

acesuares commented Dec 15, 2022

You're totally right. I misread 1.32 as 1.3.2 but the resaon is, that I am getting this error:

letsencrypt-zimbra.sh: error: The certificate cannot be obtained with '/usr/bin/certbot' tool.

@VojtechMyslivec
Copy link
Owner

I see.

You can use -v option to enable verbose output of letsencrypt-zimbra. However, if your certbot version is 1.3.2, the problem is in old non-supported version of certbot.

I don't use snap so I am not sure why it does not list any newer version. What OS and what version do you use? Have you searched your OS packages (apt/rpm) or tried to install it via pip?

@acesuares
Copy link
Author

It's my fault, probably. The version is 1.32 and that is higher than 1.6, so that's not the problem. I think i installed a firewall that blocked port 80 and thus made it impossible to get the certificate.

@acesuares
Copy link
Author

Oh BTW this has worked for years without flaws, thank you very much for writing this script!

@acesuares
Copy link
Author

Yep, the blocked port 80 was the problem.

@VojtechMyslivec
Copy link
Owner

Oh BTW this has worked for years without flaws, thank you very much for writing this script!

nice to hear that 👍 😊

Yep, the blocked port 80 was the problem.

Perfect! I will close the issue then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants