Recent content by JaXnPrivate

  1. J

    VNC Shell über API unverschlüsselt starten.

    Ich habe für ESX auch eine Extension mit interactive VNC Shell, sieht halt blöd aus, wenn ProxMox dieses Feature nicht hat. Bei bspw. Docker und Plain SSH Maschinen, lässt sich auch ein Terminal bedienen...
  2. J

    VNC Shell über API unverschlüsselt starten.

    Für den Administrator der Verwaltungsoberfläche. Siehe: https://forum.proxmox.com/threads/proxmox-cli-api-vnc-port-not-open.142467/
  3. J

    VNC Shell über API unverschlüsselt starten.

    Um die Hypervisor Console Remote einbinden zu können...
  4. J

    VNC Shell über API unverschlüsselt starten.

    Hallo, wenn ich eine Shell per API anfrage ist diese über VenCrypt verschlüsselt. Mein WebSocket zu VNC Proxy bietet aber keinerleie möglichkeiten dieses Protokol zu entschlüsseln. Wenn ich mir anschaue wie ProxMox die Shell selbst startet ist mir ein ``-notls`` Argument aufgefallen. Wenn ich...
  5. J

    vncshell / termproxy funktionieren nicht.

    Egal ob ich eine VNC Shell vom Node per API oder per CLI aufrufe Sie timet aus bevor ich ein Ticket erhalte. Das ganze habe ich auf zwei unterschiedlichen Installationen getestet (ProxMox 8.1.3 und 8.1.4). Ich kann lediglich keine VNC Proxy für Qemu Container anfragen. root@host1 ~ # pvesh...
  6. J

    NoVNC access to VM or containers

    Everything that is written here in the forum about the VNC proxy is very unclear. The fact is that with vncwebsocket only a forwarding header is "activated". This means that the PVECookie must be included... But no 0815 user should receive it, that's why I simply wrote a reverse proxy in...
  7. J

    ProxMox CLI/API (VNC Port not open)

    Everything that is written here in the forum about the VNC proxy is very unclear. The fact is that with vncwebsocket only a forwarding header is "activated". This means that the PVECookie must be included... But no 0815 user should receive it, that's why I simply wrote a reverse proxy in...
  8. J

    ProxMox CLI/API (VNC Port not open)

    I checked the syslog and the session seems to time out shortly after creation. I don't know if this is normal (security based) or maybe the proxy could not be started, I can access it via Vanilla VNC if I am fast, only VNC Websocket just doesn't work. 2024-02-29T16:07:35.528888+01:00...
  9. J

    NoVNC access to VM or containers

    I started a project years ago and it worked. At the moment I am of the opinion that the ProxMox API gives me a port, but this is only open for a very short time. (max. 5-10 Seconds) Of course there is no error message... https://forum.proxmox.com/threads/proxmox-cli-api-vnc-port-not-open.142467/
  10. J

    NoVNC access to VM or containers

    Hey, have you found a solution?
  11. J

    ProxMox CLI/API (VNC Port not open)

    If I first request a VNC proxy and then a WebSocket via the Proxmox API, regardless of whether JSON or CLI, the port is not online/open on the server. Is there anything I need to be aware of with Creation, or can I debug it somehow? pvesh create /nodes/homeserver/qemu/100/vncproxy -websocket...
  12. J

    I'm still alive :P

    I'm still alive :P

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!