Let's Encrypt Extension for Microsoft Azure webapps - 504 Error Code

Is anyone else getting this error? I was able to issue certificates manually this morning, but now all of a sudden every request I make gets this error. I searched the help forum and previously this was caused by an outage 2 months ago. However, the LE status page doesn’t mention any outages at the moment.

System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() +121329
LetsEncrypt.SiteExtension.Core.Services.CertificateService.Install(ICertificateInstallModel model) in J:\Projects\letsencrypt-siteextension\LetsEncrypt.SiteExtension.Core\Services\CertificateService.cs:62
LetsEncrypt.SiteExtension.Core.d__10.MoveNext() in J:\Projects\letsencrypt-siteextension\LetsEncrypt.SiteExtension.Core\CertificateManager.cs:150
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() +31
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +62
LetsEncrypt.SiteExtension.Controllers.d__7.MoveNext() +805
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() +31
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +62
System.Web.Mvc.Async.TaskAsyncActionDescriptor.EndExecute(IAsyncResult asyncResult) +92
System.Web.Mvc.Async.<>c__DisplayClass37.b__36(IAsyncResult asyncResult) +22
System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethod(IAsyncResult asyncResult) +42
System.Web.Mvc.Async.AsyncInvocationWithFilters.b__3d() +72
System.Web.Mvc.Async.<>c__DisplayClass46.b__3f() +385
System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethodWithFilters(IAsyncResult asyncResult) +42
System.Web.Mvc.Async.<>c__DisplayClass2b.b__1c() +38
System.Web.Mvc.Async.<>c__DisplayClass21.b__1e(IAsyncResult asyncResult) +185
System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeAction(IAsyncResult asyncResult) +38
System.Web.Mvc.Controller.b__1d(IAsyncResult asyncResult, ExecuteCoreState innerState) +29
System.Web.Mvc.Async.WrappedAsyncVoid1.CallEndDelegate(IAsyncResult asyncResult) +65 System.Web.Mvc.Controller.EndExecuteCore(IAsyncResult asyncResult) +52 System.Web.Mvc.Async.WrappedAsyncVoid1.CallEndDelegate(IAsyncResult asyncResult) +36
System.Web.Mvc.Controller.EndExecute(IAsyncResult asyncResult) +38
System.Web.Mvc.MvcHandler.b__5(IAsyncResult asyncResult, ProcessRequestState innerState) +43
System.Web.Mvc.Async.WrappedAsyncVoid`1.CallEndDelegate(IAsyncResult asyncResult) +65
System.Web.Mvc.MvcHandler.EndProcessRequest(IAsyncResult asyncResult) +38
System.Web.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar) +177

Hi @modemgeek

I am not sure what school of troubleshooting you went to but the one I attended generally taught that pasting a log with no context doesn’t really help anyone and usually results in a situation where there is no go forward. Logs are useful to backup and demonstrate whats happening but are not a way of asking questions.

What Client are you using (if you are using a script or instructions let people know)

Please fill out the fields below so we can help you better.

I ran this command:

My web server is (include version):

The operating system my web server runs on is (include version):


Thanks for replying. However I was merely asking if anyone else was experiencing a problem that could be service related. I know about two months ago this started happening and it was due to an outage. I was merely curious if this was something similar, but just haven’t been reported yet.

We are running the Let’s Encrypt extension for Microsoft Azure webapps.

I couldn’t tell you exactly what version of Windows or IIS is running since all that is hidden from us. It is most likely Windows 2012 with IIS 8.

We were able to determine where the issue lies. It wasn’t Let’s Encrypt that was returning the 504 but one of API calls to Azure.


Thanks for that.

As mentioned there are lots and lots of clients for Let’s Encrypt and part of the steps that help others help you is sharing what the client you are using and what you are trying.

It can be very hard to deduce clients just from error messages as every client has slightly or drastically different error messages.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.