SearchStax clients encounter issues when connecting Sitecore to Solr Cloud for the first time. The issues are so common that a developer can encounter them in sequence (fix one, meet the next one). On this page we present solutions to a range of these Sitecore start-up issues.
Note that SearchStax supplies explicit instructions for bridging this gap, including a Sitecore plugin that performs the configuration for you.
Sitecore can’t connect to Solr:
- IP Filtering. First, be sure that the computer running Sitecore has been whitelisted in the IP filters of the Solr deployment.
- Incorrect cloud connection string. To connect Sitecore to a Solr cloud cluster, check the App_Config/ConnectionString.config file for an entry similar to:
<add name="solr.search" connectionString="<Solr HTTP Endpoint>/solr;solrCloud=true" />
The connectionString ends with
/solr;solrCloud=true. There is no
/solrand the semicolon. Sitecore inserts that character automatically. If you connect to Solr from a browser, however, you must include the
/prior to the semicolon, as in
solrCloud=trueparameter is highly recommended for single-node Solr deployments, and is required for Solr clusters.
- Sitecore mentions 10.x.x.x:8983. You tried to build an index from the Sitecore Index Manager and got an error saying “Unable to connect to Solr” and mentioning an internal IP address (10.x.x.x) and port 8983. This is a known bug in Sitecore. To get around it:
- Generate the index from the Sitecore Content Editor instead of the Index Manager.
- Contact Sitecore for a patch file.This bug is being tracked by Sitecore under the reference number – 355209. If you’d like to learn more about this bug then please feel free to reach out to Sitecore.
- Solr Basic Auth password contains % signs: The Sitecore connection string to Solr often contains the Solr Basic Auth username and password:
If the password contains % signs, you will get an error saying “Not a valid Solr URL.” Substitute %25 for % in the URL string, so the above password becomes “pass%25word”.
Solr.log file contains schema or field errors:
- See our Help Center page on What causes Indexing Errors? for more information.