Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
expeditedshipper Posted August 27, 2019 Posted August 27, 2019 This is urgent...Our site is down. We're getting this error: An error occurred (500 Error) We're sorry, but a temporary technical error has occurred which means we cannot display this site right now. You can try again by clicking the button below, or try again later. Any advice as to why this might be the case? Please advise.
Daniel F Posted August 27, 2019 Posted August 27, 2019 Please submit a ticket and make sure that all the credentials on file are correct so that we can investigate this for you ASAP.
expeditedshipper Posted August 27, 2019 Author Posted August 27, 2019 7 minutes ago, Joel R said: We're you in the middle of an upgrade? No 2 minutes ago, Daniel F said: Please submit a ticket and make sure that all the credentials on file are correct so that we can investigate this for you ASAP. What do you mean by all credentials on file are correct? I'm not the main account owner. I can't submit a ticket from our actual website because it's down...
Adlago Posted August 27, 2019 Posted August 27, 2019 16 minutes ago, expeditedshipper said: This is urgent...Our site is down. We're getting this error: An error occurred (500 Error) We're sorry, but a temporary technical error has occurred which means we cannot display this site right now. You can try again by clicking the button below, or try again later. Any advice as to why this might be the case? Please advise. The first thing you should check when receiving an Internal Server Error is whether one of the following is the cause: Invalid file or directory rights; Incorrect directives in a .htaccess file; The script runs more than 60 seconds with 100% CPU usage.
expeditedshipper Posted August 27, 2019 Author Posted August 27, 2019 13 minutes ago, Adlago said: The first thing you should check when receiving an Internal Server Error is whether one of the following is the cause: Invalid file or directory rights; Incorrect directives in a .htaccess file; The script runs more than 60 seconds with 100% CPU usage. Problem is I don't have access to the back end server. It was working yesterday just fine. Can you give instructions on how to check those causes above?
Adlago Posted August 27, 2019 Posted August 27, 2019 6 minutes ago, expeditedshipper said: Problem is I don't have access to the back end server. It was working yesterday just fine. Can you give instructions on how to check those causes above? If you have ftp access, download and check the htaccess file as well as the permissions files and directories. ...or contact the host. Another site may have overloaded your server, or dDos attack
DesignzShop Posted August 27, 2019 Posted August 27, 2019 If you were switching php versions, or if using in cpanel, make sure you set memory_limit allocation to that specific php version and check other allocations.
expeditedshipper Posted August 27, 2019 Author Posted August 27, 2019 Looks like the issue was in the PHP-FPM being enabled in WHM. Any idea why this would be?
DesignzShop Posted August 27, 2019 Posted August 27, 2019 23 minutes ago, expeditedshipper said: Looks like the issue was in the PHP-FPM being enabled in WHM. Any idea why this would be? In the cPanel & WHM 76 version and later, the cPanel system enables PHP-FPM by default on a newly installed cPanel server.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.