Dimitra Posted March 7, 2019 Share Posted March 7, 2019 Hello, I recently updated whmce to v7.7.1 and now the system ajax calls don't work. The error I get in Chrome Developer console is: I noticed the whmcsBaseUrl variable is empty (both in front-end and back-end). I suspect this is causing the ajax calls to fail. My whmcs is installed in the home directory and in the admin Setup-> General -> WHMCS System URL I have http://www.example.gr/. Is this correct? Should I change this url to get the whmcsBaseUrl to work? Thank you very much for your time. 0 Quote Link to comment Share on other sites More sharing options...
steven99 Posted March 7, 2019 Share Posted March 7, 2019 A 500 error indicates to me that it did connect to WHMCS, or something, and received a PHP error. As such, you would want to check your PHP error logs or apache error logs -- though you may need to enable php error logging in Setup -> General settings -> other. The WHMCS base url should already be set by the setting you mentioned, though I presume you are using https vs http in that field. 0 Quote Link to comment Share on other sites More sharing options...
WHMCS Staff WHMCS Peter Posted March 14, 2019 WHMCS Staff Share Posted March 14, 2019 Hi @Dimitra To note a 500 Internal Server Error is a generic error message produced by the server due to a misconfiguration. There are potentially a wider number of causes for such a problem, here is a brief overview of them and potential fixes: * File Permissions are incorrectly set. Should be (depending on server but general rule of thumb) 644 for files and 755 for folders/directories. * An error in one of the PHP Files - Try enabling the display errors * PHP Memory & Process limitations - Try increasing to 128MB * PHP Process Limitations - Check with server admin/hosting provider * Corrupt PHP Modules, Extensions, Builds - Check with server admin/hosting provider * The obscure - If points 1-5 don't produce a fix typically the best course of action is to check the Apache Error Logs You can find more detailed information about troubleshooting such an error message in our documentation at http://docs.whmcs.com/Common_Troubleshooting_Tips#Internal_500_Server_Error If the error still persists, we'd likely then start looking at customisations and custom templates however, we'd welcome you to open a Support Ticket, including access credentials so that we can get straight to it and assist you in resolving this. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.