Salvation, a free and open-source solution for beloved PVE! If you love it, REVIEW & SHARE IT!
Repo: https://github.com/The-Network-Crew/Proxmox-VE-for-WHMCS/
Please read the entire README.md file before getting started with Proxmox VE for WHMCS. Thanks!
We're pretty much done overhauling the Module to suit our needs at The Network Crew Pty Ltd & Merlot Digital.
Please review the module! https://marketplace.whmcs.com/product/6935-proxmox-ve-for-whmcs#reviews
If you want it to remain free and fabulous, it could use a moment of your time in reviewing it. Thanks!
New Biz: Fresh Installations/Businesses using WHMCS need to take note of the Service ID < 100 case.
SID >100: The WHMCS Service ID requirement is CRITICAL, as Proxmox reserves VMIDs <100 (system).
If you don't have enough services (of any status) in WHMCS (DB: tblhosting.id), create enough dummy/test entries to reach Service ID 101+. Else you're likely to see an error which explains this: HTTP/1.1 400 Parameter verification failed. (invalid format - value does not look like a valid VM ID)
DON'T SKIP ANY PART OF THIS README.md - please don't raise pointless Issues - thank you!
Firstly, you need to upload, activate and make the WHMCS Module available to Administrators.
Once you've done all of that, in order to get the module working properly, you need to:
After forking the module, we considered how to improve security of Console Tunneling via WHMCS. We decided to implement a routing method which uses a secondary user in Proxmox VE with very restrictive permissions. This is due to be re-built again to further enhance security.
noVNC has been overhauled. It isn't guaranteed, nor the project at all. :-)
novnc_router.php - ideally we/someone will optimise this to better cater to all formats.You must have a root account to use the Module at all. Configured via WHMCS > Servers.
Additionally, to improve security, for VNC you must also have a Restricted User. Configured in the Module.
Do NOT set less restrictive permissions. The above is designed for hypervisor security.
These steps explain the unique requirements per-option.
Custom Fields: Values need to go in Name & Select Options.
Unsure? Consult the zMANUAL-PVE4.pdf legacy manual file.
Firstly, create the Template in PVE. You need its unique PVE ID.
Use that ID in the Custom Field KVMTemplate, as in ID|Name.
Note:
Nameis what's displayed in the WHMCS Client Area.
Firstly, create the Plan in WHMCS Module. Then, WHMCS Config > Services.
Under the Service, you need to add a Custom Field
ISOwith the full location.
Firstly, store the Template in PVE. You need its unique File Name.
Use that full file name in the Custom Field
Template, as in:<br>ubuntu-99.99-standard_amd64.tar.gz|Ubuntu 99
Then make a 2nd Custom Field Password for the CT's root user.
Please make sure you create an IP Pool with sufficient scope/size to be able to deploy addresses within it to your guest VMs and CTs. Else it won't be able to create a Service for you.
Private IPs for PVE Hosts: Note that VNC may be problematic without work due to the strict requirements introduced in Proxmox v8.0 (strict same-site attribute).
Per #33 there's SLAAC/DHCP/off available (2x vNICs) (May 2024).
You can of course add different config via PVE/pvesh manually, if you need to specify a prefix.
There are new features deployed into Proxmox VE upstream in the v8 branch which are exciting and should be added to this module.
PVE Roadmap: https://pve.proxmox.com/wiki/Roadmap
This module has been overhauled and remains functionally-OK but not thoroughly tested nor reviewed.
Your support and assistance is always welcomed per the spirit of FOSS (Free Open-source Software)!
If you cannot accept this, do not download nor use the code. Complaints, nasty reviews, and similar behaviour is against the spirit of FOSS and will not be tolerated.
Be grateful & considerate - thank you!
Before raising a GitHub Issue, please check:
Help: Including logs, details, steps to reproduce, etc, please raise a GitHub Issue.
Logs: We work to ensure that Proxmox VE for WHMCS passes through error details to you.
error_log contentspveproxy etc)pvesh etc variants of failing callsThe more info/context you provide up-front, the quicker & easier it will be!
* Debug: Also enable Debug Logging in Proxmox VE for WHMCS > Settings, as needed.
Please note that this is FOSS and Support is not guaranteed at all.
If you don't read, listen or actively try, no help is given.
WHMCS Admin > Addon Modules > Proxmox VE for WHMCS > Support/Health shows updates.
You can download the new version and upload it over the top, then run any needed SQL ops.
Please consult the UPDATE-SQL.md file, open your WHMCS DB & run the statements. Then you're done.
If you'd like to contribute to the Module, please open a Pull on GitHub >> The-Network-Crew/Proxmox-VE-for-WHMCS
The original module was written in 2 months by @cybercoder for sale online in 2016, though didn't sell any copies so they kindly open-sourced it and removed the licensing requirement.
We would like to thank @cybercoder and @WaldperlachFabi for their original contributions and troubleshooting assistance respectively.
Thank you to psyborg® for the module's logo design! We love it.
FOSS is only possible thanks to dedicated individuals!
This module is licensed under the GNU General Public License (GPL) v3.0.
GPLv3: https://www.gnu.org/licenses/gpl-3.0.txt (by the Free Software Foundation)
The Network Crew Pty Ltd :: https://tnc.works
Merlot Digital :: https://merlot.digital
Browse issues, raise a new one: GitHub Issues
The best place to start if you need help with a specific product is to contact the developer. All WHMCS Marketplace developers have both a website and support URL listed.
x86-64-v2-AES (#58)
(*): SQL Note: There are new columns in 2 of the module tables, see SQL.md
Resell VPS & Cloud Dedicated Products from Liquid Web
Automate the sale of VPS servers & give your clients the ability to completely manage their VPS server inside of WHMCS, using the industry leading SolusVM control panel.
Riven Lab @riven3908
GOOD
chairul anwar @chairul9768
I have managed to install this module even though there are lots of errors. but I have managed to fix it. I hope that the PROXMOX VE FOR WHMCS Free project will continue and get even better. and for developers keep the spirit
Thank You
Willi @willi7464
Hi colles Addon for WHMCS,
my Question Would the configurator from WHMCS also work if so what do I have to set.
Fabian Ruhl @fabian1776
No comment provided.
Andrei Kostas @8757
The module does not work correctly, too many errors, so do not be too happy that it is free.
Luke Thompson @luke3603
The current v1.1 release is a beta, and is the first step in resolving issues arising from the 7-year delta.
Owner@The Network Crew Pty Ltd (TNC)We have forked the module and continue to overhaul it. Version 1.2 will address many of the problems.
FOSS (Free Open-source Software) projects die out due to such abuse. You are only negatively contributing.
This is all explained on the repository. Due to your review, we have now added a Zero-tolerance Abuse line too.
Alexandre dos Santos @alexandre5881
Sorry, is free or not?
Step6: Enter license key which you obtained from www.moduleland.com, and save License.
This site are offline.
Thanks.
Luke Thompson @luke3603
Hi there Alexandre, thanks for your 5-star review!
Owner@The Network Crew Pty Ltd (TNC)The module is free, however the original Manual PDF files in the repository are outdated, and show the previous license steps.
Version 1.2 is due to be released in the next few days, it resolved many small bugs and issues in the 7 year delta.
Once you've made the update after its release, please let us know via GitHub Issues of problems.