The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Seems appropriate. Most of the Scrum meeting sounds like Russian to me anyway...
Anything that is unrelated to elephants is irrelephant Anonymous - The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944 - Never argue with a fool. Onlookers may not be able to tell the difference. Mark Twain
I'm getting a new Azure VM ready to host several web apps and am to the point of getting an SSL cert for it. It appears that Let's Encrypt requires renewals more frequently than a 'store bought' ssl but that the renewal can be automated. I might be able to live with that.
Anyhow, to the point...anyone here using let's encrypt? Anyone had issues with it? Usually there is a reason things are free...limitations and such. Thanks for any suggestions/thoughts.
Edit: 4 hours later after receiving some encouraging reviews and I can't get it working! Using a GUI tool called certify, I got a cert installed easily, but no joy on connecting via https...now giving a dns error. (INET_E_RESOURCE_NOT_FOUND) The certs (I now have 3 from trying different configurations to get it to work) appear to be valid on the server. The bindings appear to be correct as well. IIS 10 on Server 2016 if it matters.
I'd hate to find out that my ISP's cable modem is blocking 443...probably not, but I'm running out of reasons why this won't work. wte would dns have to do with it...the sites show up fine with http, but not https.
I use both in Azure and in hosted on-site websites with no problems.
The biggest issue in Azure is getting the renewal automated, which requires that your website has a service level of "always on" to run the renewal web job when necessary.
How did you automate the renewal process? I also have been using LetsEncrypt successfully in both on-prem servers and Azure VMs (dev and test servers). But every 3 months I have to go through the hassle of manually renewing.
I had the same problem at first. You have to select a Azure subscription level that won't shut down the WebJob that does the renewal. If I remember right, when you go to the web job you will probably get a warning about this, and give you the option to update your subscription. Once you do that you should have no more issues with this.
Perusing the source, it's definitely not a hobby project, imo.
This project is work in progress. It works, but probably still has many bugs and needs more testing.
If you are just looking for a Let's Encrypt client or a more mature project, then you should take a look at these projects:
For me looks like hobby project. I am not saying that it not works. Description from the author sends a signal: 'do not use it at home'
Thanks for the link for Self-Hosting. I used another GUI (certify) and everything seemed to go well...the cert shows active with 89 days, the .well-known folder was created, the tests all passed, the certs show up in IIS, bindings seem to be good....still not getting websites to work with https.
What I've done:
0: verified that my ISP is not blocking incoming on 443.
1: Added a port forwarding rule in my home/office router for 443 to the server's internal IP.
2: Tried various binding configurations in IIS.
3: Stopped and restarted the webserver via IIS after changes.
4: Checked my DNS/routing records at the domain registrar...doesn't seem to be anything I need to change here.
5: Googled for most of yesterday and this morning looking for some obvious stupid thing that I have overlooked.
6: Tried using tracert, but it won't work with a protocol in the hostname
All I'm getting when I try to access anything using https is 'can't reach this page...temporary dns error...error code (INET_E_RESOURCE_NOT_FOUND)'.
On a lighter note, I agree wholeheartedly with the idea of self-hosting and have been doing it for my small company for over 15 years.