Jump to content

WHMCS Alex

WHMCS Technical Analyst II
  • Content Count

    173
  • Joined

  • Last visited

  • Days Won

    6

WHMCS Alex last won the day on August 3

WHMCS Alex had the most liked content!

Community Reputation

26 Excellent

2 Followers

About WHMCS Alex

  • Rank
    WHMCS Technical Analyst II

Recent Profile Visitors

4028 profile views
  1. Hi @markp, Banking information is captured or existing information utilised during the payment of an unpaid invoice on a customers account. The workflow for Stripe ACH is documented here: https://docs.whmcs.com/Stripe_ACH#Payment_Workflow I hope this helps.
  2. Hi @Manchester Web Hosting, You are more than welcome to submit this as a bug here: https://www.whmcs.com/members/bugreport.php In order for there to be further assistance provided, or an update that resolves the potential issue consumed, you would need to move to a monthly leased license.
  3. Hi, Thanks for your post! I would advise using the session test script here to help determine the issue: https://help.whmcs.com/m/troubleshooting/l/678268-troubleshooting-login-problems#php-session Assuming you are using WHMCS version 7.7 or above, a potentially quick solution, where the issue relates to PHP session storage on the web server, is to configure WHMCS to leverage database driven sessions: https://docs.whmcs.com/Sessions#Configuration_2 Simply adding the line below to the configuration.php file would do that: $session_handling = 'database';
  4. Hi, Thanks for your post. Did you update your WHMCS System URL after moving the files?
  5. Hi, Thanks for your post. The described issue wouldn't be something that you could resolve, but it's certainly something we would be keen to if it's causing payment issues. I would advise submitting this as a bug report here: https://www.whmcs.com/members/bugreport.php If you can demonstrate the issue itself is causing payment failures and the change to resolve it is silm (it potentially is), we may be able to help you resolve this sooner. Please do link this thread in the report.
  6. Hi @KNK, Please update to version 8.3.1 to resolve this: https://docs.whmcs.com/Changelog:WHMCS_V8.3.1 I hope this helps.
  7. Hello @aknight, This guide will help you get that resolved: https://help.whmcs.com/m/v82/l/1420755-resolving-a-down-for-maintenance-error The tblupdatelog table in the database should provide you with more information on why the update failed. I hope this helps.
  8. Hi @jeebee123, Do you have the Sync Next Due Date option enabled? A synchronisation of the Expiry Date but not Next Due Date suggests you have the Domain Sync Enabled option enabled, but the Sync Next Due Date option. If you do have that enabled, please review the Domain Synchronisation report that is emailed out to all administrators who have the System Emails option enabled in their role for further information. I hope this helps.
  9. Hi @Hosting New, This guide will help you get that resolved: https://help.whmcs.com/m/v82/l/1420755-resolving-a-down-for-maintenance-error
  10. Hi, Thanks for your post! The error references an addon module by the name of "tpl_override": Call to a member function clientarea() on null in /home/elanmy/public_html/whmcs/modules/addons/tpl_override/hooks.php:26 WHMCS does not develop or distribute a module by that name, so I would advise reaching out to the developer(s) of it with this error so they can review the error and the function being called to determine the problem for you.
  11. Hi, This issue has been resolved in version 8.3 of WHMCS: https://docs.whmcs.com/Changelog:WHMCS_V8.3.0_Beta_1 Once version 8.3 reaches stable release tier, updating to it will resolve this.
  12. Hi @persis Thanks for your post! The issue you report has been resolved in version 8.3 of WHMCS: https://docs.whmcs.com/Changelog:WHMCS_V8.3.0_Beta_1 Once version 8.3 reaches stable release tier, updating to it will resolve this.
  13. Hi @tkalfaoglu, You will want to execute this SQL query (after you have taken a backup of the database): UPDATE tblhosting SET server = 'NEW_SERVER_ID' WHERE server = 'OLD_SERVER_ID'; Where "NEW_SERVER_ID" is the ID of the server you want all clients to be associated with and "OLD_SERVER_ID" is the ID of the server you intend to remove. You can easily find the ID's by looking at the tblhosting.id value of the database. Once that query executes and all clients are associated with the one server, you can remove the duplicate server from inside WHMCS. I hope this helps.
  14. Hi, If you are using Cloudflare and the issue is that the authoritative IP address for requests is not being correctly recorded, you likely need to configure your Trusted Proxies setting inside WHMCS, adding in Cloudflare’s IP ranges.
  15. Hi, There is presently not a way you can modify the Domain Syncronisation feature to sync more than 50 domains at one time, however, you can force the execution of the task via cron.php to execute more frequently. Example command: php -q /path/to/crons/cron.php do --DomainStatusSync Executing that every 5 minutes (either manually or as a cron job) would result in 600 domain names being synchronised every hour (12 x 50). I hope this helps.
×
×
  • 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