Wildcard Certs

[Ncgodwod]

Looking at the script, I dont see a way to use wildcard certs? Like --host-ssl-enable 31 --ssl-cert-id 1.

Instead of making a new ssl cert, just use a wildcard cert/any cert based on cert id?

[Erreur32]

Yes good idea.
i will check to add this. in new release.

[Erreur32]

I have developed a new version that includes the requested feature and harmonizes command arguments.

I need some testing first i will relase soon .

[Erreur32]

🚀 A New update has been created to incorporate your request and more.

Coming soon !

[Ncgodwod]

I finally got around to looking at this again.. I dont see how you enable this from the example sheet.

[Erreur32]

@Ncgodwod The wildcard certificate functionality is already implemented! 🎉

I need to update the documentation ;)

You can use an existing wildcard certificate with this command:

./npm-api.sh --host-ssl-enable <host_id> <cert_id>

Example:

# Use wildcard certificate ID 1 for proxy host ID 31
./npm-api.sh --host-ssl-enable 31 1

Steps:

1. List your certificates: ./npm-api.sh --cert-list
2. Find your wildcard cert ID (e.g., *.example.com = ID 1)
3. List your hosts: ./npm-api.sh --host-list
4. Apply the wildcard cert: ./npm-api.sh --host-ssl-enable 31 1

This will assign your existing wildcard certificate to any proxy host without generating a new certificate each time. The feature has been available since the script supports the <cert_id> parameter in the --host-ssl-enable command.

Hope this helps! 🚀