Search results

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?

As I said I am not aware of any challenge methods Sectigo offers. The only way to get a certificate is to use an account and get certificates by logging in. Configuring this using the above described way works now. Would not know how to do that in the UIX though.

Hi there! This is completely annoying and actually unacceptable! I write this because it works fine for PVE and not at all for PBS. But I can add more error messages to this thread: Base64 encoding the key I use for PVE: Error: urn:ietf:params:acme:error:malformed: [External Account Binding]...

Thanks, did that. In order to make it easier for others in the future I summarize what I had to do to get it working. I did all that using the CLI since I felt the UIX is not as comfortable as it should be. Register and account using your EMAIL, EAB_KEY_ID and EAB_KEY root@pve:~# pvenode acme...

Hi! We use Sectigo [1] for our x509 certs. They offer no challenge based system for ACME. We use accounts instead. I can setup an account in PVE config System/Certificates but cannot use it since I have to chose between DNS and HTTP challenge to add a certificate. Both are not an option. Please...

I want to add one more thing. Changing the ownership of backups via the UI is cumbersome if the number of backup groups is too large. The documentation for the cli tool `proxmox-backup-client` is, well, not existent. I could not find any example how to run the script **on a PBS** system. So I...

Solved it! As a former colleague once said: it's always a permissions problem. The sync was done **before** the API Token user was created. Hence all the backups belonged to the root user. Changing ownership of the backups solved it!

User/API token seem to have the correct permissions since we can see the remote datastore on the PVE. We only use the `Root Namespace`, so yes, namespace is the same.

Hi! We are in the process of replacing our current PBS system. We set up a new PBS and synced all backups to it. Then we the new PBS as remote storage to one of our PVEs for testing. We see the storage, its capacity/usage but we see no backup VM images. The backup on the new PBS checks out, all...

This is resolved. Could be that I had name and vid confused ...

Hi! When I run these two tasks - name: List VMs on Host community.general.proxmox_vm_info: api_host: "{{ inventory_hostname }}" api_user: "{{ proxmox_api_user }}" api_token_id: "{{ proxmox_api_token_id }}" api_token_secret: "{{ proxmox_api_token_secret }}" node: node -...

I created an issue on github. For some reason I get different results when I run a short python script using the proxmoxer module on our node (here I see the list of VMs) compared to when I run a task in ansible using the proxmox_vm_info module (which does not see any VMs). This is related to...

I am aware of that, but I want to clone an existing template. The "clone:" line refers to an existing template but the module complains that there is no VM with that name. And I did read the spec of the module. In fact that's where I took the code from and just replaced it with values from our...

- name: "Create Virtual Machine" community.general.proxmox_kvm: api_host: APIHOST api_user: APIUSER api_token_id: TOKEN api_token_secret: SECRET name: NEWNAME node: NODE newid: 1234 clone: TEMPLATE storage: STORAGE state: present No matter what I try I...

Thanks, that worked!

When I try to create a new VM using a non-root user I get stuck at the networking part. The existing Bridge vmbr0 does not show up for this user. When I do this as root everything works as expected. Attached screenshot shows the empty selection field. I am pretty sure that this worked before I...

I believe there is an error in the document linked. In the section called Upgrade the system you write apt update apt dist-upgrade where it should say apt upgrade apt dist-upgrade