-
Notifications
You must be signed in to change notification settings - Fork 63
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
Implementing an auto SSL feature #43
Comments
Hi Adam, thank you for your interest. I'm an Angie developer, and I can tell you that we're working on this feature right now. No specific dates yet though :) Cheers |
Amazing! Looking forward to this feature! |
Hi. Any updates? |
Hi. Work is underway, but I still can't promise this feature will be released any time soon (probably not until new year :)) The ACME protocol implementation is basically up and running, but there's more to be done. If you're interested, I can share some details :) This may all still change, but at the moment we've added several new directives to the config syntax. The most important one is At startup, the client checks the expiration dates of its certificates, and launches a renewal procedure, if necessary, or schedules renewal for an appropriate time. I wouldn't like to go deeper and tell you what's going on under the hood, particularly as we haven't solved a couple of design problems yet :) But I will appreciate any suggestions, wishes, ideas, etc. Can't promise to fulfil them all, but they will all be carefully reviewed and taken into account. Cheers |
Yes, take your time to think this through and to sufficiently test the implementation. Once this lands it'll solve a decade old shortcoming (imo) of Nginx. |
@a-sor |
Hi @adammakowskidev , I was just going to write a little update on this. We will be releasing Angie 1.5.0 soon, and we plan to include this ACME feature in it. It will come with some limitations though (e.g. only http-01 challenge, no wildcard domains, etc). We are going to further develop ACME support and overcome some of these limitations in future versions. We have changed the syntax of the new directives, now they are
I hope this gives you an idea :) Cheers |
Forgot to say that by default the client tries to acquire a certificate from Let's Encrypt. The ACME server's URL can be specified in the |
Initial support for Automatic Certificate Management Environment (ACME) released with Angie 1.5.0. |
Amazing! Today I will start testing. |
I'll second that, nice work guys! 👏 |
Ok so I tried it now, it looks like the certificates were generated because there are 3 files in the /var/lib/angie/acme/domain folder But the site does not support connection via https My config, maybe I'm doing something wrong?
|
Please check error log. Also, make sure that Note, that system-resolved usually listens on |
Hi
|
@adammakowskidev it's planned for Q2-Q3 this year. |
Hi!
First of all I would like to thank you for creating Angie, it's a very good project, much friendlier and easier to use than nginx.
I've been testing it for some time and it works flawlessly.
My question is whether it is possible to implement auto SSL, such as it works in Caddy?
https://caddyserver.com/docs/automatic-https
This would be a real game changer in the NGINX environment and a big plus for Angie.
Do you have any plans for such a feature?
Greetings
PS - Sorry if this is not the right place to report such ideas
The text was updated successfully, but these errors were encountered: