Under some conditions, a website administrator may see information like the following in the Solr connection status:

To protect your data, the [Acquia Search / Search API Acquia] module is
enforcing read-only mode on the indexes, because it could not figure out what
Acquia-hosted Solr index to connect to. This helps you avoid writing to a
production index if you copy your site to a development or other
environment(s). These index IDs would have worked, but could not be found on
your Acquia subscription:

 -  ``ABCD-12345.qa.mysiteXYZXYZ12345``
 -  ``ABCD-12345.qa.default``

Acquia Search displays this message during one of the following situations:

• Your current subscription does not contain a Solr index belonging to the current environment (for example, dev, stage, or prod) or to the current Drupal multisite instance.

• The modules have forced the Solr connection into read-only mode to prevent operations that may cause index corruption.

If you receive a message like the preceding one, refresh your Acquia subscription on your Drupal website by using the following steps:

1. As an administrator on your Drupal website, go to Reports > Status Report.

2. To the right of Acquia subscription status, click Manually refresh the subscription status.

Continuing to see the error

If your website continues to display the message, you can take other corrective steps based on your website’s environment and subscription level.

If you have an Enterprise or Elite subscription and an application on Acquia Cloud, take one of the following actions:

• Create a Support ticket to request any additional or missing Solr indexes. In the ticket, attach the status messages and website URL(s) from the problem website.

• Configure the connection by overriding the Drupal variables.

• Take no action, which will cause the website or environment to use your production Solr index in read-only mode, allowing you to test search using the production website’s Solr index.

If your website isn’t on Cloud Platform, take one of the following actions:

• Configure the connection by overriding the Drupal variables.

• Take no action, which will cause the website or environment to use your production Solr index in read-only mode, allowing you to test search using the production website’s Solr index.

If you have a different subscription level (you are only entitled to a single Solr search index for your entire subscription), take one of the following actions:

• Configure the connection by overriding the Drupal variables.

• Take no action, which will cause the website or environment to use your production Solr index in read-only mode, allowing you to test search using the production website’s Solr index.

Troubleshooting multiple search indexes

To protect your data, the [Acquia Search / Search API Acquia] module is
enforcing read-only mode on the indexes, because it could not figure out what
Acquia-hosted Solr index to connect to. This helps you avoid writing to a
production index if you copy your site to a development or other
environment(s). These index IDs would have worked, but could not be found on
your Acquia subscription:

 -  ``ABCD-12345.qa.mysiteXYZXYZ12345``
 -  ``ABCD-12345.qa.default``