Add a cert for www to an app that has already a cert for naked domain about letsencrypt-siteextension

[cadilhac]

I upgraded to 0.4.9 but this time, I got a yellow screen with stack trace and exception:

The Lets Encrypt ACME server was probably unable to reach http://www.[mydomain].com/.well-known/acme-challenge/5a6fbU1Dwj-KGngvm1x93SpzkIGHkY4G8Afu-2_p7As
View error report from Lets Encrypt at https://acme-staging.api.letsencrypt.org/[...]/MDpeykPoc2Biy9FfeS8z3gG2LqBDKofdeNpFKZmMtF4 for more information

I don't believe that it's not able to reach this particular folder, because my app didn't change since last time and if I type the url in the address bar manually, I can get the response.

[sjkp]

Thanks for the feedback - I probably need to change the code a bit, I have not tested for this scenario.

[sjkp]

I just tested it - seems to work fine. Do you select both hostnames?

[cadilhac]

Yes I select both.

[cadilhac]

Just to be sure that it was still possible to generate a cert for my app, I selected just the www, and it worked. When I select both, it doesn't.

[chadwackerman]

Realize this isn't necessarily helpful but I just did exactly this and it worked fine. But see #32 for a related issue I was having. The blank page on error is definitely confusing.

[chadwackerman]

And now I'm having the same problem. Tried to add a subdomain and nothing happens. After updating to the latest I no longer get a blank screen. Just about 25 seconds of delay and then the page reloads.

This site extension is potentially a very critical piece of infrastructure and it needs proper logging and error reporting.

[cadilhac]

I confirm that nothing changed for me too, after upgrading to the latest version.

[sjkp]

@cadilhac is it possible for you to try again with the updated version, 0.4.9? And report back here. Preferably with log files (you can remove your domain names if you want) https://github.com/sjkp/letsencrypt-siteextension/wiki/How-to-debug

[chadwackerman]

See #36 the solution is walking amongst us

[sjkp]

@cadilhac sorry for using you as a tester for this, but I haven't been able to reproduce the error. I have implemented @chadwackerman fix - but I don't feel confident that this is the perfect fix, if the problem really is that azure doesn't response in a timely manner, because Lets encrypts servers could hit another node than the one the code is hitting if you are running multiple instances or the 10 seconds could simply be too little.

[cadilhac]

I tried with 0.4.11 and it worked !! (staging, I didn't try in real mode yet).
I also noted that it took 35s for the page to reload in case this can help you determine what timeouts are involved...

[sjkp]

@cadilhac great - thank you so much for the help. It does take a while, even when no timeouts are involved. 35s sounds reasonable.
I'm closing the issue, but just ping me if you experience any other problems.