ACME Plugin - Hetzner "DNS Console is moving to the Hetzner Console"

[Der Harry]

This also works with the Proxmox Datacenter Manager. I updated the Gist file.

 

[TaktischerSpeck]

Hey, did you reboot your server?
I didn't want to reboot my server and had the same problem as you.

Only Restarting the pveproxy alone did not work for me, but as soon as I restarted the pvedaemon as well, it worked.

Just execute this over SSH.
In the webUI, I had the problem that the PVEProxy did not come online again; it just stopped the service.

systemctl restart pveproxy
systemctl restart pvedaemon

Hi guys.
I've also have my domains at hetzner moving to hetzner cloud, and I can make it work on my PFsense, but can not add it as described as a hacky workaround above.

System is running : pve-manager/9.1.2/9d436f37a0ac4172 (running kernel: 6.8.12-15-pve)

But after adding the dns_hetznercloud.sh and change rights as the other plugins, and adding the line to dns-challenge-schema.json - as described
I can choose the plugin in the dropdown(Token is generated in the new DNS console at hetzner)
View attachment 93678
But when trying to add the plugin as available I'm getting this error:
View attachment 93676

Accoording to acme github page https://github.com/acmesh-official/acme.sh/wiki/dnsapi2#dns_hetznercloud its should be possible to run - but on this server the only acme.sh is /usr/share/proxmox-acme - but following this information in the bottom make no sense

 call setup and teardown direct
# the parameter must be set in the correct order
# $1 <String> DNS Plugin name
# $2 <String> Fully Qualified Domain Name
# $3 <String> value for TXT record
# $4 <String> DNS plugin auth and config parameter separated by ","
# $5 <Integer> 0 is off, and the default all others are on.

So not sure what to do from here - to get the hetznecloud up and running - so any help is appriciated
TIA
U

 

[Der Harry]

systemctl restart pveproxy
systemctl restart pvedaemon

Sorry for my last post.

If this solves the issue, I will change the gist.

 

[CarstenMartens]

Hello,

I tested it and on Proxmox VE,

systemctl restart pveproxy
systemctl restart pvedaemon

and for Proxmox mail gateway

systemctl restart pmgproxy
systemctl restart pmgdaemon

helps to avoid a restart.

 

[Freundschaft]

Does this also work with proxmox ve 8?

 

[CarstenMartens]

Does this also work with proxmox ve 8?

It should be, but I can't verify it since we've already upgraded all Proxmox VE servers to version 9.

 

[alietz]

This is a patch that you can apply for current Proxmox 9.x and PBS 4.x systems.

Edit:

Unfortunately it needs a reboot. Only tested for PVE (Thanks @TaktischerSpeck) PDM / PBS might still need a reboot

Updated for PDM, Update for reboot.

https://gist.github.com/egandro/f2dab8a559a665fc3c21c176c98dfc29

Thanks, I just installed this on PVE 9.1 and PBS 4.1, none needed a reboot and no VMs were stopped etc.