SSL and AutoSSL without certificate guessing
Manage SSL certificates and AutoSSL in SHM with domain assignment, coverage checks, renewal state, cooldown protection and detailed issuance logs.
Manage certificates, domain assignments and AutoSSL coverage with visible validation, renewal state, rate guards and issuance logs.
Certificates and domain assignments
SSL management becomes confusing when a certificate file, a domain assignment, and an automatic renewal are all presented as the same switch. SHM separates them. The certificate inventory shows the certificates available to the account, while domain assignment controls which certificate a web host actually uses.
Users can add supported certificate material, review coverage and expiry, assign a certificate to a domain, and remove certificates that are no longer needed. Matching wildcard certificates can cover related subdomains while names outside the wildcard scope remain excluded.
Check the names being served
The AutoSSL view shows account domains, current certificate coverage, expiry context, and the latest result. A run can target the account or an eligible domain, while forced renewal remains a deliberate operation for cases where normal renewal timing is not enough. Before requesting a certificate, SHM checks the conditions it can verify and reports the stage. DNS and HTTP validation still depend on the public path reaching the server. AutoSSL cannot complete validation while the domain points to another destination.
Keep validation temporary
When HTTP validation needs a temporary responder and no web server is available on port 80, SHM can use its own managed PHP runtime for the bounded challenge. The temporary process is tracked by its own PID and stopped after the attempt, including failure paths. It is not left behind as an unexpected web server.
Configuration generation and certificate deployment use validation and rollback-aware paths. The active web stack is reloaded only after the generated configuration is acceptable, reducing the chance that solving one certificate creates a wider web outage.
Respect issuance limits
Certificate authorities impose request limits. SHM records recent attempts and applies cooldown or rate protection where required, so repeated clicks do not turn a DNS problem into a week-long issuance problem. The interface shows when a request should wait and when a normal run is available again.
Disabling another attempt during the cooldown protects the domain from avoidable issuance failures and makes the next eligible run clear.
Use the run log as evidence
AutoSSL logs are available by run and can be filtered, opened, refreshed, and downloaded. They capture the validation and deployment result rather than reducing every failure to "SSL error." That distinction helps separate DNS propagation, HTTP reachability, authority limits, and local configuration issues.
SSL Manager provides manual control when it is needed; AutoSSL provides repeatable issuance and renewal. Together they make certificate state visible, keep risky retries bounded, and leave enough evidence to fix the actual cause.