-
“Could not resolve host: nodejs.org” when setting up XM Cloud locally
I’ve recently ran into this issue when setting up a XM Cloud development environment locally: This happens when the docker container cannot resolve DNS due to a network issue. To test connectivity from inside a container, run: Possible solutions There are different reasons why Docker might not be able to resolve DNS: A) Windows Firewall…
-
Customizing Headless Proxy Output Caching
When building a site on Sitecore Headless / JSS you’ll eventually end up hosting it on a Headless Proxy Node instance. The Headles Proxy will perform server-side rendering of the page HTML for initial requests i.E. when you hit F5 (browser refresh). Subsequent requests are then usually rendered in the browser. So far so good.…
-
Handling Analytics Processing Issues
Recently, authors were reporting that no more Analytics data was being displayed since a certain date. When analyzing the logfiles of the processing/reporting server, there were many of these entries: Exception: Sitecore.Xdb.Processing.Queue.ProcessingPoolException Message: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The reason for…
-
Santa’s little xDB Helper
Sorry for the xmas pun but hey, it’s December. Back to topic. Debugging xDB issues on a remote environment can be very difficult. Is the MongoDB connection OK? Is tracking configured correctly? Are contacts being created and identified? Is my data pushed to the correct places, when my session ends? Why is GeoIP detection not working?
-
Things to look out for when setting up xDB
This post highlights some potential pitfalls when setting up xDB on a Sitecore 8.x environment.
-
Why silent saving with a processing server is a bad idea
This post highlights why silent saving, EventDisabler or using BulkUpdateContext can lead to inconsistent data on a multi-CM environment i.E. when using a processing server.
-
Using IP Geolocation and SSL on Azure
I want to share some lessons learned from a recent migration of a Sitecore infrastructure to Azure. If you are running a load balanced environment over SSL and relying on IP Geolocation then you need to look out for the following gotchas: