Search results

I did contact them and they are "investigating the issue". I wanted to see if anyone here had a similar thing happen to them or if I can get some ideas how to investigate further myself. This could be either a software or hardware malfunction of sort, but I'm out of ideas how could I possibly...

Here's a screenshot of what happens when I press the <Enter> (I've been following the entire boot process over the IPMI and no error/fail appears on screen):

I'm trying to install Proxmox v.7 on a SoYouStart server (SYS-2-SAT-64) but the install procedure with SYS' install image keeps failing. When the machine is automatically rebooted, the startup halts with the following message: "Cannot open access to console, the root account is locked". This is...

So... I have found a network configuration that kinda works for me. The connectivity disruptions still happen, though, but they "revert back" at some point (then happening again and so on). I still cannot catch the cause of this behavior... None of the logs shows any anomaly. It just stops to...

So, this works perfectly, but for the node itself. But VM's below, with their failover IP's are not accessible with this. I've been trying configurations based on Proxmox manual's Network configuration, part about using a bridge, but couldn't make it work. Either my server/node is connected...

Solved, at least it seems so. I was able to get the node respond to SSH and to serve the GUI by manually setting the network, without having to hard reboot the server. If your IP at SoYouStart is a.b.c.d and your gateway is a.b.c.254, then the winning setting is: →cat /etc/network/interfaces...

I think the biggest help at the moment would be if someone could post their network configuration of Proxmox 6 on SoYouStart. The /etc/network/interfaces file. From everything I know and I've learned the past few days, I think that's the main issue with the accessibility of the node: network...

So, I definitely cannot connect over ssh after the hang happens, but if there is an already active/open ssh connection - it will keep working without an issue.

And the last part: →dpkg -l | grep pve ii corosync 3.0.4-pve1 amd64 cluster engine daemon and utilities ii dmeventd 2:1.02.155-pve4 amd64 Linux Kernel Device Mapper event daemon ii...

Other services do work OK (I have manually stopped the pve-firewall and have tried restarting all of them but the manager and guest services): → systemctl status 'pve*' ● pve-lxc-syscalld.service - Proxmox VE LXC Syscall Daemon Loaded: loaded (/lib/systemd/system/pve-lxc-syscalld.service...

Hi all, I have just started the Proxmox VE (6.2) adventure on a new SoYouStart host and since the day one I've been having GUI hangs... at least when I try to open it from my own computer. In localhost the page is served: → curl -s -k https://localhost:8006 | grep title <title>dom01 -...