I figured out to make my DC safer and add SSL cert for trusted https that is only accessible from LAN, with 2FA etc...
however when pvenode acme cert order -f
Can't use an undefined value as a HASH reference at /usr/share/perl5/PVE/API2/ACME.pm line 196.
I never messed with certs before, this...
I'm in need of executing a script to allow traffic through firewall and open port 80 inbound to the PVE (and next PBS), and then once done, close the ports etc.
Is there a current way to do it in PVE 7.x ?
I am using an ACME server other than Let's Encrypt, and I observe PVE is having issues creating the CSR for IP addresses.
Depending of the order of the domains (the actual domain and the IP) to be verified I add in the GUI to be verified it creates a bad CSR that is not accepted by the ACME...
how to automate the use of certificates that are issued by your local certification authority?
deployed my center, I receive a certificate from it through certbot and it is located /etc/letsencrypt/live/%FQDN
I wanted to put files from /etc/letsencrypt/live/%FQDN into /etc/pve/local through...
I want to ask you how to change the port of the HTTP daemon, which is started when the certificates order is triggered.
I would prefer 8080 for example or whatever else.
I am getting "Failed to initialize HTTP daemon" error at the end of the task because my 80 port is being used by...
I can't seem to find any doc or description of the format for supplying "API data" to an ACME dns-01 challenge using the Azure plugin. I'm asking about the expected format of the parameters that need to be passed to the plugin via this dialog:
I tried using the CLI but it returns an...
I use a different hostname for SMTP and API/GUI. The certificates are separate. However, I want to understand what the best practice is because I may have done this reverse from what it should be.
PMG IP: 192.0.2.1
The ACME settings are:
mx.example.com -> smtp
hostxyz123.example.com -> api...
I was able to successfully get a Lets Encrypt cert for my PVE box, using the domain: PVE.domain.com, but I am only able to access the server as such. If I connect to the server locally at https;//PVE:8006/, I get an err_cert_common_name_invalid error in chrome. Is there any way to add SANs to...
I'm using PVE's ACME client to get a certiifcate from my ACME server. I added two names: "domain.com" and "172.16.0.1" in the control panel.
The certificate I finally got has its Subject Alternative Name = "DNS:domain.com,DNS:172.16.0.1". It's invalid. It should be...
For my internal PVE nodes I want to get ACME working. Since I'm behind a NAT firewall and the single IP's port 80 is not available, I'm trying with the DNS API challenge.
Unfortunately, my own web hoster does not provide a DNS API, so I forwarded a subdomain to 1984.hosting, which has a built-in...
The title says pretty much it all. :)
I'm writing an API client and a Terraform provider for Proxmox VE. So far the `version` and `storage` endpoints are working (albeit not necessarily complete :D ). I'm now trying to create an ACME account but I get a `403 Permission check failed (user !=...
Would it be possible to add the TLS-ALPN challange method to ProxMox's ACME implementation? I don't have the ability to use port 80 or DNS for one of my servers.
renewing of our let's encrypt certificates worked flawlessly until now.
Any ideas what could have changed with the recent updates towards PVE 7.2
root@jupiter2:~# pvenode acme cert renew
Loading ACME account details
Placing ACME order
ich habe aktuell Proxmox neu installiert und gerade meine Festplatten sind richtig gemountet. Danke nochmals an @Dunuin
Habe jetzt ein anliegen bezüglich der Zertifizierung.
Ich habe ein ACME Account eingerichtet in Proxmox als Default "Let's Encrypt V2".
Da steht auch das es...
I am seeing failures to obtain certs via letsencrypt in proxmox. The documentation shows that it simply leverages the official acme.sh, and I am pointed there for configuration information.
Following documentation found here: https://pve.proxmox.com/wiki/Certificate_Management:
# pvenode acme...
Hello, we are using PMG v 7.1-2
We started using the integrated ACME, but when the certificates are automatically generated, for some reason, they always contain outdated Let's Encrypt R3 certificate chain which expired in 2021.
This means that TLS with our customers stops working every time...
zunächst vorweg, wir sind noch recht frisch bei Proxmox und experimentieren gerade ein wenig damit herum um bei den vielen Möglichkeiten den Durchblick zu bekommen. Aber es ist einfach großartig :)
Ich bin so zB erst vor kurzem auf die Möglichkeiten mit den (ACME)Zertifikaten gestoßen...
I'm trying to setup PVE to automatically challenge my DNS with the google cloud api but when i tell it to order my certificate i get an error. It keeps saying it cant access the directory /nonexistent/.config.
I dont know if i should post this here on or on another thread for acme.sh or gcloud...