Search results

I do the recreate of the rules. But at the end it was the interface vmbr0. If I remove that interface it is running without any issues. I do not understand the magic behind, cause I only want to use the rule on vmbr0. If I remove that it works instant, ssh and web ui is accessable. Maybe the...

The rules have been working for over 3 years since Proxmox 6.x without any issues. The problem starts with proxmox 8 and 9. If I turn on the lock i see that the ssh and webUi are dropped. But in iptables/ebtables I do not see any blocking rules, also in fail2ban. The thing is the ruleset is...

At the end it has nothing to do with the switch. cause if i stop pve-firewall everything works like it should. So I beöieve that is a pve problem. Any othe suggestions?

In Proxmox 9.0.6, pve-firewall stop activates ssh and webUi for affected machines, regardless if fail2ban is running or not. I also checked banned ips and iptables. everything seems to be ok. No blocked IP. If i start pve-firewall, ssh and webUi does not work.

Hello, yes I'm able to connect to ipmi, which is like a physical connection through the server's remote management directly on the machine. I cann do a ssh to all of the nodes from each host to the others. a netstat -al shows that port 8006 and ssh ate listening internal and external. I can...

We have a 3-node cluster and it workes perfect with proxmox 8 since the last updates periods 2-3 months. The webUi and ssh is unreachable after a non-determistic time. A reboot of the affected machine solves the problem. So I give Proxmox 9 (9.0.6) a chance. But ends in the same result. if I do...

Updated to Proxmos 9.0, but problem still exists. It has something to do with pve firewall. If I stop it ssh and web ui are accessable! So I will start investigating here...

Also with kernel 6.14 the problems still existing. Any suggestions?

It seems it is the kerne 6.12, with new Kernel 6.14 the problems are no longer existing.

So fail2ban is completly remove and it appears again....

IPMI is responsible and I can log in... so service ssh status leads me to fail2ban and there is a wrong backend configured!

It seems to be the service fail2ban, cause the system is migrated from Proxmox 6 over the years. And the new backend is systemd, no more logs!

Hello, we have a problem in our 3 node production cluster which is based on Proxmox 8.2 latest kernel (no-subscription). The Cluster hat 768GB Ram, 300 core and 24TB Space. The cluster is not overcommited and has enough resourves. The web urls on port 8006 are available for a time. Then one by...

Where did you find the package ceph-exporter, cause I didn't find one for ceph 19.x?

I installed grub-efi-amd64 on a test machine made some changes in /etc/defaults/grub.cfg and reboot the system. System is started normally without any issues. If installing grub-efi-amd64 the package grub-pc is removed. System is a Dell R740XD Intel Xeon Gold based system.

After updating to latest backup tool vzdump on 19.11.2023 the backup jobs always notify after backup. Config is vzdump 100 102 103 104 105 106 113 111 112 9998 101 109 9999 107 108 121 123 122 124 500 501 502 110 --notes-template '{{vmid}}.{{guestname}}' --mailnotification failure --mode...

@LnxBil: yxou are right it depends on the container and I guess it's the sqlite db, cause I get a lot of knex timeouts in both setups after a while (db is growing, we monitored more then 500 instances). Something happend within the connection pooling of the node.js server application. Connection...

I found only this error: kex_exchange_identification: Connection closed by remote host Seems to be a sqlite3 problem within the container

I checked the system load and the disk is, this is not the problem bare metal is not heavy utilized round 5-10 %. And yes sometimes it occurs off backups are running. The docker container I ran was uptime kuma. On lxc that is placed on the same bare metal does not have time outs in kuna. I know...

Hello, The vm has twice power, double cpus and double amount of ram and I get the timeouts. The lxc container wirft docker works as expected without timeouts. So I believe to upgrade lxc container‘s resources will have no effect. I checked the stats and send it tomorr.