Search results

pve-firewall is a feature/part of Proxmox, so you're not using any additional software.

Here're some tips after I tried restoring my firewall VM (Untangle) onto proxmox. 1. First up, make sure Proxmox firewall (pve-firewall) is not a problem. SSH to your PVE and run "pve-firewall stop" and see if everything works now. If it's still broken, continue to step 2. 2. Are you using...

You need to run this command only when the copy/move is around 96 or 98%.. You can also disable udev in lvm.conf as described above, but as mentioned do it at your own risk as I havn't tested this enough to know if it's causing issues or not (i.e. do not do this on production servers). For now...

I know it's a conntrack issue. But adding the rule manually to the chain doesn't seem to work. e.g. iptables -I tapXXXXi0-IN 1 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT After some googling, finally found the answer by searching this very forum. from this thread. sysctl -w...

So, I have changed the MTU back to 1500. Wiped out all the config files in /etc/pve/firewall, and restart the same tests from the first post. Still not working, but this time the problem is fixed if I turn off firewall at VM#3. Next, I'm trying the same test using another service - MQTT at port...

Thanks @spirit. I'm seeing a packet with a payload of 3695 bytes. That shouldn't happen, hopefully this will just work if I manage to figure out why it's doing this. Have already removed the MTU of 9000 from the bridge. Now may have to reboot the router for the change to take effect. Will try...

Thanks. Same thing. Probably because I set HAProxy to go forward HTTP to HTTPS? You may be on to something there. I am indeed using Jumbo frames (9000), although the MTU for those VMs in question are all set to the default of 1500. On the router side though (I'm using software firewall called...

I have this weird problem with a VM running HAProxy. Here's my setup. VM#1 Runs HAProxy listening at 443 Subnet is 192.168.222.0/24 Handles all my SSL certificates Based on the name, it will forward the HTTPS request to VM#2 at port 10000 Firewall rules: VM#2 Runs docker Subnet is also...

What I did to "fix" the problem is to modify /etc/lvm/lvm.conf Find the line "obtain_device_list_from_udev", change it from 1 to 0. No reboot required. All LVM operations seems to work again after this change (short test so far). Not entirely sure how safe this is, but it sure beats running...