Thanks for the answers!
Finally, I found that the issue was in IPSec.
I'm not an IPSec expert so I blindly copied the configuration recommended by the documentation. But this configuration was affected by by too fast renegotiation, making the network unreliable.
After some trial and error I...
Hi.
We have a 5 nodes Proxmox Cluster, but will be reduced t three en the next months.
I have setup an internal network with SDN/VxLAN for the first time.
Following the documentation advise, I'm using IPSEC for improved security.
In this internal network I have deployed dnsmasq for DHCP and...
Ouch! Our brain is very good at make us see what we know.
I was not even aware of the existence of this file. Now I understand better how the SDN is implemented from the definition, thanks for that :)
Here you have it
(node1)
(node2)
(node3)
Hi @spirit , thanks for your help :)
Here are the files:
/etc/network/interfaces:
(node1)
(node 2)
(node 3)
/etc/pve/sdn:
controllers.cfg is empty
zones.cfg
vnets.cfg
Hi.
I have a PVE 8.1.3 cluster with 3 nodes and I'm trying to build a VxLan based VNET. My nodes ares hosted at OVH, so VLAN is not an option.
My understanding is that this will create a single logical subnet where all the containers are connected using a local IP. That way, I can deploy or...
Hi.
I'm not sure if this is possible, but it will be super cool if it is.
I have a cluster with 4 nodes.
In each cluster there's a bridge vmbr1 defined, not connected to the public IP.
LXC are :
Linked to vmbr1 bridge
Using IP6 SLAAC for automatic address assignment
Using avahi for name...
Hi.
My setup is made by a small 3 nodes PVE cluster, a PBS for storing backups from PVE and a second PBS syncing the main data store in the first PBS.
I use Icinga2 to monitor the health of my setup. No problem monitoring PVE by using check_pve.
I want to use Icinga2 to monitor the status of...
Hi all.
I have a Proxmox VE 7 deployed. We use a lot of LXC containers. I just wonder if the buffers and cache space are shared between the different containers at host kernel level or if each container has his own and cache space taken form the memory limit assigned to it.
This can have a...
Yes, I checked in the right user. I even run a find to look for any finger* file in the full system.
I'm going to move to a different investigation line. I will deploy a new container from scratch so see if I can replicate the issue. Maybe there's something wrong in the already existing...
Hi Duniun.
It's not working for me :(
If I set PBS_FINGERPRINT to empty proxmox-backup-client is expecting to get empty as the fingerprint and also failing.
For sure it's included in the command environment. To confirm that, I give it a value, like "ignored" and then I get this:
What I...
Hi Dunuin.
Thanks for the hint.
PBS_FINGERPRINT is for sure not in the environment.
When I try to set it to empty value it fails with
So, it seems that is not disabling the fingerprint check but jest expecting an empty fingerprint and thus failing because it's not empty :(
I have started...
Hi Aaron.
Sorry. I realized that I omitted one piece of information.
That backups are taken using proxmox-backup-client in bare metal servers.
We still have some of those waiting for migration to LXC.
Backups work like a charm except for issue with the fingerprint.
Cheers,
Javier Vilarroig
Hi.
Thanks for your answer.
I understand you answer, makes a lot of sense.
In my case, both systems (server and client) are having valid LE certificates.
I don't know how to change from fingerprint to certificate validation. I have found nothing in the documentation.
Can you point me on...
Hi.
I have found that every time the SSL ACME certificate, from Let's Encrypt, is renewed, all my scripts for automated backup and restore start to fail.
The error message is
If I run the command manually I get a prompt for accepting the signature change:
After that, my scripts work again...
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.