BitMaster/Proxmox-VE-for-WHMCS
1
0
Fork 0
mirror of https://github.com/The-Network-Crew/Proxmox-VE-for-WHMCS.git synced 2026-04-02 02:28:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Clarify how to access noVNC (#167)

Browse Source
This commit is contained in:
Luke S Thompson
2025-10-18 12:11:43 +11:00
parent 63f56f8eea
commit 5432eaad80
2 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@@ -146,7 +146,11 @@ After forking the module, we considered how to improve security of Console Tunne
**noVNC has been overhauled. It isn't guaranteed, nor the project at all. :-)**
Here are some of the critical requirements for VNC tunnelling:
Once you have it configured, clicking noVNC in Client Area provides direct link - click it:
<img alt="Client Area is ready for you to click into noVNC terminal console" src="_images/zVNCprepared.png">
**Here are most of the critical requirements for VNC tunnelling:**
1. PVE must be at an IPv4 which has PTR the exact same as PVE's hostname.
2. You must use different Subdomains on the 1x Domain Name, for the cookie (anti-CSRF).