Is it possible that these helper scripts is causing an error in Proxmox?

[mosespray]

I have been trying to install a proxmox cluster for months now. I have re-installed it so many times that I can do it in my sleep.
I have 5 HP EliteDesk G2 Mini computers and 2 SuperMicro servers that I am trying to use together in a cluster.
First, let me say that I LOVE these community scripts. They are so easy to use and save so much time.
I just did a fresh install of proxmox 8.4.1 on the HP mini's. I joined them into a cluster and all went well. After a while, I started installing apps using the community scripts, Dashy, nginx proxy, IT-Tools, Watchyourlan, Semaphore, Kuma, and Prometheus.
When I went back to check on things I got this dreaded error. If I log into the first node and I click on shell, I get undefined ( code: 1006 ). I also get the message "failed waiting for client: timed out
TASK ERROR: command '/usr/bin/termproxy 5900 --path /nodes/proxmox01 --perm Sys.Console -- /usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=proxmox01' -o 'UserKnownHostsFile=/etc/pve/nodes/proxmox01/ssh_known_hosts' -o 'GlobalKnownHostsFile=none' -t root@10.10.99.41 -- /bin/login -f root' failed: exit code 1"

Originally when I started to get this error, it was sometime after installing either pve-nag-buster or the Proxmox VE Post-Install script. I tried raising this issue in the proxmox forum, but I was quickly dismissed or they blamed the scripts, etc.

Anyway, I can't possibly be the only one experiencing this error. I guess I will do a new install and not use any scripts to see if I still get the error. I would hate to have to do that.

By the way, if I log into a different node, it doesn't have the error. Could there be some bios setting that I need to change to fix a timeout issue?

Thank you for listening.

Best,
Dave

[michelroegl-brunner]

I dont really see how the scripts would cause this problem, only thing i would see is the Post install script and you disable chrono or other HA things, wich would be needed for a cluster.

Best way to troubleshoot would be to reinstall the offending node and see if the error persits when no script was run. If this is the case, run the scripts one by one with some time inbetween them, to see wich might be the problematic one, so we can further look into it.

Also check if your bios and firemwares are up to date.

[mosespray]

Hello,
Thank you for the response. It must have something to do with my network. It seems to come and go. Very frustrating.