Known issues in Acquia Cloud

This page describes known issues in Acquia Cloud:

  • Some Drupal modules are not supported on Acquia Cloud
    The design of the Acquia platform can sometimes cause incompatibilities with Drupal contributed modules. Some Drupal modules are not supported on Acquia Cloud; these are listed in Modules and applications incompatible with Acquia Cloud. Other modules can be used on Acquia Cloud, but may require caution or special configuration; these are listed in Modules to use with caution on Acquia Cloud.
    For information about other software that is incompatible with Acquia Cloud, see Unsupported software.
  • Varnish header limits (CL-16154)
    Drupal 8 and certain contributed modules can increase the size of headers sent out with each response. On Acquia Cloud, the soft limit is a combination of up to 60 individual headers and up to 23KB of header data. Requests which exceed the soft limit may serve 503 status codes from Varnish and 200 status codes from the Apache web server. For more information, see the Varnish header limits knowledgebase article.
  • Acquia Connector request timeouts (N3-581)
    When a Drupal website is connected to an Acquia subscription, it sends heartbeat requests during each cron run. By default, cron runs at the beginning of each hour, which can cause the Acquia subscription service to receive thousands of simultaneous connections across all subscriber websites. This can cause some requests to timeout.
    Workaround - If your subscription service is experiencing timeouts, Acquia recommends that you modify your cron runs to not begin at the start of the hour.
  • Drupal multisite installations do not work with Acquia Insight (N3UI-904)
    The Acquia Cloud interface does not report Acquia Insight information for Drupal multisite websites.
  • Importing a site archive from a local file (N3UI-1184)
    The Acquia Cloud interface does not support importing a site archive from a local file using the UI. Instead, you can import a site archive from a URL or import using Drush.
  • Database table prefixes in Drupal 8 are not supported (CL-12329)
    Acquia Cloud does not support the use of table prefixes in databases on Drupal 8.
  • Using the Minimal installation profile for Drupal 8
    Acquia Cloud does not support the Minimal installation profile for Drupal 8 using the web installer. If you install Drupal 8 using the Acquia Cloud interface, the Minimal installation profile will not be available. Installing the Drupal 8 Minimal profile using Drush will work as expected. If you install Drupal 8 core from a tarball that includes the Minimal installation profile in the Acquia Cloud interface, you must first enable Live Dev on the environment in which you are installing Drupal, or else the installation will fail. Enabling Live Dev first allows you to install Minimal in Drupal 8. Drupal will change its settings.php file during this process, so afterwards, you will need to SSH into your server and commit the changes to Git or SVN.
    Importing a Drupal 8 application into Acquia Cloud after it was installed elsewhere using the Minimal profile (for example, using Acquia Dev Desktop) will not cause problems.
  • Theme change issues with Twig caches on Drupal 8 (CL-13461)
    Drupal 8 applications on Acquia Cloud Enterprise can experience issues where cached Twig templates fall out of sync on different web server instances when changes to themes are being made and a code deployment has been performed. The problem arises from having separate copies of the compiled Twig templates on each web server instance and a related Drupal core issue.
    Workaround - When you make changes to themes in Drupal 8 applications on Acquia Cloud Enterprise, connect to each web server instance, and then run a command similar to the following to remove the outdated Twig templates:

    drush @[sitename].[prod] --uri=http://[site_URL]/ ev '\Drupal\Core\PhpStorage\PhpStorageFactory::get("twig")->deleteAll();'
  • Backups page may not list all available backups (CL-228, NN-5435)
    The Backups page in the Acquia Cloud interface lists recent backups for the Acquia Cloud environment. However, there is a delay between the time when backups are created and when they are added or removed from the Backups page. As a result, the most recently created backups may not yet be listed, while older backups that have been replaced and deleted may be listed, but not in fact be available for download or for restoring the database.
    Workaround - You can connect to your server using SSH, SFTP, scp, or rsync, and download the backup files from the /mnt/files/[site].[env]/backups directory. For more information, see Downloading database backups from the command line.
  • PECL uploadprogress module doesn't work on Acquia Cloud (CL-10860)
    The PECL uploadprogress module is installed on Acquia Cloud, but does not currently work.
  • AuthUserFile in .htaccess is not supported
    The AuthUserFile directive in the Apache .htaccess file sets the name of a text file containing a list of users and passwords for user authentication. Using AuthUserFile is not supported in Acquia Cloud, since its value must be either an absolute path or a path relative to the server root, and therefore won't work across different Acquia Cloud environments.
  • SymLinksIfOwnerMatch in .htaccess is not supported
    Due to the configuration of directory ownership and permissions for your Acquia Cloud application's codebase and files directories, use of the SymLinksIfOwnerMatch option in your application's .htaccess file will prevent your web server from being able to access any of the assets in your files directory. The FollowSymLinks option should be used instead.
  • Some environment names in the updated Acquia Cloud interface have changed
    After the updated Acquia Cloud interface was released on December 13, 2016, in a few cases some environment names changed to unexpected values.
    Workaround - Simply rename the affected environment to use the desired name. For information about how to rename an environment, see Working with environments.
  • zlib "freed prematurely" message when inspecting tasks (CL-13875)
    When inspecting the output of any successful or failed task, the final line is:
    zlib(finalizer): the stream was freed prematurely.
    This message in the task's output does not indicate a specific issue, and can be ignored.
  • Link to application's modules page does not work (NET-69)
    The Acquia Cloud user interface displays a message that previously linked to an application's module page. This function is unsupported in the current user interface.

Add new comment

Plain text

  • No HTML tags allowed.
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.
By submitting this form, you accept the Mollom privacy policy.

Contact supportStill need assistance? Contact Acquia Support