<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[SSL Certificate Stuck in Processing – Please Check&#x2F;Reset ACME Request]]></title><description><![CDATA[<p dir="auto">I recently purchased Premium Cloud Hosting along with my domains from SiteCountry.</p>
<p dir="auto">My domain <a href="http://srrla.com" rel="nofollow ugc">srrla.com</a> is already added to my hosting account, and the DNS/nameservers are pointing to SiteCountry.</p>
<p dir="auto">I tried to install the free SSL certificate using Get automatic certificate from ACME Provider. I accidentally submitted the ACME SSL request multiple times.</p>
<p dir="auto">Now the SSL Certificates section still shows:</p>
<p dir="auto">“No items to show”</p>
<p dir="auto">And when I try to request the SSL again, I get this error:</p>
<p dir="auto">“Domain is already processing an SSL request. Please allow it to finish before making another request.”</p>
<p dir="auto">Please check the pending ACME/SSL request for <a href="http://srrla.com" rel="nofollow ugc">srrla.com</a> from your server side and, if necessary, reset/retry the pending request and install the free SSL certificate.</p>
<p dir="auto">The same SSL issue may also be present for my other domains <a href="http://odikan.com" rel="nofollow ugc">odikan.com</a> and <a href="http://srrla.in" rel="nofollow ugc">srrla.in</a>.</p>
<p dir="auto">Please check all three domains and let me know if any DNS validation or other action is required from my side.</p>
<p dir="auto">Thank you.</p>
]]></description><link>https://talk.sitecountry.com/topic/195/ssl-certificate-stuck-in-processing-please-check-reset-acme-request</link><generator>RSS for Node</generator><lastBuildDate>Sun, 16 Aug 2026 09:26:43 GMT</lastBuildDate><atom:link href="https://talk.sitecountry.com/topic/195.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 16 Aug 2026 03:47:56 GMT</pubDate><ttl>60</ttl></channel></rss>