Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- Issuance, installation to the target path, service reload and the certificate seen by clients are separate steps.
- A case-sensitive string comparison of SAN text can falsely reject DNS names that differ only in letter case; compare hostnames according to DNS rules and verify the actual certificate.
- Cron and an interactive shell can use different PATH, HOME and script locations, so a successful manual command does not prove the scheduled task runs the same script.
- Keep the last known-good certificate and deployment logs; roll back only when the new certificate is actually invalid or mismatched.
Separate renewal, deployment, validation and rollback
acme.sh issuing a certificate successfully does not prove that Nginx or x-ui loaded it. A renewal flow may also copy/install the certificate, validate its contents, reload a service and restore an older file on failure. A false result at any stage can leave the file on disk different from what clients receive.
If a script restores an old certificate after a SAN check fails, compare the ACME output, candidate certificate, deployment target, rollback record and certificate actually returned by the server. A recent file timestamp does not prove the new certificate is in service, and a rollback log does not mean you should immediately request another certificate.
Read the candidate certificate SAN, validity and target hostname
On the server, inspect the candidate certificate's subject, issuer, validity and subjectAltName. Confirm that the requested DNS name is present. Hostname validation should use SAN; do not rely only on the CN or a substring comparison in a script. If the certificate lacks the requested name or is expired, stop deployment and correct the ACME request instead of weakening validation.
Then test the complete hostname with a validation option supported by the installed OpenSSL release. Tool options vary by version; if a command is unavailable, use the equivalent documented for that release. Redact private-key paths, real hostnames, account directories and deployment identifiers before sharing output.
Read the candidate certificate SAN and hostname match
shCERT='/PATH/TO/CANDIDATE-CERT.pem'
openssl x509 -in "$CERT" -noout -subject -issuer -dates -ext subjectAltName
openssl x509 -in "$CERT" -noout -checkhost EXAMPLE.HOST
Check whether deployment code compares SAN with the wrong case rules
If the certificate contains the requested name but the script still reports a mismatch, inspect whether the validator compares SAN text and input using a case-sensitive raw string operation. DNS hostname matching must follow the relevant name-matching rules. Do not bypass validation by removing the SAN check, comparing only the CN or accepting arbitrary wildcards. Use a supported X.509 hostname verifier for wildcard boundaries.
Before editing, save the deployment script and current valid certificate. Change the comparison only when the checker falsely rejects a real match, then test the correct hostname, an incorrect hostname and wildcard boundaries offline. If SAN itself lacks the name, the correct action is to reject installation and fix the issuance request, not weaken the check.
Compare cron with the interactive script path and environment
A manual renewal may find the right acme.sh and deployment script in a login shell, while cron uses another user, HOME, PATH or config directory. Inspect the scheduled command, absolute script path, permissions and logs. Confirm that the acme.sh account configuration and renewal certificate belong to the same user. Do not close an alert just because an interactive command worked.
If cron points to an old script or obsolete path, back up the scheduled task before updating it to a confirmed absolute path. Do not put private keys, DNS API tokens or full account directories in a cron line. Verify the next controlled run reads the updated configuration and check issuance, deployment, validation and reload stages in its log.
Inspect the current user's scheduled tasks and timers
shcrontab -l
systemctl list-timers --all | grep -iE 'acme|cert|renew'
command -v acme.sh
Verify the certificate actually served before removing older copies
After deployment, inspect the certificate SAN, validity and chain on the actual Nginx or x-ui TLS port using the target SNI. Confirm that the service reloaded the intended file, then check again through the real access path. If the local port is updated but the public endpoint still serves the old certificate, inspect reverse proxies, CDNs, load balancers and caches instead of repeatedly issuing certificates.
Consider deployment complete only after the new certificate matches the hostname, the service reload succeeds and the actual entry serves it. Retain the old certificate until the new one has passed checks on all intended ports. Do not remove backups early or disable a known-good certificate.
Verify the certificate chain and hostname actually served
shDOMAIN='EXAMPLE.HOST'
CONNECT_ADDRESS='127.0.0.1'
PORT='REPLACE_WITH_TLS_PORT'
openssl s_client -connect "$CONNECT_ADDRESS:$PORT" -servername "$DOMAIN" -verify_hostname "$DOMAIN" -verify_return_error </dev/null
Rollback conditions and safety limits
If the new certificate lacks the target name, is invalid or the service reload fails, restore the last verified certificate and deployment configuration, reload and inspect the real endpoint. If only the script validation is wrong, do not let it overwrite a valid new certificate; correct the validator and preserve the candidate file first.
DNS hostname case, SAN semantics and OpenSSL command behavior depend on the applicable standard and tool release. Record renewal logs, cron environment and external TLS results separately. Issuance success is not proof of deployment, and a script rollback alone is not proof that the new certificate is invalid.
Sources
Frequently Asked Questions
Why can the site still serve an old certificate after ACME succeeds?
Issuance, copying to the service directory, validation, reload and the certificate returned at the public endpoint are separate steps. Check each one.
Does a SAN that differs only by letter case always fail?
Do not conclude that from a case-sensitive text comparison. Verify the full hostname using DNS name-matching rules and the installed X.509 validation tool.
Does a successful interactive renewal mean cron is fixed?
Not necessarily. Cron can use a different user, PATH, HOME, script path or certificate configuration directory. Inspect the actual scheduled command and run log.
When can I delete the old certificate backup?
Only after the new certificate passes the target SNI, actual TLS port and intended external-entry checks, and the rollback window has ended.