All Activity

this issues already been sorted by updating WHMCS to verions 9.1.0 and with plesk updated to version 18.0.82 Update #2

@WHMCS Carlos I never saw this email. Did anyone else? Personally, I have no intention of getting trapped on 9.1 right now. Just a quick glance around this community tells me it still has too many bugs. Your beta period was what, 2 weeks at best? Before I could even download and install it, the GA was available.

@Michael Wilson the client-side part is covered in my reply just above (Nathan asked the same thing): cancelled invoices stay visible in the client area, the duplicate gets a new ID, and a "Replaces invoice #..." line in the Notes field heads off most of the tickets. On the recurring amount: WHMCS builds the renewal invoice from the Recurring Amount on the client's service, not from the product's current price. So changing the product pricing on its own doesn't touch existing services. Either edit the Recurring Amount on the service directly, or tick Auto Recalculate on Save on the service and save, which pulls the current product and configurable option pricing into it. The catch that usually trips people up is timing. If the next renewal invoice has already been generated (that depends on your Invoice Generation days setting under Automation Settings), updating the service won't change that invoice. It only affects invoices created after the change. So check the client's Invoices tab first: if the upcoming one already exists, fix it with the same duplicate, publish, cancel routine, and the corrected service amount takes care of everything after that.

@azzepis you're right, thanks for the link, I missed that one. It's in the Plesk Obsidian 18.0.82 release notes under Deprecated and Removed Items: 18.0.82 dropped support for XML API protocol versions older than 1.6.9.1, and the oldVersionsSupported option (in the api section of panel.ini, set to true) temporarily turns the old versions back on. Plesk itself calls that not secure and not recommended, so I'd only treat it as a stopgap. @jessasaurus that gives you a quick test. If your Plesk is on 18.0.82 or later, add that option, run the sync again and see whether the Analyse table fills in. If it does, some request in the sync is still going out with an older protocol version even though the listing response you pasted says 1.6.9.1, and that's worth adding to the WHMCS ticket along with the Module Log. Take the option back out once WHMCS ships a fix. If you're still on 18.0.81 (which is what you mentioned earlier), nothing was removed yet, so the setting won't change anything and the ticket is the way to go. Same caution as before: don't tick Import/Sync on any rows while the left side is empty.

@WHMCS Carlos I try very hard to say professional in these threads (and I don't reply a lot), but I really have to wonder what world the WHMCS management/development team lives in. The next LTS release needs to be out (for a while, so it's fully vetted, BEFORE the previous LTS is retired. LTS has no real meaning if you can't stay on a LTS release. This is pretty much exactly the opposite of what we want/need. WHMCS at it's heart is ordering/billing software. We want a very slow/stable with minimal changes (especially within the LTS track). To be honest, I can't really think of a single new feature in the last 3 - 5 years that WHMCS has put out that we have implemented. There is no way we would implement automated updates until it's been fully vetted (read that as in production for several years). The risks simply don't make sense. Simply put, we can't. From my understanding/community threads, 9.1 forces us to sign up with the WHMCS marketplace. We have compliance requirements and we need to know exactly what data is shared between our WHMCS install and the marketplace. We also need to know how this will work since we keep a development and production environment. We've had ticket RLB-418773 open since 1-Nov-2026 and have received any useful answers. This is also going to force us to do two major upgrades in a relatively short timeframe. This is a lot of work for our staff (testing, training etc.) as well as potentially frustrating to customers. WHMCS really needs to reconsider supporting 8.13 until there is a stable/vetted path to the next LTS version. WHMCS's sister company cPanel manages to support multiple versions at the same time and I have to believe their codebase is much more complex than WHMCS. My 2 cents

@WHMCS Carlos No further delays in lights of all recent comments ? Also, with the release of 9.2 in December, we are going to plan a move to a soon obsolete version, this is just chaotic. Easier from 9.1 but more work overall. With the new security paradigm of this era, it would be clearly appreciated to have a bit of cushion to proceed with the migration and possibly have us land on 9.2. I think we all understood it is due to migrate but the time brought is insufficient.

Don't miss chance to get upto 50% off on all WHMCS products. Here are the offers available during the sale: 20% OFF on monthly plans — Use code FESTIVE20 30% OFF on annual plans — Use code FESTIVE30 50% OFF on open-source code — Use code FESTIVE50

VueJS WHMCS One Step Checkout v2.4.1 – Now Compatible with WHMCS 9.1.0 Hi everyone, We've released VueJS WHMCS One Step Checkout v2.4.1, bringing full compatibility with the latest WHMCS 9.1.0. This release includes several important bug fixes, payment gateway improvements, and compatibility enhancements to ensure a smoother checkout experience. What's New in v2.4.1? Bug Fixes: Fixed an issue where invalid or non-existent gid or pid values in the URL caused the order form to get stuck on the loading screen. Users are now redirected to the order form homepage. Fixed an issue with alphabetic values provided for gid or pid in the URL query string. Fixed automatic provisioning issues when ordering cPanel products using the Stripe payment gateway. Resolved an issue affecting domain transfers. Fixed redirection issues triggered by AJAX requests from other modules containing gid, pid, and product group slug parameters. Improvements: Added compatibility with WHMCS 9.1.0. Added support for PHP 8.4 and ionCube Loader 15. Added compatibility with the latest Stripe Dynamic Payment Gateway (stripe_dynamic). Updated Ukrainian, Portuguese, and Brazilian Portuguese language files to follow WHMCS 9.x naming conventions. Improved mobile responsiveness for a better checkout experience across devices. Product Details Product: VueJS WHMCS One Step Checkout Latest Version: v2.4.1 Release Date: 04 November 2026 Product Page: https://whmcsglobalservices.com/custom-template/vue-one-step-checkout-orderform/ We recommend existing customers upgrade to v2.4.1 for the latest compatibility updates and bug fixes. Have questions or need assistance? Feel free to contact our support team.

With the release of WHMCS 9.1.0, we're pleased to announce that all our WHMCS themes, client area templates, admin themes, and order forms have been updated and are now compatible with the latest WHMCS version. Our latest releases also include PHP 8.4 and ionCube Loader 15 support, along with various improvements, bug fixes, and UI enhancements. Updated Themes & Templates HostX – v3.1.2 https://whmcsglobalservices.com/web-hosting-themes-templates/hostx/ CloudX – v1.1.2 https://whmcsglobalservices.com/web-hosting-themes-templates/cloudx/ ClientX – v3.3.3 https://whmcsglobalservices.com/clientarea-template/clientx/ TwentyX – v1.3.4 https://whmcsglobalservices.com/clientarea-template/twentyx/ AdminX – v1.1.3 https://whmcsglobalservices.com/web-hosting-admin-themes-templates/whmcs-adminx/ Updated Order Forms One Step Checkout (OPC) – v2.5.4 https://whmcsglobalservices.com/custom-template/one-step-checkout-whmcs-orderform-template/ VueJS WHMCS One Step Checkout – v2.4.1 https://whmcsglobalservices.com/custom-template/vue-one-step-checkout-orderform/ What's Included? Full compatibility with WHMCS 9.1.0. Support for PHP 8.4 and ionCube Loader 15. Updated language files following WHMCS 9.x naming conventions. Improved mobile responsiveness across themes and order forms. Various bug fixes, stability improvements, and compatibility enhancements. Demo: http://demo.whmcsglobalservices.com/ We recommend all existing customers update to the latest versions to ensure smooth operation with WHMCS 9.1.0. Have questions or need assistance with the updates? Feel free to reach out to our support team.

@DennisHermannsen Unattended Automatic Updates only apply updates for the version you are on that we have marked as safe to apply automatically: security fixes, bug fixes and small improvements, with nothing that requires changes to your hooks, themes or customisations. Anything that needs manual steps is not applied automatically, and moving to a new version (9.1 to 9.2) is always a manual update. Before each update, WHMCS backs up the files it is about to replace and restores them if the update fails. @Damo fair enough, it's your call. You can keep automatic updates off, or set your own schedule, under Utilities > Update WHMCS > Configure Update Settings.

Maintenance doesn't imply new features to me. Sounds like bugfix or security fixes. Maybe @WHMCS Carlos can elaborate on that.

Maintenance releases include new features. If it was strictly security-related, then it would be referred to as such.

Welcome, Miguel. Since you've been in web hosting for a while, I'd be curious which parts of WHMCS tend to trip people up most when they first set it up. Oddly enough, a short intro like yours sometimes gets more useful replies than a detailed question, because people actually read it. Sharing a concrete example from your hosting work would probably spark good discussion here.

The duplicate, publish, cancel sequence makes sense, but I'm wondering about the client-side side effects. If I cancel the original and publish a duplicate, does the client end up seeing two invoices in their billing history for the same period, or does cancelling hide the original from their view? Also, on the recurring amount fix, is updating it on the service enough, or have you seen cases where the product pricing change didn't propagate until the next billing cycle? Trying to avoid the exact confusion pRieStaKos and bear were describing before I start cancelling anything.

Oh, we will. Automatic security updates is much appreciated - as long as it doesn't ship with new features. I know that an automatic update might break something but I'd rather have non-working software than exploitable software.

Worth agreeing on a testing checklist before the upgrade begins. Sometimes, a clean WHMCS core upgrade doesn’t prove every integration still works. Do the staged upgrade on a separate install and test the full order and payment flow, registrar module actions, invoice automation and payment callbacks. For registrar modules, test registration, renewal and transfer individually, because they can behave differently after a major version change.

There is no way that we will use this feature. Leave that kind of stuff to clients that use your hosted offering.

Fair points on the LTS path, and thanks for being direct about it. We are putting a proper, published release cadence in place so you can plan ahead instead of finding out from the docs. The next LTS will be 9.2, currently scheduled for GA in mid-December, ahead of 8.13 and 9.0 going EOL. 9.2 builds on 9.0 and 9.1 with refinements and improvements, with stability as the priority, as it should be for an LTS. We also intend to ship smaller releases, more often. 9.1 introduced Unattended Automatic Updates, which apply maintenance releases on a schedule you set, so staying current takes less effort than it used to. Where possible, I'd suggest moving to 9.1 now. It will make the transition to 9.2 much easier when it lands.

It’s mentioned in the last changelog https://docs.plesk.com/release-notes/obsidian/change-log/

That output helps a lot. The response comes back with version 1.6.9.1 and status "ok" on the webspace results, so Plesk is returning your subscriptions, and 9.0.9 is already talking the new protocol (the 1.6.9.1 update shipped in 9.0.9 as WHMCS-27404). So the empty left side isn't Plesk hiding accounts. WHMCS is getting a valid list back and not turning it into rows on the Analyse screen. On the panel.ini idea: I couldn't find oldVersionsSupported anywhere in Plesk's documentation. The [api] options Plesk documents are things like enabled, allowedIPs and deprecationWarning. And since your requests already go out as 1.6.9.1, a setting for older protocol versions shouldn't change anything here. If you want to try it anyway, back up panel.ini first and take the line out again if the sync still comes back empty. What I'd do next: 1. Open a ticket with WHMCS and attach the full Module Log entries for one sync run (request and response), with usernames, passwords and domains redacted. A valid 1.6.9.1 response with status ok and an empty Analyse table is exactly the evidence they need. Mention WHMCS 9.0.9 and Plesk Obsidian 18.0.81 Update 6. 2. While you wait, check /var/log/plesk/panel.log around the time of the sync. If one of the WHMCS requests is being rejected by Plesk's XML schema validation, it shows up there even when the main listing call succeeds. 3. Test create, suspend and unsuspend on one test service. The sync screen is only a reconciliation tool, so if those still work you can carry on normally and treat Plesk as the source of truth until there's a fix. And still don't tick Import/Sync on any of those rows while the left side shows nothing.

Can't really say it much better than this. Very business-unfriendly move of WHMCS to be fast-tracking the end of support without notice, which happens to coincide with historically busy BF/CM and end-of-year. What other obstacles can we jump through by end of year?

@WHMCS Carlos I appreciate trying to work with us, but extending it until the end of December is like not extending it. December is one of the the busiest months. There's discounts, more clients, the holidays. We'll work with what we got, I guess.

I migrated from modernbill 🙂

Other than the fact that there is no clear patch to the next LTS (which we assume will be 9.1, but it's not announced) this thread basically appears to be moot as WHMCS has (at least to us) sent out an email announcing this. The fun part will be to see if history repeats itself. "Back in the day" (prob. way before most community members) ModernBill was the popular web host billing software. They released a very unpopular major upgrade and shortly after that, WHMCS because the popular choice.

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