Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 11/14/26 in all areas

  1. Glad it helped! For the payment side, here's a quick way to prove it end to end before you call the move done: Create a test client and a $1 invoice, then pay it through each gateway you use. Check the Gateway Log (System Logs). Each payment should show a successful callback that arrived at the new domain. For Stripe, the Dashboard also shows webhook delivery attempts and responses (Developers > Webhooks). Any 3xx/4xx there means the endpoint still points at the old URL, or a redirect is getting in the way. Webhooks don't follow redirects reliably, so point them straight at the new domain. Then refund the test payments, and you're done.
    1 point
  2. +1 to Damo on redirects and client communication. A few WHMCS-specific items that are easy to miss when the domain changes: Before switching Reissue the WHMCS licence for the new domain/folder in the WHMCS Members Area, otherwise the licence check fails as soon as the URL changes. SSL on the new domain, and keep SSL on the old one, because it still has to serve the redirects. SPF, DKIM and DMARC set up on the new domain before any mail goes out from it. The switch Update System URL (plus Domain / Logo URL) under System Settings > General Settings. Make the 301 keep the path and query string, so old invoice links in emails (viewinvoice.php?id=…) and bookmarks still work. Update callback/webhook URLs at your payment gateways (Stripe webhooks, PayPal IPN, etc.), plus any OAuth/SSO apps and API IP whitelists. If you pipe or import tickets by email, add the new support addresses and keep the old ones forwarding for a good while. After Send a client announcement and update email template footers and signatures. Keep the old domain and redirects for at least a year, because people find old invoice links years later. Check Utilities > Automation Status to confirm cron and automation still run normally. Billing email can move gradually: reply from the new address and keep the old one as an alias.
    1 point
  3. We set up redirects from the old to the new. It is straightforward with rewrites to cater for older formatted URLs Educate clients in all communications about the new url. Invoice notes, helpdesk auto replies, email signatures.
    1 point
  4. Update: WHMCS Support confirmed this is a known issue, tracked as WHMCS-26898 (rounding in the return conversion). No ETA yet. Keep an eye on the release notes for that case number.
    1 point
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated