Expand my Community achievements bar.

Applications for the 2024-2025 Adobe Experience Manager Champion Program are open!
SOLVED

Contexthub.kernel.js 404 on publish 6.4

Avatar

Level 2

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,

1 Accepted Solution

Avatar

Correct answer by
Level 2

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 !

View solution in original post

5 Replies

Avatar

Level 2

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

Avatar

Level 10

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.

Avatar

Correct answer by
Level 2

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 !

Avatar

Level 10

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

Avatar

Level 1

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