New-PveNodesCertificatesCustom
Upload or update custom certificate chain and key.
API: POST /nodes/{node}/certificates/custom, Proxmox VE API viewer
Syntax
Section titled “Syntax”New-PveNodesCertificatesCustom [-PveTicket <PveTicket>] -Certificates <string> [-Force <bool>] [-Key <string>] -Node <string> [-Restart <bool>] [<CommonParameters>]Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
-PveTicket |
PveTicket |
No | Ticket data connection. |
-Certificates |
string |
Yes | PEM encoded certificate (chain). |
-Force |
bool |
No | Overwrite existing custom or ACME certificate files. |
-Key |
string |
No | PEM encoded private key. |
-Node |
string |
Yes | The cluster node name. |
-Restart |
bool |
No | Restart pveproxy. |
Every parameter also binds by property name from the pipeline, so an object with node and vmid properties (the output of Get-PveGuest, for one) fills -Node and -Vmid. Without -PveTicket the cmdlet uses the last connection, see Connection.
Output
Section titled “Output”A PveResponse: the data returned by Proxmox VE is in .Response.data, the outcome in .IsSuccessStatusCode. See Results and Errors.
