Compatible with
account required
Nginx
Nginx deployment Atomic write of fullchain.pem and privkey.pem under a configured directory, config test, reload, TLS verify, rollback of previous files. ssh/WinRM sessions use pinned host keys. nginx -t then nginx -s reload (allowlisted)
Verification: test_verified. Connection: unknown. Credentials: none. Live E2E: no.
No disposable Nginx host with pinned known_hosts and a TLS listener is configured.
What sslcertificates.io can do
Nginx deployment Atomic write of fullchain.pem and privkey.pem under a configured directory, config test, reload, TLS verify, rollback of previous files. ssh/WinRM sessions use pinned host keys. nginx -t then nginx -s reload (allowlisted) Capabilities: atomic_write, config_test, reload, tls_verify, rollback. Authentication uses ssh.
Required permissions
Restricted service account. Commands are allowlisted: nginx -t then nginx -s reload (allowlisted). Known-host verification is mandatory.
Setup
Open Dashboard → Integrations → Nginx. Enter the credentials described on this page. Values are encrypted at rest and never shown again. Run Test connection. Discovery runs only after authentication succeeds. Select a discovered resource. Do not paste opaque IDs unless the provider cannot enumerate them. Perform the certificate or notification action, then confirm the external system matches. Disconnect removes stored credentials and owned test resources created by sslcertificates.io.
Known limitations
User-supplied shell is rejected. A successful file write is not enough; the TLS endpoint must present the new fingerprint.
Official sources
Fact checked 2026-09-20. https://nginx.org/en/docs/http/configuring_https_servers.html Nginx is a trademark of its owner. sslcertificates.io is not a partner or certified reseller unless a written agreement exists.
Capabilities
Connect
Nginx is a trademark of its owner. sslcertificates.io is not a partner or certified reseller unless a written agreement exists.