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

Contexthub.kernel.js giving 404 in Publish Instance

Avatar

Avatar
Validate 1
Level 2
Hina29
Level 2

Likes

3 likes

Total Posts

14 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile

Avatar
Validate 1
Level 2
Hina29
Level 2

Likes

3 likes

Total Posts

14 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile
Hina29
Level 2

11-04-2018

Hi ,

I have used context hub in my template as below:

<sly data-sly-resource="${'contexthub' @ resourceType='granite/contexthub/components/contexthub'}"/>

However on publish instance I get a 404 for below url

http://localhost:4503/etc/cloudsettings/default/contexthub.kernel.js  ---> Giving 404

I also get a 404 error in chrome browswer console for this js file.

However in Author this works fine.

http://localhost:4502/etc/cloudsettings/default/contexthub.kernel.js  ---> Loading fine

Any help is really appreciated.

Thanks

Hina

Replies

Avatar

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,198 likes

Total Posts

6,369 posts

Correct Reply

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

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,198 likes

Total Posts

6,369 posts

Correct Reply

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

12-04-2018

Enabled the below urls in the Dispatcher's publish-farm.any

       /0010 { /type "allow" /url "/etc/cloudsettings*" }

       /0011 { /type "allow" /url "/etc/segmentation*" }

Something similar reported here:- Re: ContextHub experiences not showing on AEM 6.2 Publish instance

Avatar

Avatar
Validate 1
Level 2
Hina29
Level 2

Likes

3 likes

Total Posts

14 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile

Avatar
Validate 1
Level 2
Hina29
Level 2

Likes

3 likes

Total Posts

14 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
View profile
Hina29
Level 2

13-04-2018

Thank you for the response. I added the below entries in dispatcher publish farm file.

  /0080 { /type "allow" /method "GET" /url "/libs/cq/personalization/*" }

/0081 { /type "allow" /method "GET" /url "/etc/segmentation.segment.js"  }

/0082{ /type "allow" /url "/etc/cloudsettings*" }

/0083 { /type "allow" /url "/etc/segmentation*" }

Now i see more errors in browswer console

Below json file gives 404

http://xxxdomain.com/abc/jcr:content/contexthub.pagedata.json  --> 404

/jcr:content/contexthub.commerce.cart.json --> 404

/jcr:content/contexthub.commerce.orderhistory.json --> 404

/jcr:content/contexthub.commerce.relatedproducts.json  --> 404

Does Adobe have any documentation as to what needs to be opened in the Dispatcher when using the “granite/contexthub/components/contexthub” resource?

Just to let you know i am using AEM 6.2

Thanks

Hina

Avatar

Avatar
Boost 1
Level 1
Bhaskar_Mazumd1
Level 1

Like

1 like

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Boost 1
View profile

Avatar
Boost 1
Level 1
Bhaskar_Mazumd1
Level 1

Like

1 like

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Boost 1
View profile
Bhaskar_Mazumd1
Level 1

12-11-2018

Hi Hina,

Wanted to know if you found a resolution to the 404 errors mentioned in your post here.

I am facing the same error and i am working on AEM 6.4.

Regards,

Bhaskar

Avatar

Avatar
Give Back
Level 2
Basavaraj_K
Level 2

Likes

5 likes

Total Posts

6 posts

Correct Reply

1 solution
Top badges earned
Give Back
Boost 5
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Give Back
Level 2
Basavaraj_K
Level 2

Likes

5 likes

Total Posts

6 posts

Correct Reply

1 solution
Top badges earned
Give Back
Boost 5
Boost 3
Boost 1
Affirm 1
View profile
Basavaraj_K
Level 2

13-11-2018

Check does the anonymous user has read permission to the /etc/segmentation in publish.

Avatar

Avatar
Boost 3
Level 1
esu2805
Level 1

Likes

3 likes

Total Posts

8 posts

Correct Reply

0 solutions
Top badges earned
Boost 3
Boost 1
View profile

Avatar
Boost 3
Level 1
esu2805
Level 1

Likes

3 likes

Total Posts

8 posts

Correct Reply

0 solutions
Top badges earned
Boost 3
Boost 1
View profile
esu2805
Level 1

02-08-2019

Hi, did you get any solution to this? We are also getting these json related errors in the console in 6.5.

Avatar

Avatar
Give Back
Level 1
caraujo_ec
Level 1

Likes

2 likes

Total Posts

6 posts

Correct Reply

0 solutions
Top badges earned
Give Back
Boost 1
View profile

Avatar
Give Back
Level 1
caraujo_ec
Level 1

Likes

2 likes

Total Posts

6 posts

Correct Reply

0 solutions
Top badges earned
Give Back
Boost 1
View profile
caraujo_ec
Level 1

09-06-2020

Hi, has anybody found a workaround for this? (I am using 6.5.4)

 

Same error, it works in author, and in publish I get a 404 (hitting the instance directly).

Avatar

Avatar
Give Back
Level 1
caraujo_ec
Level 1

Likes

2 likes

Total Posts

6 posts

Correct Reply

0 solutions
Top badges earned
Give Back
Boost 1
View profile

Avatar
Give Back
Level 1
caraujo_ec
Level 1

Likes

2 likes

Total Posts

6 posts

Correct Reply

0 solutions
Top badges earned
Give Back
Boost 1
View profile
caraujo_ec
Level 1

09-06-2020

This other post proposes a workaround to make the contexthub.kernel.js show up in publish instances.

 

It worked for me, probably it can help somebody else as well.

 

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/contexthub-kernel-js-404-o...