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

Better para spacing

Luke S Thompson
2023-06-19 20:49:11 +10:00
parent a01e4d7b3a
commit 84daeec655
1 changed files with 12 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
Home.md

@@ -11,7 +11,9 @@ This wiki aims to explain some of the more specific requirements to get it worki
5. Proxmox Server IPv4 needs FCrDNS for Cookie
6. WHMCS Service ID (DB primary key) > 100
If you think this may be overkill, please consider factors such as public-to-private (WHMCS-to-Proxmox) integration and the inherent risks it carries, as well as Cyber Security factors such as anti-CSRF limitations (same-domain services due to same-domain cookie) and upstream limitations (Proxmox VM ID cannot be < 100 as they are reserved). The list goes on. We have tried to ensure a least-privilege approach with how the module has been overhauled.
Please consider factors such as public-to-private (WHMCS-to-Proxmox) integration and the inherent risks it carries, as well as Cyber Security factors such as anti-CSRF limitations (same-domain services due to same-domain cookie) and upstream limitations.
We have tried to ensure a least-privilege approach with how the module has been overhauled.
## 1. System Environment must be up-to-date & well set-up
@@ -37,12 +39,18 @@ Once everything is configured, you also need to follow the instructions below to
## 4. WHMCS & Proxmox must be Subdomains of 1x Domain
Due to anti-CSRF limitations, cookies can only be issued to subdomains of a domain at the most. This means that your WHMCS and Proxmox VE must be subdomains of the same domain name. This only applies if you wish for noVNC access to be possible, as to do this we must set a Proxmox Access Ticket in a browser cookie, and also then send the VNC Ticket as a parameter to the Proxmox API. As WHMCS originates the cookie placement request, it does not have scope to do this inter-domain.
Due to anti-CSRF limitations, cookies can only be issued to subdomains of a domain at the most. This means that your WHMCS and Proxmox VE must be subdomains of the same domain name. This only applies if you wish for noVNC access to be possible, as to do this we must set a Proxmox Access Ticket in a browser cookie, and also then send the VNC Ticket as a parameter to the Proxmox API.
As WHMCS originates the cookie placement request, it does not have scope to do this inter-domain.
## 5. Proxmox Server IPv4 needs FCrDNS for Cookie
In order to obtain the hostname of the Proxmox Server we perform a PTR/rDNS lookup on its IPv4 address. Make sure it's correctly configured so there are no problems using the VNC service via the Client Area. If you don't wish to leverage the functionality, you should leave the VNC Secret configuration blank so it is unable to attempt any connection requests.
In order to obtain the hostname of the Proxmox Server we perform a PTR/rDNS lookup on its IPv4 address. Make sure it's correctly configured so there are no problems using the VNC service via the Client Area.
If you don't wish to leverage the functionality, you should leave the VNC Secret configuration blank so it is unable to attempt any connection requests.
## 6. WHMCS Service ID (DB primary key) > 100
If you have not sold/given enough WHMCS Services for the Primary Key in your tblhosting table to be >100 then you will not have success trying to do anything with those services over the Proxmox API, as they reserve 0-100 for internal purposes to protect the system. So you will have to create dummy/fake/cancelled services to make up the difference, and then you will be up and away.
If you have not sold/given enough WHMCS Services for the Primary Key in your tblhosting table to be >100 then you will not have success trying to do anything with those services over the Proxmox API, as they reserve 0-100 for internal purposes to protect the system.
You'd have to create dummy/fake/cancelled services to make up the difference, and then you will be sorted.