Vanity URLs not working for few pages after service pack upgrade | Community
Skip to main content
RitendraS11
RitendraS11
Level 4
June 10, 2025
Solved

Vanity URLs not working for few pages after service pack upgrade

  • June 10, 2025
  • 3 replies
  • 613 views

Hi Team,

I am upgrading AEM service pack to 22 and facing a weird issue -

Currently, AEM is running on service pack 6 and it is on-premise software. I have perfromed an upgrade to the latest pack 22.

After the upgrade, few vanity URLs are redirecting to 404 while accessing via dispatcher URL. Few existing vanity URLs are working fine.

What I have checked already?

  1. Vanity URLs are getting resolved properly in AEM instance (system/console/jcrresolver
  2. No duplicate pages exists with same vanity path
  3. Newly created pages works perfectly fine with vanity URL
  4. Old pages (where issue is there), when i changed the vanity path from "test-vanity" to "test-vanity-1", i can see that the URLs are getting changed when i check on dispatcher using URL (libs/granite/dispatcher/content/vanityUrls.html)

 

Any idea/pointers, I can check further! Thanks for going through my query!

Best answer by RitendraS11

This issue occurred due to permission issue with the linux script, which creates the temporary location. The script was creating the folder with root user and hence this issue occurred. After changing the user from root-user to apache, issue got resolved and after the change everything worked perfectly fine.

 

Thanks for putting your time to view the issue and providing suggestions.

3 replies

Karishma_begumSh
Karishma_begumSh
Level 4
June 10, 2025

Hi @ritendras11 Force re-save the affected pages, flush the dispatcher cache, ensure /vanity_urls is configured properly, and consider reindexing the  sling:vanityPath index.

 

Flush dispatcher cache.

/tmp/vanity_urls
/var/cache/httpd/dispatcher

 

 

Ensure dispatcher.any has this 

/vanity_urls {
/url "/libs/granite/dispatcher/content/vanityUrls.html"
/file "/tmp/vanity_urls"
/delay 300
}

    RitendraS11
    RitendraS11Author
    Level 4
    June 13, 2025

    I am checking with Adobe support on this issue. Thanks for your reply.

    The steps being mentioned were already made and verified and didn't resolve the issue. Hence, i marked the accepted solution(marked by a community advisor) as not a solution. I think, advisors should wait for the person, who have raised the issue to accept the solution - this would be better!

      Jagadeesh_Prakash
      Community Advisor
      Jagadeesh_PrakashCommunity Advisor
      Community Advisor
      June 11, 2025

      @ritendras11  from the question its clearly cache issue

       

      1. Flush the Dispatcher Cache:
      Clear the dispatcher cache for the affected pages to ensure the latest changes are reflected.
      Use the dispatcher flush agent or manually delete the cache files.

       

      2. Ensure /vanity_urls is Configured Properly:
      Verify that the /vanity_urls section is correctly configured in the dispatcher configuration (dispatcher.any or dispatcher.yaml).
      Example configuration:
      /vanity_urls {
      /url "/libs/granite/dispatcher/content/vanityUrls.html"
      /file "/tmp/vanity_urls"
      /delay 300
      }

       

        RitendraS11
        RitendraS11AuthorAccepted solution
        Level 4
        July 21, 2025

        This issue occurred due to permission issue with the linux script, which creates the temporary location. The script was creating the folder with root user and hence this issue occurred. After changing the user from root-user to apache, issue got resolved and after the change everything worked perfectly fine.

         

        Thanks for putting your time to view the issue and providing suggestions.

          Terms & ConditionsAccessibility statement

          Loading footer...