Skip to main content

Accessing Load Balanced Content Delivery Servers

One of the most common issues that arise on load balanced content delivery servers, is that there is a problem only with one of the servers. But troubleshooting this should be easy if you follow one (or in my case, all) of the following three options.

1. Set Http response headers for each content delivery server

Within IIS, at the root server node, choose "HTTP Response Headers". From Actions, add a unique value for each of your servers. For example

Name      Value
x-s            01
x-s            02
x-s            03


Now when you bring up your webpage, you can go to Chrome developer tools and find the x-s value in the response headers section as shown in the image below



2. Add the below line (above the </body> tag) to your default layout (master page) so that all pages on your website inherit it.

<!-- Server MachineName = @HttpContext.Current.Server.MachineName -->

Now, when you bring up your webpage, right click on the page and choose "View page source". Then scroll down to the bottom of the page (by clicking Ctrl + End) and you should see the name of the delivery server that is serving up the web page.

3. In your <Site> node of your website (withing the App_config folder), add the name of each of your delivery server to the hostname (names are pipe delimited here).
For example if your CD server name is xxxcd01
then the hostname value on CD1 would be
hostName="yourwebsite|xxxcd01"
Similarly set this on other CD servers.
ie: hostName="yourwebsite|xxxcd02"
     hostName="yourwebsite|xxxcd03"

Lastly make sure that you have added a hostname binding to your website


Now, you should be able to browse directly to your content delivery server by going to http://xxxcd01

Following the above has helped me troubleshoot a ton of issues and I hope it helps others as well. Happy Sitecoreing!



Comments

Popular posts from this blog

Using Okta Authentication for a Sitecore client site

I recently had a project where we had to add a new Sitecore site to an already multi site Sitecore 8.2 Update 7 instance. This new site had to integrate with Okta to manage user authentication. I found many articles online that integrated Okta and Sitecore's admin interface but I could not find one that just integrated Okta with a client Sitecore site. My first step was to use Okta's available ASP.NET MVC projects on their Dev site and test them out. This worked very well with the first Authenticated method I tried which was WS-Fed. But when I tried to use the same authentication method with a site in Sitecore I got errors in my logs like the following: Sitecore.Security.Principal.SitecoreIdentity does not contain a definition for Claims Claims are available in HttpContext.User.Identity but not in Sitecore.Security.Principal.SitecoreIdentity, and since we are using a Sitecore site we could not read the claims. I tried to make claims work in Sitecore using various online a

Un Lock Sitecore admin account

There are times when you - Upgrade Sitecore locally - Restore databases in your local Sitecore instance. And you are no longer able to login to the Sitecore admin interface with the default admin username and password b. When this happens you can unlock the Sitecore admin account and reset the password back to b. To do this copy this aspx  file to your Website\sitecore\admin folder (and overwrite existing file) Next make sure your local web.config (in the root Website) folder has the following settings minRequiredPasswordLength="1" minRequiredNonalphanumericCharacters="0" Lastly go to the following page https://YourSitecore.com/sitecore/admin/unlock_admin.aspx And click the Unlock Administrator button. That's it, you can now login to your local Sitecore instance. Happy Sitecoreing!

Sitecore media RequestExtension for images and pdfs

On your Sitecore site what is the media file extension you see? If you see .ashx for all your media (images, pdfs) read on. Ideally the IIS application pool for your website should be configured to use Integrated mode instead of classic mode. If that is the case, there is one default Sitecore 8 setting that you should change in your Sitecore.config   FROM: <setting name="Media.RequestExtension" value="ashx"/> TO: <setting name="Media.RequestExtension" value=""/> This configures Sitecore to use the original file extensions rather than .ashx extension. So images would be jpg, gif, png's while pdfs would have the pdf extension. I also notice that Sitecore themselves have this configured on their website, so we should be good making this change. There are multiple benefits to the end user. They know the file types of media like pdfs before clicking on the download link CDN have cache settings that will be honoured