Before you begin the process of connecting the console to the server through a proxy, you need to download the proxy application file.
The file can be found under the following link after you have logged in to your ModulesGarden account.

It is advised to use the KVM virtualization type.

Warning! The used VPS may NOT have any services running, such as: PHP, WebServer (e.g. apache, nginx) or MySQL server.

ping modulesgarden.com

If everything is fine, ensure that basic server security settings have been established.
You may turn off login with a password and turn on login with a key, change the SSH port, set up firewalls, etc.

https://docs.docker.com/engine/install/
https://docs.docker.com/compose/install/

Then unzip the files.

cd /root/proxmox-proxy  

Note that the exact directory depends on the previous step where you uploaded the files.

Then open the just renamed '.env' file and provide a random set of signs to create the database and root passwords: DB_PASSWORD and MYSQL_ROOT_PASSWORD
These data will be automatically used when creating the database.

docker-compose up --build -d

docker exec -it proxyphp bash 

and run the installation script:

php -q /var/www/html/installer.php install 

When ready, find the API Key and keep it safe, you will need it later on when pasting the data into the module addon, see point 12 for details.

ip a

Note: Remember to check the IP address in your virtual machine, not in the proxyphp container.

Move to 'Addons' → 'Proxmox Addon' → 'Settings'. At the bottom you will find section 'Console Proxy' with 'Host' and 'API Key' fields.
Note that the Host field may include either an IP address or a domain. It is extremely important that you paste here the same data as the ones used in the SSL certificate.
The below screen shows an example with an IP address which is not the only correct possible option here.

Provide the necessary data and confirm the changes.

Remember to replace {vmip} with a valid virtual machine IP address, for example: https://192.168.8.113:8443/
When you see {"errors":["Invalid API Endpoint"]} it means that the server correctly responds.

• move to the '/root/proxmox-proxy catalog (the directory may differ depending on your setup)
• replace the nginx/localhost.crt and nginx/localhost.key files
• run the following command:

docker-compose up --build -d

When a new version of the proxmox proxy application is released, follow these steps to complete the update process:

• Download the updated files and upload them to your WHMCS.
• Execute the following commands sequentially:

 docker-compose pull
 docker-compose down
 docker-compose up -d --build

The Proxmox proxy is an application developed by ModulesGarden, relying on Docker containers provided by third-party vendors.
To ensure your proxy stays updated with the latest Docker images, we recommend executing the following commands occasionally:

 docker-compose pull
 docker-compose down
 docker-compose up -d --build

Important: In case of container update, there is no need to configure anything in the proxmox proxy application itself.

1. The module (such as Proxmox VE VPS For WHMCS or Proxmox VE Cloud VPS For WHMCS) connects to the Proxmox server to generate a ticket, granting access to the Proxmox panel.
2. The ticket is then forwarded to the Proxmox Proxy application, which in turn returns a token
3. The user uses the token to establish a connection with the Proxmox Proxy.
4. Finally, the Proxmox Proxy utilizes the provided token, along with the associated data (such as the server's IP address and the ticket), to establish a connection with the Proxmox server.

• Restrict access to the Proxmox servers by permitting connections only from WHMCS and the proxy application itself, blocking all other connections.
• Ensure that the server hosting the Proxmox proxy restricts remote access to ports exclusively to 8443.