If the HTML page loads but styling, scripts, or images do not, inspect the failed asset requests individually.
- Use browser developer tools to identify the exact asset URLs and their HTTP status codes.
- For 404 responses, confirm the files exist in the expected document root and that URL paths match filename capitalization.
- For 403 responses, review permissions and access-control rules.
- On HTTPS pages, check for assets still requested over HTTP because browsers may block mixed content.
- If a migration or domain change occurred, verify that the application no longer generates URLs for the old hostname or path.
- Clear browser, application, and CDN caches after correcting URLs.
Do not change DNS if the main HTML page already reaches the correct server and only individual asset URLs fail.
