Search results

I've also run a proxmox ve server and have never had this happen, only on my backup server. What do you mean by all devices exactly? The proxmox backup server is standalone.

My TOTP failed suddenly so I removed the tfa.json and tfa.json.lock lock files from /etc/proxmox-backup/ and now I can't verify TOTP. Inside /etc/proxmox-backup/ the tfa.json.lock lock file keeps getting created right after I delete it. Running Backup Server 2.4-1. How can I get TOTP working again?

The update to 7.4-3 has fixed this issue.

root@proxmox:~# journalctl --unit=pvescheduler.service --since 2023-05-05 -- Journal begins at Fri 2022-12-09 00:58:46 AKST, ends at Tue 2023-05-09 01:17:01 AKDT. -- May 06 22:16:47 proxmox.example.com systemd[1]: Stopping Proxmox VE scheduler... May 06 22:16:48 proxmox.example.com...

That's correct and it did not run on May 8, it refuses to run every day at 9pm which it is scheduled to do. 08:17:27 AM CEST is the time that I manually clicked the run button inside proxmox, the backup will not run otherwise. Here is the journal output: root@proxmox:~# journalctl...

This is the json file: {"upid":"UPID:proxmox:001EC557:0ABAE3BB:64574277:vzdump::root@pam:","state":"started","config":{"enabled":1,"schedule":"21:00"}} I'm not sure what you mean by the journal, can you be more specific on how I can give you the output of journal?

Backup Server 2.4-1 Virtual Environment 7.4-3 My scheduled backups will not run unless I run the following on my proxmox server: systemctl stop pvescheduler systemctl start pvescheduler After I do this the scheduled backup triggers and runs but it will not run daily as it is set to do. I know...

I found this, may be of interested to this thread: https://www.mouser.com/catalog/additional/SanDisk_WD_Write-Intensive_ProdBrief_US_1017161.pdf

Thanks so much for the info everyone! I have a DHCP server I need to filter access to and I needed a MAC prefix set for it! Easy peasy.

Worked for me with old pve installs on a disk that errored "has holder...". Thank you.

I kinda figured out a way to do this but it's not exact. The default extent size in a proxmox installation is 4mb so it's 4mb x the number extents available to give you an approximate total volume in gb or tb. This exact number will not work in the resize, you'll need to take off around 100gb...

I see that on a KVM VM it's the same numbers. Any advice would be appreciated.

Is there an easy way to resize an LXC containers disk to the max size? I see outputs like: Insufficient free space: 25600 extents needed, but only 1541 available What are these numbers? I tried kilobytes and bytes but it didn't make sense. If I knew the available number I could probably get it...

That's awesome, great news with all the cheap incompatible Windows Server 2022 hardware on sale right now :)

Is it possible to install a windows 11 vm on a host server running proxmox 7.x that does not have tpm? Or does the host server need to be tpm enabled to run a windows 11 vm?

Thanks @oguz makes total sense. I just went ahead and did a htpassword directly on the login and then 2fa. Got tired of limiting IPs but all solved now, thanks for all the support.

I figured out the issue on this. It's not an nginx or SSL issue it's a pveproxy issue. I have my pveproxy secured with specific IPs like so: ALLOW_FROM="192.168.0.1,192.168.0.3,192.168.0.1,192.168.0.5" DENY_FROM="all" POLICY="allow" Obviously not using my real IPs, but I have all the IPs of the...

I got to the: Welcome to nginx! page using this: # HTTPS server server { listen 443 ssl; server_name proxmox.mysite.com; ssl_certificate /etc/letsencrypt/live/proxmox.mysite.com/fullchain.pem; # managed by Certbot ssl_certificate_key...

In /etc/hosts it shows: my.ip.address proxmox.mysite.com proxmox pvelocalhost And no there is nothing inside /etc/nginx/sites-enabled/ Bummer, I've been using proxmox for 6 years now after many upgrades and this is a first for me. It always worked until now.

I purged nginx and reinstalled and still the same gateway error. cat /var/log/nginx/error.log: [error] 14755#14755: *1 peer closed connection in SSL handshake (104: Connection reset by peer) while SSL handshaking to upstream, client: 201.84.22.108, server: _, request: "GET / HTTP/1.1"...