Recent content by jforman

Youre absolutely right, and I hadn't noticed that API endpoint until now. I've made some rudimentary Python code to post TLS certificates to Proxmox VE nodes that I've posted at https://github.com/jforman/proxmox_certupdater. I'll be adding more to it to make it a bit more useful, but if...

I have pre-existing infrastructure which registers and updates TLS certificates for organization's sites via Lets Encrypt. I'd like to use this infrastructure to automatically push a new certificate to my various Proxmox VE nodes via the Proxmox API...

I think my system has gotten into an untenable state root@moon1:~# pveceph install update available package list start installation Reading package lists... Done Building dependency tree Reading state information... Done gdisk is already the newest version (1.0.3-1.1). ceph-common is...

I thought I was getting close. I brought that file back to the following contents: ``` # PVE pve-no-subscription repository provided by proxmox.com, # NOT recommended for production use deb http://download.proxmox.com/debian/pve buster pve-no-subscription # security updates deb...

As requested, output from both commands: root@moon1:~# pveversion -v proxmox-ve: 6.4-1 (running kernel: 5.4.124-1-pve) pve-manager: 6.4-13 (running version: 6.4-13/9f411e79) pve-kernel-5.4: 6.4-4 pve-kernel-helper: 6.4-4 pve-kernel-5.4.124-1-pve: 5.4.124-1 pve-kernel-5.4.78-2-pve: 5.4.78-2...

Hi Moayad, I did run it, and saw no warnings. root@moon1:~# pve6to7 --full = CHECKING VERSION INFORMATION FOR PVE PACKAGES = Checking for package updates.. PASS: all packages uptodate Checking proxmox-ve package version.. PASS: proxmox-ve package has version >= 6.4-1 Checking running...

I've read several of the other 'unable to upgrade' posts and I'm not sure what I'm missing here in my quest to upgrade from 6.4 to 7.0. Bottom of apt dist-upgrade output W: (pve-apt-hook) !! WARNING !! W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'! W...

This seems to be happening to me as well. I'm using the HTTP API to perform the clone. Rough Setup: 3 node proxmox cluster using LVM over iSCSI for shared VM storage. jforman@moon1:~$ pveversion -v proxmox-ve: 6.2-1 (running kernel: 5.4.41-1-pve) pve-manager: 6.2-4 (running version...

Thanks @fabian . I've filed https://bugzilla.proxmox.com/show_bug.cgi?id=2771 per your suggestion.

I did a bit more testing: Defining the proxmox object like this: proxmox = ProxmoxAPI(host, verify_ssl=False, user='root@pam', token_name='tokenname1234', token_value='tokenvalue1234) ..... Gives me this error: proxmoxer.core.ResourceException: 403 Forbidden: Permission check failed (user...

@oguz I was not able to. Per your suggestion, would you be able to suggest where in my above Gist I would need to use the authentication cookie? I thought the API token id/secret was sufficient for that functionality. I've never heard of an "authentication cookie" in this context.

@oguz Sadly, same thing, even when wrapped in single quotes (my shell in this case is zsh).

My code is found here: https://gist.github.com/jforman/178010d3930283949e4be45b9d3d95c7 Invoked via: % docker run --env-file=my_env_file -t -v certs/proxmox/:/certs jforman/proxmox_cert_updater ./proxmox_cert_updater.py --host moon1 --proxmox_username root@pam # my_env_file...

I'm trying to upload an SSL certificate via the API (https://pve.proxmox.com/pve-docs/api-viewer/index.html#/nodes/{node}/certificates/custom) using the Proxmoxer Python API, with an API Token tied to the root user. I think I've gotten my code right, but am seeing the following error when I...