Search results

Thanks! I contributed to it. Hopefully some day it will get implemented. Meanwhile, I'll keep searching for an Ansible module, or try to implement one myself (it's weird it does not exist yet, as managing firewall rules seems like a common task to me).

Yes, I suppose the way to go is to automate it. I mean, the GUI is fine up to a certain point but, afterwards, one should start investing time and effort in automating. I see that Ansible's Proxmox module does not support the PVE Firewall, and the Ansible Role PCT only offers container...

Oh, it is possible! I already have it working fine. The Authoritative Server is listening on the IP address 192.168.0.<id> and the Recursor is listening on the IP addresses 127.0.0.1 and 192.168.0.254. My question was not about that, but which was the recommended way to have to IP addresses of...

The reason is that I run a PowerDNS Authoritative Server for two internal zones (forward and reverse) on the IP address 192.168.0.<id> and a PowerDNS Recursor (with access to the Internet to reach the hosting provider nameservers) on the IP address 192.168.0.254 in the same LXC, and both need to...

Hey everyone! So I need a LXC in my Proxmox 7 cluster to have two IP addresses of the same 192.168.0.0/24 private network: 192.168.0.<id>, where <id> is the <ctid> assigned by Proxmox (i.e. 100, 101, 102, etc.). 192.168.0.254 (i.e this specific IP address). I have achieved this by adding two...

Hey everyone! I have read the PVE Firewall documentation plus a bunch of posts on these forums and, if I have understood correctly, there is no way to configure a single rule allowing ping among all LXC in the nodes of a Proxmox 7 cluster as rules at the datacentre level don't apply to...

So I have been suggested by a user on Reddit that I may not even need to configure a gateway in the LXC that require just a private IP address if I were to use the following: apt-cache-ng, an APT proxy. Will set it up soon, as well as an internal DNS using pDNS. pbs-client instead of scp to...

Hello everyone! I have a Proxmox 7.1 cluster with single-NIC nodes running on Hetzner with the following network interfaces: Ethernet device eno1: Public IP address assigned to the server when ordered. Bridge vmbr4001: Holds the public subnet assigned to the vSwitch with id 4001 (so that...

As per the other thread mentioned in the previous post, as per the documentation here and here, it is not possible to back up a container that has FUSE in use. Options to have certbot in a LXC: Install the Certbot Debian package (a bit behind in version, but hopefully will work fine and it...

Thank you very much for your reply, Oguz. From reading that documentation you linked I see that using snap to install certbot inside a LXC is just not possible: Therefore I am going to have to give up on the idea of using snap to install certbot to have a Let's Encrypt certificate in each...

I created this other thread with a full test of this error code 23 problem. I hope I can get some feedback there or here as the problem still persists.

I have a Proxmox 7.1-7 cluster with two nodes with a number of CTs and no VMs. Hosts communicate through a VLAN. Guests communicate through a second VLAN. I have configured a PBS 2.1-2 server that communicates with the hosts through the first VLAN. All servers have ext4 (no ZFS, no Cepth). I...

Nevermind, I found it: Go to the container options. Go to features. Mark FUSE. Shutdown. Start. Now I have a container with a working snap installation, but backups are still returning error code 23 when the FUSE option is activated and snap in use.

Only container not backing up properly is the original one, the CT 100. The only difference I have found out is that in that LXC I tried to install Let's Encrypt Certbot from snapd and, in order to do so, I had to follow these steps: https://github.com/lxc/lxc/issues/1854#issuecomment-606241047...

Okay, after a host reboot after the latest set of Proxmox 7.1 package upgrades, CT 104 was backed up successfully. It looks like those upgrades I installed two days ago without restarting the host were messing things up: INFO: starting new backup job: vzdump 104 --storage pbs1 --node proxmox2...

Okay, so it's not a matter of disk space. I managed to back up all my other LXC, including two MySQL servers and two MongoDB servers. For some reason, only my two PostgreSQL servers fail, and they are not the biggest LXC. All my LXC are Debian 11 Bullseye with the same basic configuration and...

Hi, Dietmar, and thanks for your reply. As far as I can tell, there is enough disk space left for the operation on the proxmox1 node: ~$ df -h Filesystem Size Used Avail Use% Mounted on udev 63G 0 63G 0% /dev tmpfs 13G 1.1M 13G 1% /run /dev/md2...

Hello everyone! I have a live PVE 7.1 cluster with two nodes (proxmox1 and proxmox2) and a test PBS 2.1 (pbs1) with one datastore named "local" configured at /opt/backups (same disk as the OS, as this is just a test to learn how it works). Filesystem on both PVE nodes, their containers and the...

At first I was tempted to install certbot from Debian packages but: Given how often Certbot gets updated and the amount of changes each new version brings in. Given the recommended way to install it is to use snap In the end I decided to find a way to install the snapd package and make it...

I'll make the changes, then. Thanks a lot for the heads-up, @cgimicro!