Search results

Hey, Anyone of you might got an idea what the issue could be?

Hey, @Moayad do you got an idea on this? or anyone else? Thanks.

Hey, Oh sorry, I should have mention that. I am using as per documentation: https://pve.proxmox.com/pve-docs/api-viewer/#/nodes/{node}/qemu/{vmid}/vncproxy However, the code also appends ?websocket=1, using this since Proxmox 5.x. Removing websocket=1, despite not using websockets at all, just...

Hey, When I request a VNC session from Proxmox using the API, the timeout is pretty short with less than 5 seconds. Anybody got an idea if its possible to adjust it? So far I didn't find any way yet.... Regards, Ne00n

Had the same Issue, partially copied from OVH, this one works for me. # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo...

I tried your setup again with an older Proxmox 7.x iso seems to worked for now. Thanks!!!!

Please, read what I say. https://en.wikipedia.org/wiki/Booting Not be confused with boo tang.

Did you read what I wrote? The server is not booting, it has nothing to do with the network configuration. And why the fuck, would I name an interface ens81, I would rather jump from the next bridge instead.

This worked for you? I got a machine using this way, still stuck on boot. It boots fine within the VM, don't have an IPMI so I can't figure out why. The Logs are giving me nothing, so I suspect same error as before and this one is not fixing it.

We run the same hardware, Proxmox 6.x, today we had also a crash. Hetzner did offer to update the BIOS. Its not the first crash tho, will see how it goes.

Sorry for the late reply. The Ubuntu USN's are exactly my problem. The changelog will only appear 3-5 days later when Proxmox already has patched the kernel. Is there any way you could inform us prior, that a security update for the kernel is on the way?

Hey, Current method is, to watch the ubuntu update/security notifications and take actions when a security update which is relevant has been dropped. But the current method sucks balls. The current issue is, the latest Proxmox Kernel is from 15th February, while Ubuntu dropped notifications 3...

Well, everything worked fine, until I restarted to many nodes at the same time. Why should that be tinc's fault? Everything worked before. I reboot a node, it fails back into not enough quonum state until i manually fix it by restarting the services. Well, these are based in 3 different data...

Hey, It seems like it was a bad timing, I always made sure I just reboot one node and wait until its back. Running these commands seems to fixed the issue: service pve-cluster restart systemctl restart corosync However, when I reboot a single node, the node runs into the same issue again...

Hey, I did configured a 3 Node cluster over tinc, about 10ms between the nodes. So after I rebooted the nodes to apply changes, the cluster broke up, into 3 nodes in Standalone mode. I attached screenshots, so you can take a look. Afterwards, I tried to check the status with: pvecm status It...

The Webinterface runs local as it should be, since I use a reverse proxy.

Any Update?

Here you go: I also tried to disable the spiceproxy since I dont need it but your guide to remove it from the autostart did not work anymore. Yeah and I took a look at the manuals but it does not really help.

No idea?

I missed to mention that I mean the current stable release.