Recent content by proxwolfe

Got it working again (with help from ChatGPT). The problem was that while the new config files were distributed, the running corosync processes on the old nodes were still using the old (management) IP pf the new node and, hence, rejecting, the new node's packages on the corosync network...

Hi, I have a three node home lab cluster with separate corosync and management networks. One of the nodes was recently replaced with new hardware. When joining the existing cluster, apparently, I used the management network address for the replaced node instead of its corosync network address...

I use headscale, too. But establishing a common network between my otherwise segregated PVEs means to circumvent my inner firewall. If I were willing to do this, it would easier to remove the firewall instead of making an effort to circumvent it. That is a very good point. I have not added it...

Yes, that would work, if both PVEs shared the same management network. But they don't. The networks outside my inner firewall and inside are totally segregated. Nothing goes in. That's the problem in my case. And, yes, I could put them on the same network and then the migration would be not an...

Okay, so set up a tailscale network for example. That is an option, but my objective is to let nothing from the outside reach behind my inner firewall. And having a common network between inside and outside would basically circumvent the inner firewall.

I'm aiming for maximum security. But, admittedly, I'm still learning. How so? The PVE management network is, of course, separate from the DMZ network. That is, actually, the contingency, I'm trying to provide for. Well, there is the obvious option of piercing my inner firewall. But I'm...

Yes, I believe that is a classic setup. And yes, there are two fully fledged firewalls. One on the edge to the internet and one behind it at the edge of my private LAN. It does seem so. Unless, of course, Proxmox take up my suggestion to have PDM act as a conduit. I'm feeling relative...

Only the VMs live in the DMZ. The PVE that serves them does not. The PVE management interface, of course, is on a separate management network and not reachable from the DMZ.

Up to now, it has been my policy to not allow anything from the outside into my inner firewall. Ideally, I would like to keep it that way. If no viable other solutions exist, port forwarding would indeed be an easy option. But how would I integrate the authentication into the PDM migration...

Up to now, it has been my policy to not allow anything from the outside into my inner firewall. Ideally, I would like to keep it that way. If no viable other solutions exist, wireguard certainly would be an option. And how would I use that to migrate a VM from outside in? Would I set up a new...

In my homelab I have a small cluster from which I serve some applications that live in my DMZ. And I have another node inside my inner firewall on which I run some apps that need not be reachable from the public internet. Amongs others, I run PDM from there. While from inside the firewall, it it...

This did the trick. Thank you.

Hi, I have a PBS running for a while without any issues. My PVE cluster is doing regular backups to the PBS. Today, I changed the PBS's name (and FQDN). Of course, under the new name (and the new FQDN) it can't be accessed anymore by PVE. So I edited the storage.cfg in PVE to reflect the PBS...

Sorry, this was almost two years ago. I don't remember the details. But from going through the posts, I'd say that I just replaced the disk and did not issue the repair command.

I had this problem once as well and I was looking for a way to avoid running into it again. Someone pointed out that you can set a quota on a zpool to protect some space from being used. zfs get quota <poolname> Unfortunately, this gives you an absolute value and you have to do the math...