Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

AEM 6.2 Dispatcher Unresolved Issue

Avatar

Avatar
Validate 1
Level 2
phall_hershey
Level 2

Likes

10 likes

Total Posts

20 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Validate 1
Level 2
phall_hershey
Level 2

Likes

10 likes

Total Posts

20 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile
phall_hershey
Level 2

17-11-2017

Hello,

My organization is currently upgrading our AEM environment from 6.1 to 6.2.  We completed our stage setup and are experiencing zero issues.  The URLs are working without any issues.  However, when we move the same dispatcher code to PROD when we try testing the production URLs by spoofing our web browsers, each website produces a Not Found - The requested URL /en_us/home.html was not found on this server. 

On production, we don't receive any errors in the dispatcher.  When we go to https://www.sitedomain.com/content/site/en_us/home.html the page renders correctly without any issues.  However, when we remove /content/site, I get a Not Found error message.

Has anyone every experienced this issue before?  If so, how did you resolve the issue?  If not, do you have suggestions on how to get to the root cause?

Again, our stage environment is working perfectly fine with the code deployed in production.

Thanks in advance to anyone who helps!!

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
Level 2
phall_hershey
Level 2

Likes

10 likes

Total Posts

20 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Validate 1
Level 2
phall_hershey
Level 2

Likes

10 likes

Total Posts

20 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile
phall_hershey
Level 2

20-11-2017

Thanks this was just what I was looking for.  The solution to my problem was found at the bottom of the page (link below).

Https URL' resulting with 404 after in place upgrade of 6.2(6.1 to 6.2)

In the dispatcher.any/clientheaders.any added "X-Forwarded-Port"

Answers (4)

Answers (4)

Avatar

Avatar
Validate 1
MVP
Albin_Issac
MVP

Likes

106 likes

Total Posts

119 posts

Correct Reply

33 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile

Avatar
Validate 1
MVP
Albin_Issac
MVP

Likes

106 likes

Total Posts

119 posts

Correct Reply

33 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile
Albin_Issac
MVP

17-11-2017

This is a known issue with 6.2 after upgrade, https URL's are not working

Refer - https://www.albinsblog.com/2017/04/in-place-upgrade-of-aem-to-62-version.html  (Https URL resulting with Page Not Found)

Regards

Albin I

Avatar

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,115 likes

Total Posts

3,149 posts

Correct Reply

1,072 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,115 likes

Total Posts

3,149 posts

Correct Reply

1,072 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile
Jörg_Hoh
Employee

20-11-2017

Hi,

the dispatcher sample config has switched to allow all headers (using the "*" wildcard); using it would have prevented your problem from appearing 🙂

Jörg

Avatar

Avatar
Validate 1
Level 2
phall_hershey
Level 2

Likes

10 likes

Total Posts

20 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile

Avatar
Validate 1
Level 2
phall_hershey
Level 2

Likes

10 likes

Total Posts

20 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 10
Boost 1
View profile
phall_hershey
Level 2

20-11-2017

Here is the Not Found error:

The requested URL /en_us/home.html was not found on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

Avatar

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,164 likes

Total Posts

6,273 posts

Correct Reply

1,144 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,164 likes

Total Posts

6,273 posts

Correct Reply

1,144 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile
kautuk_sahni
Community Manager

20-11-2017

Please have a look at this thread:- Not Found The requested URL / was not found on this server.

Jörg Hoh​ Need you help in this Dispatcher issue!!