AutoSSL polls for days with no result

[LoadFactor]

I'm getting AutoSSL logs with messages like this:

3:58:01 AM The queue contains a request for a certificate for “****”’s website “****.****.com” (order item ID “1669*****”). The system last polled for this certificate at May 19, 2022, 7:56:03 AM UTC. The next poll will happen no earlier than May 19, 2022, 8:06:03 AM UTC.

More than a day later it's still polling. Meanwhile, the existing cert has expired. I have cleared the queue by renaming the sqlite database and whitelisted Sectigo's IP addresses:

178.255.81.12
178.255.81.13
91.199.212.132
199.66.201.1

(although 178.255.81.13 isn't pinging)

Restarted this, several hours later, nothing but endless "the queue contains a request" messages.

 

[Spirogg]

I'm getting AutoSSL logs with messages like this:

3:58:01 AM The queue contains a request for a certificate for “****”’s website “****.****.com” (order item ID “1669*****”). The system last polled for this certificate at May 19, 2022, 7:56:03 AM UTC. The next poll will happen no earlier than May 19, 2022, 8:06:03 AM UTC.

More than a day later it's still polling. Meanwhile, the existing cert has expired. I have cleared the queue by renaming the sqlite database and whitelisted Sectigo's IP addresses:

178.255.81.12
178.255.81.13
91.199.212.132
199.66.201.1

(although 178.255.81.13 isn't pinging)

Restarted this, several hours later, nothing but endless "the queue contains a request" messages.

I would put in a ticket to support. Had same issue with my hostname and they got it updated yesterday was expired for a couple days.

 

[LoadFactor]

I would put in a ticket to support. Had same issue with my hostname and they got it updated yesterday was expired for a couple days.

Interesting. My helpful customer has decided to delete and recreate the subdomain, so now I'll need to flush and run it again to see if the problem reproduces. If it's still there, I'll bump to support.

Thanks for the assist.

 

[LoadFactor]

Recreating the subdomain resolved the issue.

 

[Spirogg]

Recreating the subdomain resolved the issue.

Glad you got it working.