Server Errors - Front End - Incident not resolved !
7 Days ago we started getting front end server errors. This is effecting our main website, Google ads / Merchant account and our customers are abandoning they're carts. We will still be paying google for the clicks and Lightspeed for this faulty service your delivering and all our customers will be getting is a generic Unable to reach the website server error within the browser.
This issue (Ticket #686970_) is one of 4 we currently have open with you and nothing has changed to fix any of the problems.
Lightspeed what do you regard as an accepteble level of site wide front and backend errors? Contractually you are required to identify what is an acceptable level of errors- So please what is it?
We are in a situation now where our tickets have a ticket!
You system Status indicates a reality to the contrary, and this is very frustrating as it reduces integrity and trust in your overall system.
I find it so very difficult to accept that adding servers to cope with seasonal loads now is the right thing to do as a server provider. You should be set up to handle the traffic before it comes.
We are not happy at all to be paying any sevice fees this month as we feel you have contractually failed to deliver the services we pay you for.
Incident not resolved !
Just incase your engineers have a moment to spare during the seemingly never ending task of keeping the ecom platform running here are instructions on how to resolve the internal 500 errors we reported several days ago now.
Fixing 500 Internal Server Error
500 errors are server-side errors, meaning it's likely your problem to fix if it's your website.
There are lots of reasons why your site might be serving a 500 Error to your users, but these are the most common:
- A Permissions Error. In most cases, a 500 Internal Server Error is due to an incorrect permission on one or more files or folders. In most of those cases, an incorrect permission on a PHP and CGI script is to blame. These should usually be set at 0755 (-rwxr-xr-x).
- A PHP Timeout. If your script connects to external resources and those resources timeout, an HTTP 500 error can occur. Timeout rules, or better error handling in your script, should help if this is the cause of the 500 error.
- A Coding Error in .htaccess. While not as common, be sure to check that your site's .htaccess file is properly structured.
Post edited by Abbas on
0 · Share on Google+