hey guys, have the same question.
I'd like to block outgoing SMTP for specific VMs
If I do the following:
Datacenter level:
- Firewall: Yes
- Input policy: Allow
- Security rule with SMTP restrictions for outgoing (not enabled)
Node level:
- Firewall: Yes
- Input Policy: Allow
VM:
-...
Hey Guys,
We had 24 OSDs (2 TB) drives with overall available space of 19.97 TB (replica size - 2 ) on our primary ceph-storage pool.
We added 10 more OSDs (same 2 TB drives) and having 25.42 TB only (while I'm expect to have ~ 28 TB approximately)
Funny thing, that when I added latest OSD (I...
Hello,
Sorry for bumping old thread, but is it possible to configure default VM id range from the GUI?
cluster1 - starting from 100
cluster2 - starting from 1000
The reason why I'm asking, because we're using Proxmox Backup Server and would like to backup 2 clusters to the same machine...
@mira Hello, thank you for your feedback.
I run it and that's what I got:
root@pve1:~# pvecm delnode pve7
Could not kill node (error = CS_ERR_NOT_EXIST)
Killing node 7
command 'corosync-cfgtool -k 7' failed: exit code 1
Seems like it did the trick, I don't see pve7 anymore in gui...
Hello Guys,
I mistakenly added new node to cluster using public network (instead of storage one). I'm checking https://pve.proxmox.com/wiki/Cluster_Manager#_remove_a_cluster_node
to remove the node. I powered off the machine (pve7) to make sure it will never power on again (going to...
guys, I've figured this out - it's because of Let's Encrypt SSL certificate installed on the cluster node thus you need to use covered server's hostname (in my case it's pve1.mydomain.com):
root@pve6:~# pvecm add pve1.mydomain.com
Please enter superuser (root) password for 'pve1.mydomain.com'...
Actually, the reason why I bumping this because I cannot add new node by using:
root@pve5:/etc/pve# pvecm add 192.168.200.241
Please enter superuser (root) password for '192.168.200.241': *******************
Establishing API connection with host '192.168.200.241'
500 Can't connect to...
Hey guys
https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysadmin_certs_api_gui
I, unfortunately, disrespected this warning several month ago while tried to configured Let's Encrypt SSL on primary node of my cluster (4 nodes)
Do not replace or manually modify the automatically...
Guys, has anybody managed to address this? I have exactly the same issue, trying to add 2 more nodes with the same version (6.4-13) and getting:
root@pve6:~# pvecm add pve1
Please enter superuser (root) password for 'pve1': *******************
Establishing API connection with host 'pve1'
500...
@dcsapak thank you for getting back.
not something really
the logic is :
1) primary pbs1 located in the Datacenter (connected to Juniper EX4600-40F without any firewall rules configured)
2) secondary pbs2 located in the office and connected to pbs1 as Remotes (transparent switch connected to...
Meanwhile, on pbs2 I've found out the following in /var/log/syslog:
Aug 27 21:24:01 pbs2 proxmox-backup-proxy[18001]: HTTP/2.0 connection failed
Aug 27 21:24:01 pbs2 proxmox-backup-proxy[18001]: removing backup snapshot "/mnt/datastore/pbs2_storage/vm/129/2021-08-25T13:46:14Z"
Hello Guys,
We have 2 PBS servers in different locations (inside 1 city), identical hardware configuration:
E5-2640V3 (12 Core - 2.4Ghz)
16GB PC4-2133P DIMM
2 x 250 GB SSD (OS, ZFS Mirror)
12 x 4 TB HDD (storage, ZFS RAIDZ2)
Version: Backup Server 2.0-9
One of the servers connected to our...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.