Leaderboard

@stormy, I'm glad to hear the e-invoicing feature will be a real value add for you. We are working with expert solution-providers in this space, so we're confident about delivering an easy to use and compliant solution with the broadest coverage. @andp97, Yes, by the end of the year in a pre-release version of WHMCS you will have access to this new feature. This bullet point actually describes two significant features which we're very excited about: 1. A RESTful API which provides access to the product catalogue and shopping cart logic. This will provide a suite of new endpoints to get product catalogue information, add, manipulate and get information about items in the cart (including price breakdowns and totals) and much more, all without touching the cart.php file or PHP session data. This means that power users could create their own highly-bespoke frontends whilst WHMCS handles the maths in the background, before seamlessly passing visitors to the checkout page to complete payment. 2. A brand new thin client powered by the aforementioned new API capabilities, providing a thoroughly modern purchase experience based on Vue.js. I've attached a sneak peak below. The new BuyFlow is a compiled Single-page application, meaning the layout isn't manipulated through templates, but you will be able to customise the colours to match your theme through a custom.css overrides file. The shopping cart as it exists today (cart.php and order form templates) isn't going away and will still be available if you'd like to stay with the familiar experience. Stay tuned to our blog and socials over the coming weeks for more information!

Another year another price increase for all WHMCS licenses. The question is has there been any updates to the software that justify the rising costs? The only change I've seen this year that was actually welcome was ironically a feature that existed but was removed. That being the ability to directly change client passwords. I can't think of anything else from memory. Anyone else?

Greetings, I have an older WHMCS installation (7.8.3). It is one of three owned licenses I purchased long ago. I wasn't too happy about taking the shaft due to the semi-recent changes in WHMCS subscriptions and pricing. So, I'd like to stretch this free interim out as long as possible, frankly. Meanwhile, it is past time to update MariaDB 10.2 on the server which currently works well with my 7.8.3 installation. Any advice here would be much appreciated. Will MariaDB 10.5 or 10.6 work with WHMCS 7.8.3 (and PHP 7.3). Thank you!

It's the same for every single WebPros product. Also cPanel, Plesk, SolusVM, Comet Backup, etc. etc. etc. All suffer from another (= yearly) price hike. Plesk seems to be the worsed off.... At this rate, it won't take long for WebPros to lose real customers... Ah well. Then WebPros will be sold (again) to a different investment group and prices will increase even more. Mark my words (unfortunately).

Thanks for opening a new thread, I had posted in the 2025 one. In my case, they will be extracting an extra $25/mo in exchange for absolutely nothing. The email is hilariou,s though: "We understand any change in pricing directly affects your business, which we do not take lightly." HOWEVER, if they succeed in doing the European E-invoicing right, which I highly doubt, then the price increase would be worth it. The problem is - can we trust WHMCS with something that can get you us legal and financial trouble?

Well, there we go again!!! https://assets.whmcs.com/customer-licensing-guide-2026.pdf In my case, they will be extracting an extra $25/mo in exchange for absolutely nothing. The email is hilariou,s though: "We understand any change in pricing directly affects your business, which we do not take lightly."

Your idea is technically doable in WHMCS, but there are some important fiscal and accounting issues to be aware of. The main challenge is that the money would come from someone who is not your client, while the credit is assigned to a third party (your actual client). This creates a mismatch between the payment and the service, meaning you would legally need to issue a receipt or invoice to the donor even though the benefit goes to someone else. On top of that, VAT and taxes can get tricky. If the donation is treated as payment for a service, VAT normally applies, but calling it a "pure donation" isn't straightforward, since the money is effectively being used to pay for another person's services. And when your client eventually uses the credit to pay for their server, that counts as a separate transaction requiring its own invoice, which could create accounting confusion or even potential tax issues (double taxation) if not handled carefully. So, while WHMCS can handle the technical side, the real challenge is making sure this setup is compliant from a fiscal perspective. That being said, personally I would avoid playing with real money. Instead I'd create an alternative currency (credits, tokens or coins) that donors purchase and for which you issue an invoice. The beneficiary who receives the donation can then use those tokens at payment time to reduce the total of an invoice, for example by redeeming a discount coupon that adds a negative line on the invoice. That way you avoid the mismatch of receiving money from one party and assigning credit to another, and you eliminate the risk of double invoicing or double VAT payments.

Hello, I have a dedicated Hetzner server, WHMCS cannot connect to the server, it gives this message, but these ports are open on the host, and Hetzner also says that we did not close the port and it is open, but it still does not connect. FAILED: Could not connect to Virtualizor. Please make sure that all Ports from 4081 to 4085 are open on your WHMCS Server or please check the server details entered are as displayed on Admin Panel >> Configuration >> Server Info.

Il Ballot SC-081v3 è una proposta dello CA/Browser Forum che riduce la durata massima dei certificati SSL/TLS, passando da un periodo di validità fino a 3 anni a un massimo di 12 mesi. Gradualmente verranno introdotti periodi di validità più brevi. Questo cambiamento impatta direttamente la gestione dei certificati e la sicurezza dei siti web. Perché il cambiamento? Migliore protezione da compromissioni Aggiornamenti crittografici più veloci Allineamento agli standard del settore Prima vs Dopo SC-081v3: Validità certificato: da fino a 3 anni → 12 mesi Sicurezza: buona → maggiore Rinnovi: meno frequenti → annuali obbligatori Gestione: semplice → automatizzata consigliata Roadmap rapida: 1️⃣ Q4 2025: emissione certificati 12 mesi 2️⃣ Q1 2026: aggiornamento software gestione SSL 3️⃣ Q2 2026: tutti i nuovi certificati conformi WHMCS già gestisce riemissione e distribuzione automatica dei certificati SSL a fine ciclo, normalmente ogni 12 mesi, supportando certificati fino a 3 anni. Grazie alla collaborazione con Digicert, il team introdurrà le modifiche necessarie per rispettare i periodi di validità più brevi ben prima che diventino obbligatori. 💡 MarketConnect continua a offrire totale automatismo e facilità di gestione, aggiornandosi proattivamente agli standard industriali e garantendo ai clienti sicurezza e tranquillità senza interruzioni.

We have identified some bugs in the WHMCS (Current version 8.12) client and Admin areas for various users in differnt time periods. The following are some of the examples. 1) A product is active but its expiry date is wrong. Wrong: Expiry date - 1969 Actual: Expiry date - 2026 2) A product is active but its due date is wrong. Wrong: Due date 11/30/-0001 Actual: Due date 11/30/2025 3) A customer is Unpaid but his account status displaying as Active. Wrong: Status-Active Actual: Status-inactive

Hi @venkat.j, The current latest version is 8.13. This behaviour suggests the dates were set to 00/00/0000, either by an admin (in which case there should be an entry in the client's Log tab) or by a rogue after-market module (in which case there probably wouldn't). You can edit the date fields to set the actual dates and click Save Changes. The correct dates will be stored.

Will need to take your word for it, since there's no way for us to substantiate that. I've personally never heard anyone state they'd like to hand over control of billing in WHMCS, but my circle is smaller. A further note, up 63% is a relative term. If no one wanted it, but x number of users now do, the vague starting point allows for some "fudge room" in gauging increase of interest.

can you maybe release an update to 8.13 to add a tool similar to the PHP compatibility tool that shows what files use these old components and won't be compatible? it'll help hosts like us that rely in multiple vendors plugins understand who we need to reach out too to ensure they're getting WHMCS v9 ready.

I Need to.. any whmcs developer ? Thank you

@sajibdesigns You need to select a Registrar from the dropdown before clicking accept order

Yep WebPros is toxic to the industry. Just a company looking to milk as much as they can out of the industry with no regard for their products or clients. Back in the early days of WHMCS for me. 2009 I used to have so much passion for the software. Would always be excited to test new versions in depth. Those times are long done sadly.

Toda vez que atualizo o meu WHMCS alguma parte de tradução parece andar para trás requerendo novas intervenções para ajustar traduções que já estavam corretas. Sei que as traduções adicionais devem ser aplicadas na pasta de tradução customizada e frequentemente aplico essas traduções ao arquivo, principalmente para o que aparece na interface dos clientes, mas a WHMCS não tem dado nenhuma atenção as traduções, minha sensação é de que a empresa já não se importa mais em nada com as parte de multi línguas do serviço.