Help Center Categories: SearchStax Help Center

SearchStax Managed Search service clients frequently report threshold alerts about “indexing errors.” They ask what causes these errors and how to avoid them. Most indexing errors are due to a… Continue reading Solr Indexing Errors

A 301 Error or 301 Moved Permanently error normally means that you asked for a page that now resides at a new URL. The web server is supposed to provide… Continue reading 301 Error

In the SearchStax Managed Search service, a “400 Error” or “400 Bad Request” error simply means that the Solr server received your request but was unable to make sense of… Continue reading 400 Error

A SearchStax Managed Search service “401 Error” means that something made an unauthorized request of the Solr cluster. This usually indicates a problem with Solr Basic Auth or with the… Continue reading 401 Error

When we see this error in SearchStax Managed Search service, what does it mean? Questions? Do not hesitate to contact the SearchStax Support Desk.

In the SearchStax Managed Search service, a 404 Error means that the browser was able to communicate with Solr, but Solr could not find what was requested. In the case… Continue reading 404 Error

SearchStax Managed Search service clients who post very large Solr queries sometimes see: HTTP Error: The remote server returned an error: (413) FULL head. A similar error occurs when indexing… Continue reading 413 Error

New users of the SearchStax Managed Search service sometimes discover that they have difficulty loading data files that exceed 100 MB in size. Note that Dedicated Node deployments are limited… Continue reading 413 Maximum Post Size Exceeded

SearchStax Managed Search service users who submit extremely large queries sometimes encounter 414 Request URI too long errors. For instance, a client received this error when submitting /select queries that… Continue reading 414 Error