Search results

I was able to successfully add 6 domains to the ACME list, but the following error message appears on the 7th:

/usr/share/javascript/proxmox-widget-toolkit/proxmoxlib.js in this file I replaced acmedomain_count: 5 with acmedomain_count: 50, and replaced for (let i = 0; i < Proxmox.Utils.acmedomain_count; i++) { with for (let i = 0; i < 50; i++) { I restarted the pmgproxy service and now ACME accepts...

Hello! I downloaded and started using the Proxmox Mail Gateway 8.1 software. In the Configuration/Certificates menu, ACME has 5 domains created and it won't let me add more, but I don't get any error messages. Is this a bug or a limitation of the free version? Best regards, Zoltan

When I want to create a VM on node3 on this LVM (), I get this error messasgo in the log: create full clone of drive scsi0 (STREAMER-TESZT:133/vm-133-disk-0.qcow2) Command failed with status code 5. command '/sbin/vgscan --ignorelockingfailure --mknodes' failed: exit code 5 TASK ERROR: clone...

i found on node 2 in journalctl (at this time i restarted node2): Dec 14 14:13:47 node2 kernel: scsi host5: iSCSI Initiator over TCP/IP Dec 14 14:13:47 node2 kernel: scsi 5:0:0:0: Direct-Access TrueNAS iSCSI Disk 0123 PQ: 0 ANSI: 7 Dec 14 14:13:47 node2 kernel: sd 5:0:0:0: Attached...

root@node3:~# pvscan PV /dev/sdb VG PROXMOX-LUN-0 lvm2 [<10.00 GiB / <4.00 GiB free] PV /dev/sda3 VG pve lvm2 [66.55 GiB / 8.25 GiB free] Total: 2 [<76.55 GiB] / in use: 2 [<76.55 GiB] / in no VG: 0 [0 ] root@node3:~# vgscan Found volume group "PROXMOX-LUN-0" using...

node1: node2: node3: until I restarted node 2, it didn't work there either, but since then everything is fine. live migration also works. it would probably work on node3 too if I restarted it...however, I wanted to solve it without restarting. root@node2:~# lsscsi [0:0:0:0] cd/dvd...

I tried the following command without success: systemctl restart pvedaemon systemctl restart pveproxy systemctl restart pvescheduler systemctl restart pvestatd systemctl reload pvedaemon systemctl reload pveproxy systemctl reload pvescheduler systemctl reload pvestatd

Hello! My cluster consists of 7 nodes. I would like my iSCSI storage to be available on all of them. Here's how I did it: This is a two step procedure and can be fully configured via the web interface. First, add the iSCSI target. (On some iSCSI targets you need to add the IQN of the Proxmox...

I have also this problem: Dec 09 00:00:45 node6 pvestatd[1205]: got timeout Dec 09 00:00:45 node6 pvestatd[1205]: unable to activate storage 'DEBIAN-10-DEFAULT' - directory '/mnt/pve/DEBIAN-10-DEFAULT' does not exist or is unreachable Can you send me the solution?

OK, thanks.

Sorry, my mistake. My fault. I only changed the config in /etc/corosync/corosync.conf, I did not change /etc/pve/corosync.conf. I overwrote the file /etc/pve/corosync.conf, and everything is fine, now the GUI shows it well. I'm sorry to bother you. :)

I tried, but nothing changed. I changed the version from 7 to 8 in the config, but the GUI still has 7. It's like the GUI hasn't updated... I don't know...

root@node1:~# cat /etc/pve/corosync.conf logging { debug: off to_syslog: yes } nodelist { node { name: node1 nodeid: 1 quorum_votes: 1 ring0_addr: 192.168.6.20 } node { name: node2 nodeid: 2 quorum_votes: 1 ring0_addr: 192.168.6.21 } node {...

Hello! I have Proxmox 7.3 VE. Afterwards I added a failover link to the Cluster. (added lines to the corosync.conf) Everything is fine, but in the GUI I cant see the second link. In the CLI: GUI: hat should I do to show it well in the GUI? Best regards, Zoltan