Knowledge Base - Articles

Posted 21 Mar 2017

A wildcard certificate is an SSL certificate which can be used with multiple subdomains of a domain. The principal use is for securing web sites with HTTPS.

A wildcard is often designated as *.example.com and cover sub domains such as:

It should be understood that a wildcard SSL cert will ONLY cover the domains at the level of the "*" and NOT two levels such as:

Posted 17 Mar 2017

Drupal 8 and certain contributed modules may increase the size of headers sent out with each response. On Acquia Cloud, the soft limit is 60 individual headers and/or a combined total of 23kb of header data. Requests which exceed the soft limit may serve 503 status codes from Varnish and 200 from the Apache backend. 

We are working towards a Varnish configuration change that will remove this soft limit. In the meantime you may need to adjust your site to emit less header data.

Posted 16 Mar 2017

Early Drupal composer-based builds frequently utilized 'packagist.drupal.org' to fetch drupal packages via Composer. This repository was fully deprecated on March 10th, 2017. Builds still using 'packagist.drupal.org' will cause composer update to fail unless the recommended changes noted below are made to your composer.json file. If you have Remote Administration (RA), automated updates will fail until the changes below are made.

Posted 15 Mar 2017

The new Acquia Cloud UI now allows you and your team to take control of, and manage your own SSL certificates. 

Here are some simple steps to quickly create and upload your SSL certificate to the environment on which you wish to have domains covered with the particular SSL certificate. 

Posted 13 Mar 2017

When installing an SSL certificate through our new Cloud UI, the Private Key will only auto-populate under these conditions:

  • The CSR was generated in our new Cloud UI (Not through another non-Acquia source and not in the old UI)
  • When you install the cert, be sure to click the Install link to the RIGHT of the CSR name. 

If you believe that you have met the above conditions and the Private Key is still NOT auto-populating, you should:

Posted 13 Mar 2017

If your team is installing an SSL certificate through our new Cloud UI and are getting the error "Invalid Private Key" - you may want to start by reviewing the order of your CA Intermediate Cert file. 

We have found that some SSL providers, such as GoDaddy, provide these cert files in the reverse order from what is required by our tools. Our tool expects the order to begin with the main certificate and end with the root.

Posted 01 Mar 2017

If your site is showing an error similar to this one:

php-error .... PHP Fatal error: Class 'Solarium\Client' not found in /mnt/www/html/XXXXX/docroot/modules/contrib/acquia_connector/acquia_search/src/Plugin/SolrConnector/SearchApiSolrAcquiaConnector.php on line XX request_id=...

This is a message warning you that the code in your Drupal site can't find the Solarium PHP library (which is basically a set of PHP classes that would've normally been downloaded by Composer, and that are needed by search_api_solr module).

Posted 21 Feb 2017

As of Wednesday, 1 March 2017, Acquia Cloud Free applications will no longer have access to Acquia Search.  

If your Acquia Cloud Free application requires Acquia Search, we recommend you speak with our Sales team to upgrade to an Acquia Cloud Professional subscription before 1 March 2017. 

You can reach our Sales team through https://www.acquia.com/ or by phone or email address for your region.  

Posted 13 Feb 2017

In April 2017, Ubuntu 12.04 (Precise) will reach end of life. After April 2017, Canonical, Ubuntu’s developer, will no longer issue security fixes or package updates for Precise, so it is important that we migrate your application to Ubuntu 16.04 (Xenial) in order to keep your application on an operating system that is supported and secure. This deadline will not be extended as it is critical your application be upgraded to ensure its continued security.

Acquia Cloud Free applications

Posted 09 Feb 2017

Since version 7.50, Drupal 7 has supported the storage of multi-byte UTF-8 characters in MySQL. This means Drupal 7 can now store emojis, certain Asian language characters and other symbols.

Some preparatory steps must be taken, however, to fully enable this capability on Acquia Cloud environments.

Contact supportStill need assistance? Contact Acquia Support