Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Set up HTTPS, manage TLS certificates, and debug secure connection issues.
Set up HTTPS, manage TLS certificates, and debug secure connection issues.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Activate on: SSL certificate, HTTPS setup, Let's Encrypt, certbot, TLS configuration, certificate expired, mixed content, certificate chain error.
TaskTool/MethodGet free certcertbot, acme.sh, Caddy (auto)Check cert statusopenssl s_client -connect host:443View cert detailsopenssl x509 -in cert.pem -text -nooutTest configssllabs.com/ssltest or testssl.shConvert formatsSee formats.md
# Let's Encrypt with certbot (most common) certbot certonly --nginx -d example.com -d www.example.com # Check expiry echo | openssl s_client -connect example.com:443 2>/dev/null | openssl x509 -noout -dates # Verify chain is complete openssl s_client -connect example.com:443 -servername example.com # Look for "Verify return code: 0 (ok)"
ErrorCauseFixcertificate has expiredCert past valid dateRenew with certbot renewunable to verify / self signedMissing intermediate certInclude full chain in confighostname mismatchCert doesn't cover this domainGet cert for correct domain or add SANmixed contentHTTP resources on HTTPS pageChange all URLs to HTTPS or use //ERR_CERT_AUTHORITY_INVALIDSelf-signed or untrusted CAUse Let's Encrypt or install CA cert For detailed troubleshooting steps, see troubleshooting.md.
Nginx: server { listen 443 ssl http2; ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; } Apache: SSLEngine on SSLCertificateFile /path/to/cert.pem SSLCertificateKeyFile /path/to/privkey.pem SSLCertificateChainFile /path/to/chain.pem For Node.js, Caddy, Traefik, and HAProxy, see servers.md.
Let's Encrypt certs expire in 90 days. Always automate: # Test renewal certbot renew --dry-run # Cron (certbot usually adds this) 0 0 * * * certbot renew --quiet
TypeUse caseSingle domainOne site (example.com)Wildcard (*.domain.com)All subdomainsMulti-domain (SAN)Multiple different domains on one certSelf-signedLocal dev only โ browsers will warn
Application auth (JWT, OAuth) โ see oauth skill SSH keys โ see linux or server skills VPN/tunnel setup โ see networking skills Firewall configuration โ see server/infrastructure skills
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.