Knowledgebase Home | Glossary | Favorites Knowledgebase Home | Glossary | Favorites
503 Errors
Article Details

Last Updated
15th of September, 2010
Would you like to...
Print this page Print this page
Email this page Email this page
Post a comment Post a comment
Subscribe me
Add to favorites Add to favorites
Remove Highlighting Remove Highlighting
Edit this Article Edit this Article
Edit this Article Quick Edit
Export to PDF
User Opinions (400 votes)
100% thumbs up 0% thumbs down
How would you rate this answer?
Helpful
Not helpful

Table of contents

  1. 503 Unrouteable URL
  2. 503 No Servers Found
  3. 503 Errors With Magento

1. 503 Unrouteable URL

This error will occur if you use an address like http://example.com without adding a site alias in the control panel.  To fix this do the following:

  1. Click your site under Sites in the control panel
  2. Click More Details
  3. Click the blue Create New Alias button
  4. In the Alias Hostname (FQDN) field type 'example.com' replacing example with your domain name
  5. Click the blue Create button

2. 503 No Servers Found

This message indicates that the Stackable load balancers are attempting to retreive an index page at your environment's document root and the web server on your container is not responding or it is returning an HTTP 500 series message.  It can also occur if a .htaccess file has malformed syntax, krufty development paths hard coded or if it is rewriting requests to the index.  This is most common if your .htaccess file is being managed by Magento but can happen with any .htaccess file.  If you are using Magento, skip ahead to the Magento specific documentation at the bottom.

To determine if the web server on your container is responding, login to Stackable Control, locate the container serving your environment and access the container's Service Monitor. If the httpd service is down, you may need to increase the amount of memory allocated to your container. 

If the Service Monitor indicates that your container's web server is responding, the web server may be returning a 500 series error to the load balancer which in turn has taken the container out of service for your site. This may be caused by:

  • Invalid .htaccess in the root of your website
  • Incorrect database connection strings
  • A syntax error or other fatal condition in the code driving your website

Log into your container and check the Apache error log for errors.  Documentation on where to find your logfiles is located here.

3. 503 errors with Magento

503 errors when using Magento are caused by .htaccess rewriting health check requests to a file the load balancer is not expecting.  To resolve this do the following:

  1. From the Stackable control panel click your site name under the Sites heading
  2. Click Details
  3. Scroll down and click LB under Settings
  4. Click Set to the right of HTTP health check url
  5. Change the '*' to '/index.php' or the name of your index file, making sure to include the '/'
  6. Click Set next to HTTP health check method
  7. change OPTIONS to GET
  8. Click Save Settings Changes

If, after trying these fixes you are unable to solve your 503 error please contact our support team at support@stackable.com.
Visitor Comments
  1. Comment #1 (Posted by Jodecy)
    It's about time smoenoe wrote about this.
Post Comment for "503 Errors"
To post a comment for this article, simply complete the form below. Fields marked with an asterisk are required.
   Your Name:
* Your Comment:
* Enter the code below:
 
Related Articles
No related articles were found.
Attachments
No attachments were found.

Continue