WHMCS.Community
-
WHMCS Beta Program
-
- 24
- posts
-
-
WHMCS.Community
-
Using WHMCS
-
- 13.1k
- posts
-
- 6.5k
- posts
-
- 6.1k
- posts
-
- 96.4k
- posts
-
- 28.6k
- posts
-
- 855
- posts
-
-
WHMCS Showcase
-
Developing & Extending WHMCS
-
Third Party Add-ons
A place to discuss third party modules, add-ons and extensions for the WHMCS platform.
- 18.7k
- posts
-
- 22.9k
- posts
-
- 59.1k
- posts
-
- 636
- posts
-
- 183
- posts
-
-
Community Competitions
-
- 625
- posts
-
- No posts here yet
-
-
General Discussions
-
- 40.1k
- posts
-
-
General Feedback & Assistance
-
- 8.7k
- posts
-
- 6
- posts
-
-
Club Forums
-
- No posts here yet
-
- 51
- posts
-
- 149
- posts
-
- 17
- posts
-
- 523
- posts
-
- 494
- posts
-
- 108
- posts
-
- No posts here yet
-
- 69
- posts
-
- 90
- posts
-
- 6
- posts
-
- 7
- posts
-
- 5
- posts
-
- No posts here yet
-
- 29
- posts
-
- No posts here yet
-
- 30
- posts
-
- 298
- posts
-
- 20
- posts
-
- 22
- posts
-
-
Member Statistics
116330
Total Members11199
Most Online
-
Community Statistics
82k
Total Topics377.4k
Total Posts -
Who's Online 2 Members, 0 Anonymous, 3470 Guests (See full list)
-
Popular Contributors
-
1
-
2
-
3
-
4
-
5
-
-
Our picks
-
![[From the Blog] WHMCS 9.1 Is Now Available](//storage.whmcs.community/monthly_2026_10/whmcs91.png.1bfe575deb67063d976fa5af8b0156ff.png)
[From the Blog] WHMCS 9.1 Is Now Available
WHMCS Community posted a topic in News, Announcements & Blogs from WHMCS,
WHMCS 9.1 is here! The latest release is now available and supported for use in production environments, bringing new ways to manage billing, simplify routine maintenance, and build more flexible customer experiences. Whether you want greater control over invoice handling, an easier way to get started with MarketConnect, or less manual work keeping your installation up to date, WHMCS 9.1 has something for you. The release also introduces PHP 8.4 support and expands the possibilities for...View the full blog post-
0
Reputation Points
- 0 replies
Picked By
WHMCS John, -
-
![[From the Blog] WHMCS 9.1 Beta Now Available](//storage.whmcs.community/monthly_2026_10/whmcsheader91beta.png.edbcd64ce9f791b06baed31a5b6fcc7d.png)
[From the Blog] WHMCS 9.1 Beta Now Available
WHMCS Community posted a topic in News, Announcements & Blogs from WHMCS,
The WHMCS 9.1 Beta is now available for testing on staging environments. Whether you're testing your own integrations and templates, running it on staging to see how it affects your day-to-day work, or just want to help us catch issues before general availability, here's what's changed. Please don't run this build in production. Get it on the WHMCS 9.1 Beta landing page. WHMCS 9.1 Beta includes the following new functionality and enhancements: Credit and Debit Notes, with Invoice Immutability...View the full blog post-
0
Reputation Points
- 0 replies
Picked By
WHMCS John, -
-
![[From the Blog] WHMCS 9.0 Release Candidate OUT NOW](//storage.whmcs.community/monthly_2025_12/whmcs9-rc-blog-fin.png.c46266bad8fb542c4a5855754481b67c.png)
[From the Blog] WHMCS 9.0 Release Candidate OUT NOW
WHMCS Community posted a topic in News, Announcements & Blogs from WHMCS,
We're excited to announce the availability of the WHMCS 9.0 Release Candidate!-
1
Reputation Points
- 0 replies
Picked By
WHMCS John, -
-
-
Topics
-
-
Posts
-
By Eduardo G. · Posted
So 8.13 and 9.0 are both LTS and they both get EOL at the same time? 9.0 is not getting even a full year, quere is the "long" in the LTS? 😞 1 year 7 months LTS for 8.13 11 monts LTS for 9.0 It makes no sense to label all versions as LTS and then EOLing them all. Once again, I'm very disappointed -
@WHMCS Carlos Nope, exactly in the same position we were before. Not really sure why a company that puts out billing related software can't understand that ending support at year end is just not a good idea. So, for us, we either need to upgrade in November, get a management exception to upgrade during year end or risk not updating (not really an option). The path forward is pretty mirky also. 8.13/9.0 are both labeled at LTS with a 2026-12-31 date. What is the next LTS release going to be?
-
It's because WHMCS developers do not wnat to do nothing after plesk changed it's API. Add this in Plesk in the Panel.ini editor as workaround: [api] oldVersionsSupported = true -
By WHMCS Carlos · Posted
We have extended 8.13 support to 31 December 2026, and the email notice went out to all customers today. I hope this takes some of the pressure off the upgrade. I understand this won't be ideal for everyone. To be clear on what the date means: your 8.13.x install keeps working after 31 December. We simply won't release any further patches for it, including security fixes. Going forward, every supported version will have its EOL date published. No more TBD. -
By jessasaurus · Posted
from the list accounts response i see the following Array ( [@attributes] => Array ( [version] => 1.6.9.1 ) [webspace] => SimpleXMLElement Object ( [get] => SimpleXMLElement Object ( [result] => Array ( [0] => SimpleXMLElement Object ( [status] => ok [filter-id] => 1 [id] => 1 [data] => SimpleXMLElement Object ( [hosting] => SimpleXMLElement Object ( [vrt_hst] => SimpleXMLElement Object ( [property] => Array ( [0] => SimpleXMLElement Object ( [name] => seo-redirect [value] => none ) [1] => SimpleXMLElement Object ( [name] => ftp_login and more like that in it wont send all of it as it has usernames and password in it as shown in the images i posted plesk is fully up to date!!! (Plesk Obsidian 18.0.81 Update #6) and running WHMCS version 9.0.9 this is the requests WHMCS is sending for list accounts <?xml version="1.0" encoding="UTF-8"?><packet version="1.6.9.1"><!-- Copyright 1999-2016. Parallels IP Holdings GmbH. --> <server> <get_protos/> </server> </packet> <?xml version="1.0" encoding="UTF-8"?><packet version="1.6.9.1"><webspace> <get> <filter/> <dataset> <hosting/> <subscriptions/> </dataset> </get> </webspace> </packet> -
By Waqas Ahmed Waseer · Posted
One thing in your output matters more than the matching: the left-hand (Module/Server) side ends with "No Records Found". That means the sync didn't get a single account back from Plesk, so this isn't a username or domain mismatch. WHMCS is getting an empty list, and Test Connection succeeding only proves the login works, not that the account list call returns anything. Before anything else, don't tick Import/Sync on those rows and continue. For services that exist in WHMCS but not "on the server", the sync terminates them in WHMCS and sets them to Terminated, so you'd mark 10 live customers as terminated. What I'd check, in this order: Configuration > System Logs > Module Log: enable logging, run the sync again, then open the Plesk entries. Look at the response to the account/subscription listing request. If it's an XML error (permission denied, protocol version, parse error), that's your answer. If it's a valid response with no results, go to step 2. On the Plesk box, run plesk bin subscription --list and confirm these domains are really subscriptions on that server, not domains added under one subscription (additional domains don't show up as separate accounts). Make sure the hostname/IP on the WHMCS server record is this Plesk server. If it points at an old or different server with the same admin login, Test Connection passes and the list is still empty. The Module Log request URL shows exactly where it's going. Check the WHMCS and Plesk versions. The current module needs Plesk Onyx 17.8 or Obsidian 18.0+. If the Module Log shows a clean response that does list the subscriptions and the left side is still empty, that's a module bug. Open a ticket with WHMCS and attach the log entry with the credentials and domains redacted. -
-
By Waqas Ahmed Waseer · Posted
What you're seeing is the "Domain Expiry Status Update" behaviour in v9. When a domain expires with its renewal invoice still unpaid, the cron cancels that invoice (or just the domain line if the invoice has other items on it) and issues a credit note for it. So by the time the client paid a week later, WHMCS had already written the renewal off, and you end up with a credit note plus a payment for the same thing. You can't delete a credit note, but you can clean it up: 1. Open the credit note (Billing > Credit and Debit Notes, or the Reference column in the invoice Ledger). If it still has a remaining balance, close it. Per the docs, closing a credit note with a balance creates an offsetting debit note, so it stops being picked up by the next invoice. 2. If it's already been applied to the next invoice, remove the applied credit from that invoice. That generates a debit note for the amount and puts the balance back where it should be. 3. Check that the domain itself actually renewed and the expiry date moved. When the payment lands after the cancellation, I wouldn't assume the renewal went through on its own. If you'd rather WHMCS stopped creating billing notes altogether, the switch is Configuration > System Settings > General Settings > Invoices > Invoice Immutability. The option "Immutability and billing note generation disabled" goes back to the old behaviour: no credit/debit notes, cancellations and overpayments go straight to the client's credit balance. Before you change it, check with your accountant whether you need credit notes for tax reasons (EU/UK VAT usually does). It also won't change notes that already exist. Also worth updating to 9.1 if you're on 9.0.x. The 9.1 release notes list several fixes in this area, such as cancelling an invoice now returning partial payments and applied credit to the client's balance, and removing credit no longer flipping a paid invoice to Refunded. Docs I went by: Credit and Debit Notes and Configure Invoice Immutability, both under docs.whmcs.com/9-1/billing-and-invoicing/. -
Another addon that should be standard feature - and was even hinted about a while back by WHMCS with the release of 7.8 in 2019 when it started to support multiple saved cards. -
By Waqas Ahmed Waseer · Posted
Thanks for checking the logs, that narrows it down a lot. If both rows come from stripe_dynamic.php and that's the only endpoint, it isn't leftover config on your side. The module is recording the decline from the charge attempt and then recording the charge.failed webhook as a second event for the same attempt. I'd still put that in a ticket with WHMCS, with the two gateway log entries for one invoice attached, so it gets fixed in the module rather than everyone working around it. On dropping that event: whether it's safe depends on what you take through Stripe. For card payments that WHMCS attempts itself (the cron capture, or a client clicking Pay Now), the decline comes back in the API response right away, so the webhook only repeats what WHMCS already knows. Where the webhook earns its keep is a payment that fails later, after the charge call has already returned, like an ACH or SEPA debit that bounces a few days on. Without it, as far as I can tell, that invoice would just stay unpaid with no failure email and nothing in the gateway log, and you'd only spot it in the Stripe dashboard. So if you're cards only, removing it is a reasonable stopgap. Run one test with Stripe's generic decline test card (4000 0000 0000 0002) and one successful payment to confirm you get one failed row, one email, and paid invoices still go through. If you offer bank debits, I'd keep the event and stop the duplicate email with an EmailPreSend hook instead. Either way, make a note to add the event back once WHMCS ships a fix.
-
![[From the Blog] WHMCS 9.1 Is Now Available](http://storage.whmcs.community/monthly_2026_10/whmcs91.png.1bfe575deb67063d976fa5af8b0156ff.png)
![[From the Blog] WHMCS 9.1 Beta Now Available](http://storage.whmcs.community/monthly_2026_10/whmcsheader91beta.png.edbcd64ce9f791b06baed31a5b6fcc7d.png)
![[From the Blog] WHMCS 9.0 Release Candidate OUT NOW](http://storage.whmcs.community/monthly_2025_12/whmcs9-rc-blog-fin.png.c46266bad8fb542c4a5855754481b67c.png)
