Recent content by thesix

This morning's automatic renewal job failed as usual. This afternoon I switched on debugging and ran a manual renewal for the certificate as requested by Harica support. This worked, I have a new certificate now. I guess I leave this for now and hope I do not have to revisit this issue next...

Well, you could just buy a certificate from them for €36 :cool: but I will try to find a solution.

What would you need? There is already a debugging log in the other thread regarding this issue.

Das Problem besteht weiterhin und alle Selbstheilungen scheinen auf Zufall zu basieren. Es gibt mittlerweile einen Bugreport dazu.

No, unfortunately it does not resolve.

It is disappointing that after so much time the problem persists. Meanwhile we run pbs v4.2.5 and the error still exists. Anyone have a clue what's going on here?

We upgrade PBS to 4.1.0 today but the problem still exists :oops:

By the time of this writing it was not possible to create/edit/delete ACME accounts via GUI. Thas has changed, so this issue is obsolete.

OK, that could be the problem here too.

I don't want to disclose that here in public. Suffice to say that the certificates are created at the provider, it works for proxmox pve hosts in the same subnet behind the same firewall. This still has me puzzled :cool:

We did a check on firewall logs and found no anomaly, no trace of dropped packets. I can confirm that the certificates were created but somehow the process stops before successfully retrieving the certificate. I did try the same process on one of our PVE nodes and it worked flawlessly. PVE and...

Since a couple of days our PBS tries to renew its x509 cert. We configured it to use our ACME-PROVIDER with the same credentials we use everywhere else. Here is what happens. We get emails stating: Proxmox Backup Server was not able to renew a TLS certificate. Error: connection closed before...

Hi, I ask politely: when will there be a working account creation for ACME accounts (that are NOT letsencrypt) in the GUI? Sincerely, T.

I believe you and at the same time state that this is undesired behavior. But thanks for taking you time. Just checked btw. The certificate I configured via CLI appears as ACME HTTP in the UIX ...

Just out of curiosity: why would you need a challenge if you are using EAB?