Troubleshooting Issues Related to the Enhanced Experience Composer

Display problems sometimes occur in the Enhanced Experience Composer (EEC) under certain conditions.

The EEC won’t load an internal QA URL that is not accessible on public IP. (EEC only)

This can be resolved by allowlisting the following IP addresses. These IP addresses are for Adobe’s server used for the Enhanced Experience Composer proxy. They are only required for activity editing. Visitors to your site do not need these IP addresses allowlisted

Ask your IT team to allowlist the following IP addresses:

Region IP Addresses Hostnames
United States 52.55.99.45 us1-proxy.adobemc.com
Europe, Middle East, and Africa (EMEA) 52.51.238.221 emea1-proxy.adobemc.com
Asia-Pacific (APAC) 52.193.67.35 apac1-proxy.adobemc.com

You might see the following error message in Target:

Error: Your website domain (ISP) is blocking the Enhanced Experience Composer. You can allowlist the Enhanced Experience Composer's IP addresses or turn off Enhanced Experience Composer in Configure > Page Delivery menu.

The following are reasons that you might see this error message and remedies to fix the situation:

  • Issue: Your website domain (ISP) is blocking the Enhanced Experience Composer.

    Remedy: Allowlist the IP addresses listed above.

  • Issue: The IP addresses are allowlisted but your website does not support TLS version 1.2. Target currently uses the default configuration of 1.2. Prior to the Target 18.4.1 (April 25, 2018), the default configuration supported TLS 1.0. For more information, see TLS (Transport Layer Security) Encryption Changes.

    Solution: See the following question (The Enhanced Visual Experience Composer won’t load on secure pages on my site that use TLS 1.2).

The EEC won’t load on secure pages on my site that use TLS 1.0. (EEC only)

You might see the error message described above in “The Enhanced Visual Experience Composer won’t load on secure pages on my site.” if the above IP addresses are allowlisted but your website does not support TLS version 1.2. Target currently uses the default configuration of 1.2. Prior to the Target 18.4.1 (April 25, 2018), the default configuration supported TLS 1.0. For more information, see TLS (Transport Layer Security) Encryption Changes.

To check the TLS version on your website using Firefox (other browsers have similar steps):

  1. Open the affected website in Firefox.

  2. Click the Show Site Information icon on the browser’s address bar.

  3. Click Show Connection Details > More Information.

  4. Examine the TLS version information under Technical Details:

  5. If you find that your website is showing TLS 1.0, see TLS (Transport Layer Security) Encryption Changes for information about Target’s TLS support policy. To remedy the situation for now (valid until September 12, 2018), reach out to Customer Care for configuration with your TLS version and the domain.

I’m seeing timeouts or “access denied” errors when loading sites with proxy enabled. (EEC only)

Make sure proxy IPs are not blocked in your environment.

On this page