System.NullReferenceException

Question
#1

Hello,

The application is working fine for 4 other domains, however, on the subdomain, I’m seeing the following error in the logs.

Let me know what you think.

Thank you!

2019-11-17 10:31:28.594 -08:00 [INF] Certify/4.1.6.0 (Windows; Microsoft Windows NT 6.2.9200.0)
2019-11-17 10:31:28.594 -08:00 [INF] Beginning Certificate Request Process: blog.mydomain.com using ACME Provider:Certes
2019-11-17 10:31:28.594 -08:00 [INF] Registering Domain Identifiers
2019-11-17 10:31:28.594 -08:00 [ERR] BeginCertificateOrder: creating/retrieving order. Retries remaining:2
2019-11-17 10:31:28.809 -08:00 [ERR] BeginCertificateOrder: error creating order. Retries remaining:1 :: System.NullReferenceException: Object reference not set to an instance of an object.
at Certes.AcmeContext.<>c.b__19_0(Directory d)
at Certes.IAcmeContextExtensions.d__0.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Certes.AcmeContext.d__19.MoveNext()
— End of stack trace from previous location where exception was thrown —
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Certify.Providers.Certes.CertesACMEProvider.d__26.MoveNext()
2019-11-17 10:31:29.811 -08:00 [ERR] BeginCertificateOrder: creating/retrieving orde

#2

Hi Adam,

Thanks, please send your full log file through to support at certifytheweb.com, this is quite an unusual error and may be related to a specific domain. It’s also odd that it’s cycling through more than 1 retry (it will generally make 3 attempts to start the order in case there is a problem talking to the Let’s Encrypt API), which again suggests that Let’s Encrypt is rejecting something about the name. It’s also worthwhile checking your domain with https://letsdebug.net/

#3

Thanks for getting back to me.
After waiting a few days, it started just working again.