Manage SSL and domains with Grok Bot on xCloud

Certificates fail quietly, which makes them a good fit for a Bot that checks without being asked. Ask a Grok Bot which of your sites have a certificate that expires in the next 30 days and it reads sites_index, then sites_ssl and sites_sslCertificates for each site, and answers with the provider, the status and the expiry date. For a single site it adds servers_dns_check, one lookup that says whether the domain's record points at your server and whether the Cloudflare proxy is on. A proxied record on a site that xCloud manages through Cloudflare is the finished state, so a good answer says that instead of calling it a fault. Everything here is a read and runs without a prompt, so it works on a routine.

The routine is the main reason to do this from Grok Bot. Ask the Bot: every Monday at 8:00 AM, check every site's certificate and DNS and post anything that expires within 30 days or whose record no longer points at the server. The Bot creates it, shows its next run and lets you Test run it. Because a routine runs on the Bot's cloud computer, it carries on with your laptop closed. What it cannot do alone is renew. Installing, renewing, switching or deleting a certificate stops for your approval, and a normal renewal only fires within seven days of expiry unless you ask for a forced one. So the report arrives in the conversation and you answer with a yes, which the Bot turns into sites_ssl_renew and then polls until the certificate settles. It loads the site over HTTPS before it says done.

Domains are where you will hear no. Adding, changing or removing a domain on an existing site is dashboard-only, under Site, Domain, and a staging site goes live under Site, Domain, Go Live. When you ask, the Bot reads the primary and additional domains through sites_domains, tells you what is set and gives you the path and the site's dashboard link. It does not improvise a workaround, and it will not replace a working certificate with a different provider without telling you first.

Grok Bot specific: Your DNS provider is not part of the connection. xCloud writes the DNS record and the certificate itself only at site creation, when the domain's zone is on a Cloudflare account you connected to xCloud. Everywhere else the Bot can check a record but not change it, so a report that DNS has not propagated is a message to you to fix the record at your registrar. Do not turn the propagation wait into a routine. Ask the Bot to check once, wait, and ask it again later, because each check is a single lookup. Tell the Bot which error visitors see as well: a Cloudflare 526 is an SSL fault, while a 522 usually means ports 80 and 443 are blocked at the origin, and the two need different checks.