https://docs.whmcs.com/9-0/tags/whmcs-support/Recent content in whmcs-support onHugo -- gohugo.iohttps://docs.whmcs.com/9-0/troubleshooting/start-troubleshooting/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-0/troubleshooting/start-troubleshooting/In some cases, you may suspect a problem but not know exactly when or where it occurred in WHMCS. This can make finding the cause difficult. If you can’t find the symptoms in our documentation, the steps below can help you collect details before you contact support. When you troubleshoot an issue, note the exact steps that you take and their results. If you need to contact WHMCS Technical Support, these details will help us find and address the problem faster.https://docs.whmcs.com/9-0/troubleshooting/grant-access-to-whmcs-support/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-0/troubleshooting/grant-access-to-whmcs-support/If you have submitted a ticket to WHMCS Technical Support, you may need to grant access for our team to investigate issues on your system. Share the connection details that match your environment, and allow traffic from the WHMCS Support IP addresses and ranges below. This troubleshooting information only applies to self-hosted WHMCS installations. Grant Access to WHMCS Support # To grant access to your system to WHMCS Support: Identify the WHMCS instance and account.https://docs.whmcs.com/9-0/system/system-cleanup/Mon, 01 Jan 0001 00:00:00 +0000https://docs.whmcs.com/9-0/system/system-cleanup/Over time, the log files in WHMCS can become very large. WHMCS allows you to prune logs to reduce the size of the database and reduce disk space. You can access this feature at Utilities > System > System Cleanup. Only delete information that you’re certain is not necessary. WHMCS Technical Support cannot assist with some cases if you have removed the relevant log files. Performance issues in WHMCS can occur due to many factors, including insufficient system resources, large databases, problematic modules, or server configuration issues.