You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the current Proxmox VE deploy hook script isn't compatible with Proxmox Backup Server as is, due slight API differences.
Based upon my tests the differences are the following:
PBS listens on port 8007 by default.
PBS doesn't support user defined roles, you must create an API Token with /system/certificates path and Admin role which includes Sys.Modify permissions.
PBS API Authorization header format is different -> Authorization: PBSAPIToken=TOKENID:TOKENSECRET
The certificates update API endpoint is the same as PVE, where the node is the PBS instance nickname (shown in dashboard). pbs.example.com:8007/api2/json/nodes/{node}/certificates/custom
The current PVE deploy hook script can be easily adapted with these changes.
I have tested the API calls with Postman and was able to update the certs successfully via the API.
If you agree i can make a PR with the adapted script.
Regards!!
The text was updated successfully, but these errors were encountered:
Please upgrade to the latest code and try again first. Maybe it's already fixed. acme.sh --upgrade If it's still not working, please provide the log with --debug 2, otherwise, nobody can help you.
Steps to reproduce
Right now the current Proxmox VE deploy hook script isn't compatible with Proxmox Backup Server as is, due slight API differences.
Based upon my tests the differences are the following:
PBS listens on port 8007 by default.
PBS doesn't support user defined roles, you must create an API Token with /system/certificates path and Admin role which includes Sys.Modify permissions.
PBS API Authorization header format is different -> Authorization: PBSAPIToken=TOKENID:TOKENSECRET
The certificates update API endpoint is the same as PVE, where the node is the PBS instance nickname (shown in dashboard).
pbs.example.com:8007/api2/json/nodes/{node}/certificates/custom
The JSON Payload is almost the same, as PVE but "restart" and "force" keys are switched to <true|false> instead <0|1> as PVE.
https://pbs.proxmox.com/docs/api-viewer/index.html#/nodes/{node}/certificates/custom
Example:
The current PVE deploy hook script can be easily adapted with these changes.
I have tested the API calls with Postman and was able to update the certs successfully via the API.
If you agree i can make a PR with the adapted script.
Regards!!
The text was updated successfully, but these errors were encountered: