Fix deployment to https insecure proxmoxve instances

[ohartl]

Currently it is not possible to deploy a cert to a proxmox server when the proxmox api has an invalid certificate. For example the self signed on initial deployment or the current cert is expired. Although the deploy script should allow insecure connections.

Causing this error in the log

...
2023-11-04T15:18:44	acme.sh	[Sat Nov 4 15:18:44 CET 2023] == Info: Trying 10.0.0.18:443...
2023-11-04T15:18:44	acme.sh	[Sat Nov 4 15:18:44 CET 2023] Here is the curl dump log:
2023-11-04T15:18:44	acme.sh Please refer to https://curl.haxx.se/libcurl/c/libcurl-errors.html for error code: 60
2023-11-04T15:18:44	acme.sh _CURL='curl --silent --dump-header /var/etc/acme-client/home/http.header -L --trace-ascii /tmp/tmp.URYIOu3V -g '
2023-11-04T15:18:44	acme.sh _post_url='https://pve.domain.com:8006/api2/json/nodes/pve/certificates/custom'
2023-11-04T15:18:44	acme.sh POST
2023-11-04T15:18:44	acme.sh TARGET_URL='https://pve.domain.com:8006/api2/json/nodes/pve/certificates/custom'
2023-11-04T15:18:44	acme.sh _cfullchain='/var/etc/acme-client/home/domain.com/fullchain.cer'
2023-11-04T15:18:44	acme.sh _cca='/var/etc/acme-client/home/domain.com/ca.cer'
2023-11-04T15:18:44	acme.sh _ccert='/var/etc/acme-client/home/domain.com/domain.com.cer'
2023-11-04T15:18:44	acme.sh _cdomain='domain.com'
2023-11-04T15:18:44	acme.sh _deployApi='/usr/local/share/examples/acme.sh/deploy/proxmoxve.sh'
2023-11-04T15:18:44	acme.sh DOMAIN_PATH='/var/etc/acme-client/home/domain.com'
2023-11-04T15:18:44	acme.sh ACME_DIRECTORY='https://acme-v02.api.letsencrypt.org/directory'
2023-11-04T15:18:44	acme.sh Using config home:/var/etc/acme-client/home
2023-11-04T15:18:44	acme.sh Running cmd: deploy
2023-11-04T15:18:44	acme.sh Using server: https://acme-v02.api.letsencrypt.org/directory
...

The fix seems easy, just one _ to delete, see #4139 (comment) and #4139 (comment).

[github-actions]

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.

[ohartl]

Has been fixed with #4853