How do I ... Determine which Web Server I am Accessing?
Rarely, a change will be published but seems to only appear sometimes. In these cases, a cache expiration problem is likely.
First, open an incognito or private window and navigate to your launched website page or a stage version of your page if you haven't launched.
Second, try a different browser.
Three, try other devices. Cell phones are especially good because they tend to use a variety of different networks.
Fourth, republish the page(s) in question. Publishing the page again should expire server caches and give the server stack another change to fix the problem. Remember that although publishing usually happens in a minute or less, it can take more than a few minutes and in some cases if a lot of content has been published, much longer.
Finally, if you are convinced that the behavior is wrong, affects more than one device, and can't be fixed by republishing — you'll need to determine which dispatcher each desktop computer is accessing. Create a new Ensemble web support ticket that tells us what page you're on, how we can tell the correct appearance from the wrong appearance, and which dispatcher(s) is (are) not updating.
1) Open the page in question in the Google Chrome browser
2) Right-click or control-click on the page to bring up the developer inspector
3) Click on the tab called Network
4) Reload the page
5) The top item in the list of assets should be the page. It may end in .html or it may just represent the URL in the browser bar. Click on that item.
6) In the panel which opens to the right, you'll see a field label that read "X-RouteInfo:" make a note of the name. It will be something like cmsw-prod-02. The 02 is the number of the dispatcher.
7) Although this is all we need to know to troubleshoot the problem, dispatchers 01 and 03 point to publisher 02 (cmsa-prod-02) while dispatchers 02 and 04 point to publisher 03 (cmsa-prod-03). cmsa-prod-01 is the authoring environment.