Issue with page editing in Kentico 13 test environment

Tameside MBC Development asked on August 2, 2024 07:39

I'm using Kentico 13.0.142, and am having issues when editing pages. When I go into the admin site and click a page in the pages menu, and the 'Page' tab, none of the styles, scripts or images load. So the page's unstyled content appears, but nothing else. The console shows 404 errors for a lot of scripts, styles and images, including the page builder ones.

When loading the front end on the test server, that works without issues, and loads styles, scripts and images as expected.

It's a new website, so we don't currently have a live version, but this issue doesn't occur locally. If I run both the admin and front end sites from Visual Studio, then everything loads as expected for the page editing, it's only on our test server that there's an issue.

It was working a week ago, and we have obviously been making changes to set the site up, but nothing that I can think of that would cause this issue. There's no errors showing up in the event log either, so I've not got much to go on.

It has very similar set up to a site being hosted on the same server without issues, so I'm really confused.

Any help would be much appreciated.

Recent Answers

Juraj Ondrus answered on August 2, 2024 07:51

what is the difference in the projects and environments? This sounds like some security setting is blocking the communication or loading of the resources between the admin app and front end app. It could be a firewall, gateway, proxy or it could also be some custom CSP/CORS settings.

0 votesVote for this answer Mark as a Correct answer

Tameside MBC Development answered on August 2, 2024 10:32

As far as I can see there's no difference between the environments, apart from one running on localhost and the other on our development server. We also have another instance of a Kentico site on that server with very similar settings, and that runs without issues.

Could the fact there are 2 Kentico instances running on one domain be an issue?

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on August 2, 2024 10:33

There must be set something differently - it can be also in the project configuration - CSPs, CORS, etc. or firewall rules. You can run as many instances of Kentico on one server as you want - as soon as they are running on separate IIS sites.

0 votesVote for this answer Mark as a Correct answer

Tameside MBC Development answered on August 5, 2024 10:17

After the comment about the separate sites, I thought it may be an issue with the site being on the same site as another Kentico instance. But after adding it to another server, it still has the same issue. There is another site with almost the same settings, working on the same server, so I don't think it's a firewall or configuration issue. Is there any way to check why there are 404 issues in Kentico? There's nothing in the event log to suggest why it may be happening.

0 votesVote for this answer Mark as a Correct answer

Tameside MBC Development answered on August 5, 2024 15:01

I've logged this with support, but have done some further research into this whilst waiting for their reply.

It appears to be an issue with Kentico using cmsctx URLs instead of proper URLs in the iframe. If I compare the code in the local environment to the test one, the local has a proper URL for images, scripts and stylesheets, the test has cmsctx URLs.

A good example is the header image:

Local: /img/header/logo-home.png Test: /cmsctx/pm/bd6edaaf-ff69-4e53-a252-6a1d567c849e/culture/en-GB/wg/bf922dd8-6c74-4dc6-a435-cca41fd94b27/readonly/0/ea/1/h/54116ffcb9512489d8ba75a9adadfc52e3963281189fd4b2a1e0ce296034e37f/-/TSCP/img/header/logo-contact.png?uh=b3c192a550ffebab0f664d7d8496201d16227d5202f1ede9bd142741fee49a3f&administrationurl=https%3A%2F%2Fdevserv04.tameside.gov.uk%2FTSCPAdmin

If I change the URL in dev tools to '/TSCP/img/header/logo-contact.png', which is the actual URL, then it loads as expected, this is the same for the css and js files, so it seems that Kentico is using the wrong URLs for the files. I'm not sure if this sheds anymore light on the problem.

0 votesVote for this answer Mark as a Correct answer