mirror of
https://github.com/tobychui/zoraxy.git
synced 2025-05-31 04:37:20 +02:00
Updated Migrating Certificates From Other Systems (markdown)
parent
34f9d656c1
commit
48f5710f6a
@ -38,5 +38,10 @@ mydomain.com.pem
|
||||
|
||||
Once Zoraxy cannot get a direct hit on searching the registered certificate, it will start checking if which certificates contains a CN host-name that matches the current SNI provided hostname. Generally speaking, you can name it to anything you want. For high traffic sites, although there are cache and in-memory lookup map in place, it would still save a bit CPU cycles if you use the first / most commonly used hostname as the filename.
|
||||
|
||||
|
||||
### ACME Update Options (Optional)
|
||||
You can create a json file with the same name of the certificates to hints the ACME module what CA to use during renewing the certificate. Assuming you have `example.com.key` and `example.com.pem` key-pairs, you can create and edit `example.com.json` and add the following contents
|
||||
```
|
||||
{"acme_name":"Let's Encrypt","acme_url":"","skip_tls":false}
|
||||
```
|
||||
If this file didn't exists, the ACME module will use the system default CA for renewing the certificate. A list of ACME names can be found in the ACME Tool dropdown. If you have a custom CA, you can also fill in the URL for the CA and set to skip TLS check if required.
|
||||
|
Loading…
x
Reference in New Issue
Block a user