Preventing 500 Read Timeout Errors

Stephan Pringle Saturday, June 7, 2003

There may be a time that you or your visitors will try to look at your online resume, portfolio or blog and during the visit, will will incur a 500 Read Timeout.

Why did this happen? Well, Apache most likely has crashed and when Plesk tried to restart it, the older sockets were still open.

So what can you do about it? If you have ROOT access, you should log in and kill off the old processes then restart Apache clean. Otherwise, contact the hosting provider and let them do it for you.

My hosting provider, Sipylus, occasionally did this for me on Plesk but since they moved me to cPanel, it does not happen anymore.

The following two tabs change content below.
facebook-profile-picture
My Twitter profileMy YouTube channel

Stephan Pringle

Technology Support Specialist at Sipylus
About The Author: Stephan Pringle is an Information Technology Support Specialist. He covers hardware and software and provides tips for you to troubleshoot and repair issues on your own. In his spare time, he writes articles about the State of New York on his Hackintosh and HackBook and that has helped him to become the top contributor of the New York City section of Yahoo! Answers.
facebook-profile-picture
My Twitter profileMy YouTube channel

Latest posts by Stephan Pringle (see all)

Related posts:

  1. Components for Parallels Plesk Panel
  2. Recover a Hacked WordPress Site
  3. Subscription Expiry in Plesk
  4. Use SSL for Domains on a Shared IP
  5. Electronic Resume
facebook-profile-picture

Stephan Pringle

About The Author: Stephan Pringle is an Information Technology Support Specialist. He covers hardware and software and provides tips for you to troubleshoot and repair issues on your own. In his spare time, he writes articles about the State of New York on his Hackintosh and HackBook and that has helped him to become the top contributor of the New York City section of Yahoo! Answers.

Related Posts