Entire shop site fails to load suddenly

[Torbz]

Performed a recent upgrade on a shop to 1.4.6.2

Bought a NoChex module from the addon shop for £240 which didn't work

 

Gave the PS support team admin access to the shop to have a look at it.

 

They refund the money and don't fix the module. 10 minutes after support email me about this, the whole site disappears with no error messages and a blank white screen.

 

Server error log shows nothing except the odd 404 missing file.

 

What on earth has happened? No-one else we know has intervened!

 

Totally stuck for ideas now and it's the client's busiest time of year and they have no shop!

 

There's no apparent server breach or hosting account breach has anyone got the slightest idea where to look now the site is obviously loading but bringing a blank white page.

 

Thanks for any help

[Guest]

Sure I can't help, but posting a link to the store may help others to help you?

[Torbz]

Good point - forgot that - though NOTHING loads on the page so it won't offer any insight.

 

www.needleneeds.co.uk/store

 

Interestingly, its kicked up a 500 error, but it is definitely not file permissions (as it previously always has been with 500 errors) and the cpanel error log is useless at adding any bits of info.

[Guest]

I have no idea, but perhaps if I ask some questions it may prompt you or others

 

Have you checked with the host to ensure they do not have problems (I know you can get into cpanel, but I have found that hosts can have issues at the front end, but not the back end)

 

Can you access via ftp? Are all the files where they should be? Can you restore from a backup?

 

HTTP Error 500 Internal server error

Introduction

The Web server (running the Web Site) encountered an unexpected condition that prevented it from fulfilling the request by the client (e.g. your Web browser or our CheckUpDown robot) for access to the requested URL.

This is a 'catch-all' error generated by the Web server. Basically something has gone wrong, but the server can not be more specific about the error condition in its response to the client. In addition to the 500 error notified back to the client, the Web server should generate some kind of internal error log which gives more details of what went wrong. It is up to the operators of the Web server site to locate and analyse these logs.

500 errors in the HTTP cycle

Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with the Web server:

• Obtain an IP address from the IP name of the site (the site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
  
  
• Open an IP socket connection to that IP address.
  
  
• Write an HTTP data stream through that socket.
  
  
• Receive an HTTP data stream back from the Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.
  
  

This error occurs in the final step above when the client receives an HTTP status code that it recognises as '500'. Frank Vipond. September 2010.

Fixing 500 errors - general

 

This error can only be resolved by fixes to the Web server software. It is not a client-side problem. It is up to the operators of the Web server site to locate and analyse the logs which should give further information about the error.

[Guest]

YOu look to be back up and running. What was the problem in the end?