Vanity urls are not working on publishers | Community
Skip to main content
RitendraS11
New Participant
December 20, 2023
Solved

Vanity urls are not working on publishers

  • December 20, 2023
  • 3 replies
  • 2522 views

I have a page, where I wanted to add a vanity URL. After adding the vanity URL,

In Author instance, 

When checked on <SERVER_URL>/libs/granite/dispatcher/content/vanityUrls.html - VanityUrl appears fine.

In the Publish instance,

When checked on <SERVER_URL>/libs/granite/dispatcher/content/vanityUrls.html - VanityUrl doesn't appear. It should appear on the publisher instance.

 

When I hit the vanity URL directly on the publisher, I get the page with the correct content. Why do I get the correct page provided the vanity URL doesn't appear in Query?

 

When I hit the vanity URL via the dispatcher, it throws 404 error page.

 

I have checked a few threads in the community related to vanity URLs - but didn't find anything related to my query.

 

Please help me here with suitable pointers.

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by RitendraS11

Hi Everyone, 

 

Thanks for looking into it.

The issue was with the re-indexing of oak indexes. It was not working properly on publishers and hence we need to manually re-index the failing Oak indexes. It resolves the issue.

3 replies

RitendraS11
RitendraS11AuthorAccepted solution
New Participant
January 23, 2024

Hi Everyone, 

 

Thanks for looking into it.

The issue was with the re-indexing of oak indexes. It was not working properly on publishers and hence we need to manually re-index the failing Oak indexes. It resolves the issue.

robertol6836527
New Participant
February 4, 2024

HI,


Could you tell me how it is possible to launch the re-index the failing Oak indexes for the vanity URL?


Thanks

RitendraS11
New Participant
February 7, 2024

@robertol6836527 - As mentioned in my query, the vanity URLs appeared fine in the author instance and not in publishers for newly changed URLs. In my checks, I found that some oak indexes were failing. Once, the indexes were re-indexed - the issue was resolved.

kautuk_sahni
Employee
January 2, 2024

@ritendras11 Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

 

Kautuk Sahni
RitendraS11
New Participant
January 2, 2024

Hi Kautuk,

 

We have almost solved the issue with the help of the Adobe support team. Once, the issue is resolved, I will add the solution and findings for the community.

 

Best

Riten 

kautuk_sahni
Employee
January 23, 2024

@ritendras11 Just a nudge! If you solved this, can you please share the answer with the Community?

Kautuk Sahni
Saravanan_Dharmaraj
New Participant
December 21, 2023

@ritendras11 Could you check if the anonymous user has access to this URL in publish

  /libs/granite/dispatcher/content/vanityUrls.html and set the read permission and do the testing?

 

RitendraS11
New Participant
December 21, 2023

@saravanan_dharmaraj - didn't get your point here - how the permissions on the vanity URLs page will impact here. The page is accessible on the publisher without login. It works fine with the old configured vanity URLs. Only, newly configured vanity URLs are not reflecting on publishers and dispatchers.

 

I have a similar setup for one test environment and vanityUrls works perfectly there.

Saravanan_Dharmaraj
New Participant
December 21, 2023

Gotcha. I thought none of them are coming through that URL. So its only new one added not showing up.