Recent content by ericpardee

ohhhhhhhhh, I see. Thanks, I was able to query the sqlite db and see what I needed. Thanks again Fabian!

Thank you for the response. root@zeusprox01:~# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert datassd pve twi-a-tz-- <794.79g 0.00 0.24 root...

Started using Proxmox VE, noticed that my hard disk was a bit slow and decided to replace with SSD. I installed Proxmox on the new SSD and all is working but I would like to access the data (view the old configs, etc.) from the prior pve disk. Both disks are using LVM. While this is similar...

Also, here's a sample AWS IAM Policy for the Proxmox VE node acme plugin to add dns verification: { "Version": "2012-10-17", "Statement": [ { "Sid": "VisualEditor0", "Effect": "Allow", "Action": [...

Figured it out thanks to my buddy The creds.txt for AWS should be: AWS_ACCESS_KEY_ID=AKIAXE7ONotReALQRAZZ AWS_SECRET_ACCESS_KEY=tt83/YrTszktnverWOuldpostmre5lkey+X7qpv8d8/df I was missing the preceding AWS_, and no, those aren't real keys

Trying to use a dns ACME Plugin: pvenode acme account register default <email> pvenode acme plugin add dns aws-dns-validation --api aws --data creds.txt pvenode config set --acmedomain0 zeusprox01.esp.zone,plugin=aws-dns-validation pvenode acme cert order systemctl restart pveproxy The issue I...