404 error when loading the OCE Site URL
(Doc ID 2745964.1)
Last updated on MARCH 22, 2024
Applies to:
Content and Experience Cloud - Version 20.4.2 and laterContent and Experience Cloud Service - Version 20.1.2 and later
Content and Experience Cloud Classic - Version 19.3.2 and later
Information in this document applies to any platform.
Symptoms
After migration of "SiteA" from UAT to Production, OCE URL "https://<instance_name>.ocecdn.oraclecloud.com/site/SiteA" renders a blank screen and the browser console outputs:
Status 404 returned from /_cache_da63/structure.json with response:
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.</p><p>If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.</p><p>If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address
Changes
In UAT, the site name was "SiteAB".
Site is renamed to "SiteA" and moved to Production using OCE Toolkit.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |