Contexthub.kernel.js 404 on publish 6.4 | Community
Skip to main content
Level 2
October 31, 2018
Solved

Contexthub.kernel.js 404 on publish 6.4

  • October 31, 2018
  • 4 replies
  • 3325 views

Hello !

We just pushed live the AEM 6.4 version today - and i noticed an issue with the contexthub kernel js file.

https://www.ourwebsite.com/etc/cloudsettings/default/contexthub.kernel.js is giving a 404 while it was ok on the 6.2.

I tested directly via IP on the publisher (to go without dispatcher)

https://IP_OF_6.4_PUBLISH:5433/etc/cloudsettings/default/contexthub.kernel.js and still the same 404 (so not related to any dispatcher rule)

On 6.2 version - it is served correctly.

http://IP_OF_6.2_PUBLISH:4503/etc/cloudsettings/default/contexthub.kernel.js

Does anyone got any idea of what can be wrong. COde and configuration are stricly the same.

Last addition - the contexthub.kernel.js is served well on the author machine.

It is extremly urgent as we are already live.

Thanks,

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 mlds06

Hello !

In fact just need to Change sling:resourceType from

/libs/granite/contexthub/cloudsettings/components/baseconfiguration

to

granite/contexthub/cloudsettings/components/baseconfiguration

on the contexthub configuration (/etc/cloudsettings/...) did the trick (we were already having the rest).

Thanks a lot for your support

It's now solved !

4 replies

mlds06Author
Level 2
October 31, 2018

Just to add an extra information - here is the sightly line of code we have to include the dispatcher :

smacdonald2008
Level 10
October 31, 2018

ContextHub - as  described in the AEM DOcs - does not appear or work on Publish instances.

Configuring ContextHub

Its a tool used to test personalization on Author instances and like other granite based components - not used on Pub instances.

mlds06AuthorAccepted solution
Level 2
October 31, 2018

Hello !

In fact just need to Change sling:resourceType from

/libs/granite/contexthub/cloudsettings/components/baseconfiguration

to

granite/contexthub/cloudsettings/components/baseconfiguration

on the contexthub configuration (/etc/cloudsettings/...) did the trick (we were already having the rest).

Thanks a lot for your support

It's now solved !

smacdonald2008
Level 10
October 31, 2018

I am still curious - are you trying to use ContextHub on Pub?

February 19, 2024

Hi @smacdonald2008 

 

We can see the 404 in the network tab in the publisher Environment. Can you please suggest on how we can avoid 404 visibility.

 

Note: Modified the resource type on Author then we can't see any error related to context hub in author environment.

 

Thanks in advance