Multi-Experience Operations
Known issues
On Multi-Experience Operations (MEO) sites, Acquia-issued domains added by MEO setup are registered as custom domains in the site configuration. After a customer uploads a custom SSL and TLS certificate, the load balancer serves the custom certificate for all custom domains, such as Acquia-issued domains. Since the custom certificate does not cover *.prod.acquia-sites.com, browsers display the Connection is not secure or TLS certificate mismatch error when users access these domains. The default FQDN of the site does not get affected and continues to serve the default Acquia wildcard certificate. This issue occurs only if a custom SSL or TLS certificate is present on an MEO site. MEO sites without a custom SSL or TLS certificate are not affected.
Workaround: To access the site securely, complete one of the following actions:
Use the default FQDN or a custom domain to access the site.
Remove the custom SSL or TLS certificate if the certificate is not required. This action enables all domains to use the default Acquia wildcard certificate.
Continuous Delivery environments (CDE), formerly known as On-Demand Environments (ODE), do not support MEO codebases. You cannot create CDEs for applications hosted on MEO. If you try to create a CDE for an MEO-hosted application, the operation fails.
To develop and test changes for MEO sites, use the non-production environments provisioned for your codebase. To request additional non-production environments, contact Acquia Support.
On Multi-Experience Operations (MEO) sites, Acquia-issued domains added by MEO setup are registered as custom domains in the site configuration. After a customer uploads a custom SSL and TLS certificate, the load balancer serves the custom certificate for all custom domains, such as Acquia-issued domains. Since the custom certificate does not cover *.prod.acquia-sites.com, browsers display the Connection is not secure or TLS certificate mismatch error when users access these domains. The default FQDN of the site does not get affected and continues to serve the default Acquia wildcard certificate. This issue occurs only if a custom SSL or TLS certificate is present on an MEO site. MEO sites without a custom SSL or TLS certificate are not affected.
Workaround: To access the site securely, complete one of the following actions:
Use the default FQDN or a custom domain to access the site.
Remove the custom SSL or TLS certificate if the certificate is not required. This action enables all domains to use the default Acquia wildcard certificate.
Continuous Delivery environments (CDE), formerly known as On-Demand Environments (ODE), do not support MEO codebases. You cannot create CDEs for applications hosted on MEO. If you try to create a CDE for an MEO-hosted application, the operation fails.
To develop and test changes for MEO sites, use the non-production environments provisioned for your codebase. To request additional non-production environments, contact Acquia Support.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Multi-Experience Operations