XM Cloud: Experience Editor is not working

Jaya Jha
2 min readJul 11, 2024

--

After configuring the local XM cloud environment using Docker, the next step is to check how we can modify a page in the experience editor. However, as usual for me, it’s not functioning here either and I’m receiving the following error.

The remote name could not be resolved: ‘rendering’

As per usual, I conducted extensive research and nothing seemed to work in my case. The solution was actually very simple and minor but took a lot of time to pinpoint. Once again, my colleague Jitender found the solution, saving us both a significant amount of time as we were both struggling with different solutions.

Let’s delve into the solution that proved helpful after much struggle.

Navigate to the ‘docker-compose.override.yml’ file and modify it as per the following screenshot.

We need to add a hostname for rendering. I’m attaching a screenshot illustrating the adjustment we need to make.

save it and again run ./up.ps1 script your experience editor will work this time without any error and you can edit.

I hope this will assist someone who has been struggling with this issue for a long time.

If you’re encountering an initial setup error where it states, ‘waiting for CM’, I recommend checking out my previous blog post, as it may prove helpful.
Waiting for CM to become available | by Jaya Jha | Jul, 2024 | Medium

Happy XM Cloud learning.

--

--

Jaya Jha
Jaya Jha

Written by Jaya Jha

I am a full-stack Web Application Developer with extensive experience in Sitecore Ecosystem .Passionate about exploring cutting edge technologies.

No responses yet