The SearchStax® Frequently Asked Questions page includes the following approved question and answer about our Apache Solr Cloud services.

Sitecore Connection Errors.

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. Note that DHCP can change a server’s IP address without warning. If the connection used to work but then stopped working, suspect this source.

  • 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="" connectionString="<Solr HTTP Endpoint>/solr;solrCloud=true" />

    Solr is unforgiving about this string. An extra / at the end will break it.

    The connectionString ends with /solr;solrCloud=true. There is no / between /solr and the semicolon. Sitecore inserts that character automatically.

    If you connect to Solr from a browser, which is a good debugging aid, you must include the / prior to the semicolon, as in /solr/;solrCloud=true.

    The solrCloud=true parameter 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. The system seemed to hang or took a very long time to complete indexing. There was 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. (They say the bug was fixed in Sitecore 10, but two of our clients have encountered it there.)

  • Solr Basic Auth password contains special characters: The Sitecore connection string to Solr often contains the Solr Basic Auth username and password:

    https://username:pass%word@<Solr Endpoint>;solrCloud=true

    There are special characters that cannot be passed in an HTTP URL. If the password contains % signs, for instance, 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”.

    Or, just use a password without special characters.

Solr.log file contains schema or field errors:

We love to answer questions!

Please contact the SearchStax Support Desk immediately if you have any question about Solr Cloud deployments.

Return to Frequently Asked Questions.