Replies: 3 comments · 2 replies
-
|
Yes good idea. |
Beta Was this translation helpful? Give feedback.
-
|
I have developed a new version that includes the requested feature and harmonizes command arguments. I need some testing first i will relase soon . |
Beta Was this translation helpful? Give feedback.
-
|
🚀 A New update has been created to incorporate your request and more. Coming soon ! |
Beta Was this translation helpful? Give feedback.
-
|
I finally got around to looking at this again.. I dont see how you enable this from the example sheet. |
Beta Was this translation helpful? Give feedback.
-
|
@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 1Steps:
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 Hope this helps! 🚀 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
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?
Beta Was this translation helpful? Give feedback.
All reactions