Wildcard certificate update

[bsgirardi]

Hello everyone, first I'd like to say that I love NPM and can't live without it anymore. Given that certificate validity periods are decreasing, is there any way to update the wildcard certificate that was manually installed on all registered hosts?

[tigran-sargsyan-w]

At the moment, there doesn't seem to be a built-in way in NPM to replace one manually uploaded custom certificate and automatically update every Proxy Host using it.

The reason is that custom certificates are stored as certificate records, and Proxy Hosts reference a specific certificate ID. Uploading the renewed certificate normally creates a new certificate record, so the existing hosts still point to the old one.

For a wildcard certificate there are basically two approaches:

1. If possible, let NPM manage the wildcard certificate through Let's Encrypt + a DNS challenge. Then renewal is automatic and the hosts keep using the same managed certificate.

2. If the wildcard certificate must be generated externally, automate the replacement through the NPM API:

   • upload the renewed certificate;
   • get its new certificate ID;
   • list Proxy Hosts using the old certificate_id;
   • update those hosts to the new ID.

I would avoid simply overwriting the files inside the NPM volume. It can make Nginx use the new PEM files, but NPM's database/UI metadata such as expiration dates remains out of sync.

There are also open enhancement requests for exactly this use case — replacing a custom certificate or assigning one certificate to multiple hosts in bulk — so I don't think you're missing an existing UI option.