Documentation

Inconsistent Dispatcher vhost configuration across AEM as a Cloud Service publish pods

Last update: Thu Feb 05 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

After updating the Dispatcher vhost configuration to restrict access by specific IP addresses, some AEM as a Cloud Service publish pods don’t apply the new configuration consistently. This results in certain pods returning HTTP 301 redirects and causing infinite redirect loops, while others return HTTP 200 responses as expected. The issue occurs because required hosts aren’t explicitly defined in the vhost configuration. To fix this, confirm all required ServerAlias entries and restart Dispatcher pods to ensure consistent behavior.

Description description

Environment

  • Product: Adobe Experience Manager as a Cloud Service - Sites
  • Constraints: Stage environment

Issue/Symptoms

  • Some publish pods don’t load the updated Dispatcher vhost configuration, resulting in HTTP 301 redirects and infinite redirect loops.
  • Other pods successfully apply the new configuration and return HTTP 200 responses.

Resolution resolution

  1. Confirm all required ServerAlias entries. Each vhost file should include: ServerAlias "*.adobeaemcloud.net" "*.adobeaemcloud.com" "localhost" "127.0.0.1" This ensures the dispatcher invalidation process and routing functions across pods. For a deeper explanation of how Dispatcher cache invalidation works in AEM as a Cloud Service and why these aliases are required, see Caching in AEM as a Cloud Service on Experience League.
  2. Flush cache and restart Dispatcher pods. If some pods still serve old vhost logic, flush the dispatcher cache by restarting pods via Cloud Manager. This ensures all pods load the same new Dispatcher configuration. See Clear dispatcher cache at scheduled time in AEMaaCS for an example of using pod restarts to clear Dispatcher cache.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f