Access Denied – HTTP 403 Error Post Login<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } Issue After logging in, the user encounters Access Denied – HTTP 403 error on the webpage.If the user clears everything after / in the URL and refreshes, they are redirected to:<instance_name>.service-now.com/now/nav/ui.. Cause: This issue is commonly observed when the system property glide.product.image.light contains an invalid or corrupted value.Typically, this value points to an image attachment (example: 4579060c1bc3911052b5b912cd4bcbfa.iix).During clone operations, the referenced image file may not be copied from the source instance, leading to a broken property value. Resolution Log in to the affected instance with admin rights.Navigate to System Properties → search for glide.product.image.light.Check the property value:If set, clear the value and Save.Refresh the login page and retry access. Note: If the customer requires the product image, they can re-import the file from a working instance and update the value of the property.In most cases, simply clearing the property resolves the issue. ✅ Best Practice:Always validate system properties post-clone, especially those referencing attachments or images, as these may not always replicate properly.