chore: release v1.3.0

- VERSION: 1.2.0 → 1.3.0
- CHANGELOG: add v1.3.0 section (VNC & Terminal fixes)
- README: update version badge to 1.3.0
- WIKI: bump version header, expand Console section (VNC/xterm.js),
  update VNC troubleshooting section
This commit is contained in:
markmorado
2026-03-27 21:36:21 +01:00
parent 29f1255705
commit abeb8d53a3
4 changed files with 41 additions and 14 deletions

View File

@@ -4,6 +4,18 @@ All notable changes to PVEmanager will be documented in this file.
---
## [v1.3.0] - 2026-03-27
### 🖥️ Console — VNC & Terminal Fixes
- **VNC «Connection closed» fixed** — `RFBClass` (noVNC) now receives the WebSocket URL string directly instead of a pre-opened `WebSocket` object; the `onFirstMessage` hack that broke the RFB handshake before the first frame is fully removed from both `virtual_machines.html` and `instance_detail.html`
- **VNCAuth fixed for QEMU** — `vncproxy` is now called with `"generate-password": 1`; the returned 8-character DES key is passed to noVNC as the VNC password; falls back to `ticket` when `password` is absent (Proxmox 9.x NoAuth mode)
- **LXC `vncproxy` 500 fixed** — LXC `vncproxy` API does not accept `generate-password`; the parameter is omitted for LXC, which uses `ticket` as the VNC password
- **LXC context menu opens xterm.js terminal** — the right-click context menu in the VM list now shows **Terminal** for `lxc` type (calls `openTerminalConsole()`) and **VNC Console** for `qemu` type; previously all types used `openVNCConsole()`
- **Terminal modal added to VM list page** — `#terminalModal` with full xterm.js (FitAddon, WebLinksAddon, Dracula theme) added to `virtual_machines.html`; reuses existing backend endpoints `GET /api/{server_id}/container/{vmid}/terminal` and `WebSocket /proxmox/ws/terminal/{server_id}/{node}/{vmid}`
---
## [v1.2.0] - 2026-03-16
### 🐛 Bug Fix — Disk Resize Lock Conflict

View File

@@ -4,7 +4,7 @@
**Modern web panel for managing Proxmox servers, virtual machines and LXC containers**
[![Version](https://img.shields.io/badge/version-1.2.0-blue?style=flat-square)](CHANGELOG.md)
[![Version](https://img.shields.io/badge/version-1.3.0-blue?style=flat-square)](CHANGELOG.md)
[![License](https://img.shields.io/badge/license-MIT-green?style=flat-square)](LICENSE)
[![Docker](https://img.shields.io/badge/docker-ready-2496ED?style=flat-square&logo=docker&logoColor=white)](compose.yml)
[![Python](https://img.shields.io/badge/python-3.12-3776AB?style=flat-square&logo=python&logoColor=white)](backend/)

View File

@@ -1 +1 @@
1.2.0
1.3.0

39
WIKI.md
View File

@@ -1,6 +1,6 @@
# 📖 PVEmanager - Documentation
> Complete guide for installation, configuration and usage of PVEmanager v1.2.0
> Complete guide for installation, configuration and usage of PVEmanager v1.3.0
---
@@ -460,12 +460,15 @@ Select multiple VMs/containers and perform mass actions:
See [Bulk Operations](#-bulk-operations) for more details.
### VNC Console
### Console (VNC / Terminal)
1. Open VM details
2. Click **Console** button
3. Console opens in new tab
4. Fullscreen mode supported
- **QEMU VMs** — VNC console via noVNC (in-browser graphical display).
1. Open VM details → click **Console**, or right-click VM in the list → **VNC Console**
2. Full keyboard and mouse passthrough; fullscreen supported
- **LXC Containers** — interactive shell via xterm.js terminal.
1. Open container details → click **Terminal**, or right-click container in the VM list → **Terminal**
2. Full PTY: tab completion, colours, Unicode, terminal resize on window resize
3. Uses the Proxmox `termproxy` WebSocket protocol (auth handshake + keepalive pings every 2 min)
### Configuration Changes
@@ -475,7 +478,7 @@ RAM: 512MB - 128GB
Disk: Increase size (decrease not possible)
```
> **Note (v1.2.0):** Disk resize is fully asynchronous. The panel waits for the Proxmox resize task to complete before starting the VM, preventing `lock file timeout` errors that occurred when the VM was started immediately after a resize request.
> **Note (v1.2.0+):** Disk resize is fully asynchronous. The panel waits for the Proxmox resize task to complete before starting the VM, preventing `lock file timeout` errors that occurred when the VM was started immediately after a resize request.
### High Availability (HA)
@@ -1570,13 +1573,25 @@ docker compose exec app env | grep SMTP
- SMTP server may be unreachable
- Timeout is 10 seconds
### VNC Issues
### VNC / Terminal Issues
#### "VNC connection failed"
#### "VNC connection failed" (QEMU)
- Check that VM is running
- Check that VNC is enabled in Proxmox
- Try restarting VM
- Check that the VM is running
- Ensure VNC is enabled in the Proxmox node settings
- Try restarting the VM
- Verify the Proxmox API user has `VM.Console` privilege
#### "Connection closed" immediately on VNC open
- This was a known bug fixed in v1.3.0 (noVNC received a pre-opened WebSocket instead of URL)
- Upgrade to v1.3.0 or later
#### Terminal not connecting (LXC)
- Check that the container is **running** (not stopped or paused)
- Verify the Proxmox API user has `VM.Console` privilege on the node
- Check logs: `docker compose logs app --tail 50`
### Command Issues