Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>There are several reasons that you might receive the "no suitable nodes" error regarding requests. A fuller discussion of this problem is at <a href="http://nosuitablenodes.com" rel="nofollow noreferrer">http://nosuitablenodes.com</a>. Here's a summary:</p> <blockquote> <p>First, this is an error message from a load balancer used to direct traffic to available backend servers for your site. It means no backend resources are available to produce the content requested. This is a default message basically meaning the site is currently unavailable.</p> </blockquote> <p>Think about your site's resources. Static HTML? Scripting language that creates the page content on the fly? DB-backed website? At each level there are resources that can cause a load balancer (that produced the error message) to time out and return this message.</p> <p>What can you do? (The real question!)</p> <p>First, contact the system administrator for your site. The system administrator with access to the load balancer will be able to pinpoint the service that is causing the error condition.</p> <p>As the site owner you can do a few things to remedy this condition yourself. Add more resources behind the load balancer (for hosted sites, this may be beyond your control) If you are not in control of the resources (i.e., you are using a hosting provider): Determine the actual cause and then for:</p> <ol> <li>Web Server) Optimize the configuration to support more connections</li> <li>File system/server) Move static content to a CDN, using byte-code caching in your scripting engine to reduces disk reads</li> <li>Scripting engine) Optimize scripting engine to use byte-code caching</li> <li>Database) optimize queries or move to a dedicated database instance</li> <li>Remote resources) minimize dependencies on remote resources, or optimize them, if possible</li> </ol>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload