All Activity

I also have the same question because this looks like it could be related to how the different support department email addresses are authenticated or associated with the SMTP account. It seems that the support address can send successfully because it matches the SMTP account, while addresses such as sales, billing, abuse, and general are being rejected when the system tries to use them in the `MAIL FROM` command. The 550 message specifically mentioning that `support@example.com` cannot send emails from `sales@example.com` makes me wonder whether each department address needs to be configured separately or whether the SMTP server needs to explicitly authorize those sender addresses. I’d also be interested in knowing the recommended setup when multiple departments and users need to send replies from their own department addresses. If all four addresses are supposed to use the same SMTP account, there may be a sender-alias, mailbox, or permission setting that needs to be configured on the mail server. Since the same error is appearing repeatedly in the activity log, it seems like the application is attempting to send the message correctly but the SMTP server is rejecting the sender identity. Hopefully someone who has configured multiple support departments with separate From addresses can clarify what needs to be changed.

Actually, WHMCS has been doing it this way for at least 10 years… 😂

I added the setting to my config file to allow for invoice editing, but I notice the late fees still go into the "ledger" section without any type of label showing it is a late fee. And that section doesn't appear to be editable. How can I get back to being able to remove late fees?

Any chance of getting a copy? Sounds perfect for my needs too!

Thanks. If you have any questions we will be happy to assist you.

Have an email notifier to let me know of new tickets. I'd really like to have the name of the person who opened it included, but notification merge files in the "default" template don't offer that. Even the email of the client that opened it would be helpful if not the name. Currently I get only Ticket opened (with link) and by user # at the end of that user's link. Any way to get the user name or email also? Can't seem to find it. Admin email notification only.

Well its been 8ish months since release and about 55% of whats been released has been security fixes. I'm usually the first to update (including to beta), but I held back on 9.x, and I'm glad I did - Here we are 8 months on, and from the feedback it seems most are still recommending staying on the 8.x branch till fixes are implemented for all the invoicing issues and concerns. After you take security out, what is left is maintenance: ~1% of all post-GA updates is a new feature ~12% is billing correctness ~10% is making Nexus behave ~20% is module/platform plumbing and deletions What is in each bucket Billing / invoices / credits / reports (11) Downgrade credit calc, invoice chunking, invoice generation errors, cancelled services renewing by mistake, mass-pay late fees, late fees on 9.0 upgrade, admin invoice currency, billing notes excluded from income stats and cashflow, invoice-merge hook, Stripe admin capture logic. Platform / ops / compatibility (10) jms/serializer bump, ClassLoader error on update, Smarty-tag handling, S3 default region, Setup Tasks list, PHP-version health check, deprecated-module health check, Recaptcha error handling, activity-log error handling, persist Sign-In Integration notice. Nexus / theme / cart (9) Inclusive tax, renewals visibility, product deletions, domain addons, URL rewrites, path references, cart error handling, session handling in the Nexus theme, 360 Monitoring landing-page crash. Modules / integrations, not security (8) Plesk integration, suspend/unsuspend, and change-password updates; Enom variable name; Digicert SSL expiry; Stripe + Invisible reCaptcha errors; OAuth call errors; Sign-In Integrations handling. Removals (2) HipChat notification module; Asiapay, Gate2shop, Inpay, and Paypoint dropped from the package. New feature (1) Stripe Dynamic Payments in 9.0.3. If I had to guess, your development team is flat out using AI to plug all the big holes. If this is the case, great - Let us know. If this isn't the case, then very little has been done in the way of meaningful changes to the GA release. How bout decent passkey support - There is NO WAY im buying a third party addon for this.

Just a quick update, Lara v9.0.1 is fully compatible with WHMCS v9.0.8 (security update).

Hello, I was wondering does anyone use SmarterMail?? with there WHMCS I have Redesigned the SmarterMail Module from SmarterTools. - I have updated Core files to support latest WHMCS v9.0.8 - Updated to work with PHP v8.3 - Updated the module to work and intergade and support Lagom 2 If anyone require's this for there WHMCS Please message me be more then happy to provide the ZIP Files. Regards Lee

Hi there everyone I am lee im a software programmer from melbourne Australia

Interested in experiences migrating from self-hosted to cloud, especially regarding avoiding downtime, etc. Who's done this and can you share lessons learned? Thanks!

We are looking for an experienced Electron + React + TypeScript developer to build a custom desktop application for real-time event monitoring and bidirectional communication. Scope of work: • Implement two-way event ingestion through local sockets and daemon bindings. • Develop a secure authentication flow with key/credential handshake. • Maintain an immutable event timeline: deleted, retracted, dropped, or cleared records must remain visible as clearly marked archived placeholders rather than being removed. • Build a clean, modular and maintainable React interface. • Ensure reliable operation of persistent background streams within Electron’s IPC architecture. Requirements: • Strong commercial experience with Electron, React and TypeScript. • Practical experience working with long-running, high-availability background processes and real-time data streams. • Good understanding of Electron IPC and secure credential handling. • Ability to structure the application into clear, maintainable modules. If you have relevant experience, please share examples of recent projects or similar work. Include your Telegram contact in your private message.

Hi @azzepis, We have indeed included some maintenance updates to the Plesk module to address this in 9.0.8: WHMCS-27532 — Update Suspension and Unsuspension in Plesk WHMCS-27812 — Update Change Password in Plesk Whilst older versions won't be getting a similar update, you can grab the following files from the 9.0.8 patch set and upload them, overwriting the existing files: /modules/servers/plesk/templates/api/1.0.0.0/webspace_set_status.tpl /modules/servers/plesk/templates/api/1.0.0.0/webspace_set_password.tplwebspace_set_status.tpl These files aren't tied to a specific version of WHMCS, so will work with EoL and LTS versions.

Oh, sure. Why not, people don't need fully functional billing system, they need safe one! Good work, as always

Hi @azzepis, We do not currently plan to make these updates to the Plesk module in 8.13. 8.13 is currently in Long Term Support, meaning it receives critical security updates. Maintenance occurs in the General Availability release (currently 9.0). New features and continued compatibility updates - such as these - are, as much as possible, planned for new feature releases (9.1, 9.2 etc.)

WGS PROXMOX VPS for WHMCS v1.0.1 is now available! We've released PROXMOX v1.0.1 with several bug fixes and improvements to make provisioning and VM management more reliable. What's New in v1.0.1 Bug Fixes Fixed the client area service details page design issue. Fixed cron path configuration issues. Fixed icon file path issues. Improvements Improved IPv6 support for all VMs. Required module configuration settings are now pre-enabled. Improved VM assignment with IP selection. Provisioning is now fully based on the Guest Agent, removing the dependency on Cloud-Init. We recommend all PROXMOX module users update to v1.0.1 for the latest improvements and fixes. As always, we'd love to hear your feedback and suggestions from the WHMCS community! You can check out the module here: https://whmcsglobalservices.com/proxmox-vps-whmcs-module/

📢 PayPal Buy Now Pay Later (paypalbnpl) V1.0.3 Released We’ve released a new update with: • WHMCS 9.0.8 compatibility • Improved license verification and validation The latest version is now available for download. Please update to the latest release to benefit from these improvements.

Wanted to share how we approached the client-facing side of this, since "showcase" threads here are usually templates/themes rather than service integrations - figured it's still relevant. We added a widget inside the WHMCS client area that gives customers a live view of their active Voice Agents, Chatbots, phone numbers and remaining usage, plus a one-click button into their own portal to configure things further. A few decisions that mattered for making it feel native rather than bolted-on: - It follows whatever WHMCS template/theme is active (light/dark/auto) instead of shipping its own fixed styling - Text is served in the client's own WHMCS language setting rather than one fixed language - Every provisioning step (new order, suspend on missed payment, reactivate on payment, cancel) happens automatically and is logged to the WHMCS Activity Log, so support can see exactly what happened without leaving WHMCS Happy to go into more technical detail (hooks used, caching approach, etc.) if anyone's building something similar and wants to compare notes. The module itself (EchoCall) is listed on the WHMCS Marketplace if anyone wants to see it running live in a client area.

Something that's helped us on the support side, sharing in case it's useful to others here. For a long time our ticket volume was dominated by the same handful of repetitive questions: password resets, "why did my invoice change", basic DNS/propagation questions, "is my service still active", simple troubleshooting steps. None of that needs a human, but it still ate up staff hours because every channel we had (email, ticket, live chat widget) was just a way for the client to reach a person - none of it actually answered anything on its own. The thing that moved the needle for us wasn't a faster channel, it was giving clients something that can actually resolve the routine stuff itself (voice and chat) and only creates a ticket / pings a human when it's a genuine edge case. Two things made this work in a WHMCS context specifically: 1. It needs to see real account data (service status, invoices, tickets) to give a correct answer, not just a generic FAQ bot. Otherwise you're back to "let me create a ticket for that." 2. The handoff to a human has to be clean - full context carried over, no "please repeat your issue." We ended up building our own tool for this (EchoCall) because we couldn't find an existing option that did both well, and it's now listed on the WHMCS Marketplace as a white-label reseller module if anyone wants to see how we approached it - happy to compare notes either way, curious what others are doing to keep ticket volume down without just adding another inbox.

I’d recommend choosing a payment gateway based on your country, supported payment methods, transaction fees, and WHMCS integration. It’s also worth checking whether the gateway provides an official WHMCS module and good documentation.

Thanks for sharing this! WizardPanel Lite looks like a useful option for beginners who want to build a website directly with WHMCS. I especially like that it doesn't require WordPress. I'll definitely check it out.

Not only did they not provide this patch for 8.x, the update they did provide overwrites the plesk module changes from manually patching it, so we had to manually apply the fix again after the update.

what about 8.x?

Hi @websavers, Yes absolutely! We have ensured that the upcoming v9.1 release will be ready for this deprecation. The case ID is WHMCS-27404.

This really should be core WHMCS functionality.