Cloud IDE

Known issues

This page describes any known issues with Cloud IDE.

If you encounter any difficulties with Cloud IDE, contact Acquia Support for assistance.

Only one IDE can be used at a time

If you’re working with multiple IDEs simultaneously, you might receive the following error message when performing an action that requires invoking a Cloud Platform API endpoint. For example, when using Acquia CLI.

Your Cloud Platform API credentials are invalid.

It happens because at the moment only one IDE at a time can be authenticated against the Cloud Platform API. To work around this issue, ensure that only one IDE is opened in a browser tab at any given point in time.

The automated Cloud Platform API authentication might fail

Cloud IDE automatically connects to the Cloud Platform API. However, sometimes the connection might fail. As a workaround, you can generate a Cloud Platform API token and manually authenticate using Acquia CLI with the following command:

acli auth:login

Cloud IDE is incompatible with database prefixes

In Cloud IDE, Acquia preconfigures your database connection so that you can run your application without requiring manual configuration of the Drupal database array. However, if you use database prefixes, Acquia cannot detect this custom setting and you must configure the Drupal database array manually in settings.php.

Downloading a large database through the visual database editor can fail

The visual database editor offers the option to generate and locally download a MySQL backup of your tables. Due to the very nature of PHP processes and fixed timeouts across the stack (Apache and nginx), it is normal that databases larger than a few hundred megabytes will fail to download.

The best practice to download a database backup from Cloud Platform is to leverage Acquia CLI, by using the pull:db --no-import command. Alternatively, to download the IDE database, use Drush or a raw MySQL command instead.

Pulling an application times out when the Shield tunnel is down

In Cloud IDE, pulling an application times out with the following error when the Shield tunnel is down.

ssh: connect to host port 22: Connection timed out

To prevent this issue, use a network monitoring tool to generate keepalive pings. For more information, see resolving Shield issues.

Sending emails from Cloud IDE doesn’t work

Sending emails from Cloud IDE is not currently supported. As a workaround, you can use an external SMTP relay.

Cloud IDE reserved paths cannot be used as Drupal custom paths

For monitoring and authentication purposes, Cloud IDE has defined a number of reserved paths. This means those paths cannot be used in your Drupal application and will fail to load entirely for the expected node or endpoint.

Here is the list of reserved paths:


The workaround is to use different paths in your Drupal application.

Dark Reader browser extension runs into API limits

The Dark Reader browser extension (Chrome / Firefox) increases the number of HTTP requests per page load as it analyzes images and sends them to a third party to see if the colors should be inverted. This results in too many API requests to the IDE proxy and display the following error:

    "error": "rate_limit_exceeded",
    "message": "You have reached the maximum number of requests to the API. Please try again later."

Vimium browser extension might break the IDE functionality

The Vimium browser extension (Chrome / Firefox) provides keyboard shortcuts for navigation and control in the browser. It might break the IDE functionality, such as the Vim editor in the terminal. Acquia recommends disabling the Vimium browser extension by creating a rule.

To create a rule, go to Vimium Options, and add the following URL in the “Patterns” field. Click Add Rule, and then click Save Changes.


Federated Authentication requires a workaround

If you use Federated Authentication, you must use a workaround before configuring a newly-created IDE.