Unpublished welcome page shows instead of published content
Hi,
Apologies if I'm asking a silly or basic question here - I'm quite new to Umbraco v7 (but loving it so far).
I have a new site for a client that's currently partially in UAT (not all content is yet present); they have an existing Umbraco site, based on an earlier version (but still v7). New site version is 7.7.1 (the most current when I started it).
There seems to be an issue where cookies are hanging around after logging in to the backend of the site (the new site is currently on www2.[domain].com, the old one is on www.[domain].com) - sorry I can't share the actual site due to an NDA.
This causes the "no published content" welcome page to show instead of the actual website - the client has to go into Incognito Mode in Chrome (or delete their cookies for the site)
I've confirmed that I can replicate this by logging in to to the backend, logging out, closing the browser completely and then trying to view the site again in the same browser after closing - instead of the home page, I get the "Unpublished content" welcome page for v7.
I can fix this by deleting a cookie called "X-Mapping-[random letters] - after doing this and refreshing the page I get the published content again.
The UAT site is on load balanced servers, configured according to the documentation and using Distributed File Replication but the same issue doesn't seem to be happening on the dev site (which isn't load balanced), so I'm wondering if it's something to do with that.
Is there some way of ensuring this doesn't happen? A configuration setting or something that I'm not aware of?
Some more research indicates that this is actually a cookie set by something called "Stingray Traffic Manager" - is it likely that the configuration issue lies in that rather than Umbraco?
Okay, it isn't to do with the cookie, that was a red herring (it just happens to be a symptom because clearing it forces the load balancer to send users to the server that's actually working).
When I looked at the logs on the second server behind the load balancer (which I should have done before posting) the log file says that Umbraco has no content, so clearly there's something wrong with the configuration here - investigations are continuing (the 2 servers have identical configurations as far as I can see - the only difference is that the other one is the "master" server that will be used for back end functions).
2017-11-22 12:12:57,747 [P3752/D2/T1] INFO Umbraco.Core.CoreBootManager - Umbraco 7.7.1 application starting on [Machine Name]
2017-11-22 12:12:57,762 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Determining hash of code files on disk
2017-11-22 12:12:57,778 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Hash determined (took 8ms)
2017-11-22 12:12:57,825 [P3752/D2/T1] INFO Umbraco.Core.MainDom - Acquiring MainDom...
2017-11-22 12:12:57,840 [P3752/D2/T1] INFO Umbraco.Core.MainDom - Acquired MainDom.
2017-11-22 12:12:57,840 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IDiscoverable
2017-11-22 12:12:57,887 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IDiscoverable (took 48ms)
2017-11-22 12:12:57,887 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IApplicationStartupHandler
2017-11-22 12:12:57,887 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IApplicationStartupHandler (took 1ms)
2017-11-22 12:12:57,903 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IDiscoverable
2017-11-22 12:12:57,903 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IDiscoverable (took 0ms)
2017-11-22 12:12:57,903 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving Umbraco.Core.PropertyEditors.IPropertyEditorValueConverter
2017-11-22 12:12:57,919 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved Umbraco.Core.PropertyEditors.IPropertyEditorValueConverter (took 0ms)
2017-11-22 12:12:57,919 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IDiscoverable
2017-11-22 12:12:57,919 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IDiscoverable (took 0ms)
2017-11-22 12:12:57,919 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving Umbraco.Core.PropertyEditors.IPropertyValueConverter
2017-11-22 12:12:57,919 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved Umbraco.Core.PropertyEditors.IPropertyValueConverter (took 1ms)
2017-11-22 12:12:57,934 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IDiscoverable
2017-11-22 12:12:57,934 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IDiscoverable (took 0ms)
2017-11-22 12:12:57,934 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving Umbraco.Web.Mvc.SurfaceController
2017-11-22 12:12:57,934 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved Umbraco.Web.Mvc.SurfaceController (took 0ms)
2017-11-22 12:12:57,934 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IDiscoverable
2017-11-22 12:12:57,934 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IDiscoverable (took 0ms)
2017-11-22 12:12:57,934 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving Umbraco.Web.WebApi.UmbracoApiController
2017-11-22 12:12:57,934 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved Umbraco.Web.WebApi.UmbracoApiController (took 0ms)
2017-11-22 12:12:59,700 [P3752/D2/T1] INFO Umbraco.Core.DatabaseContext - CanConnect = True
2017-11-22 12:12:59,887 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving Umbraco.Core.Models.PublishedContent.PublishedContentModel
2017-11-22 12:12:59,887 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved Umbraco.Core.Models.PublishedContent.PublishedContentModel (took 2ms)
2017-11-22 12:12:59,965 [P3752/D2/T1] INFO Umbraco.Web.Cache.CacheRefresherEventHandler - Initializing Umbraco internal event handlers for cache refreshing
2017-11-22 12:13:00,200 [P3752/D2/T1] INFO Umbraco.Web.Search.ExamineEvents - Initializing Examine and binding to business logic events
2017-11-22 12:13:00,200 [P3752/D2/T1] INFO Umbraco.Web.Search.ExamineEvents - Adding examine event handlers for index providers: 3
2017-11-22 12:13:00,215 [P3752/D2/T1] INFO Umbraco.Core.CoreBootManager - Umbraco application startup complete (took 2571ms)
2017-11-22 12:13:00,559 [P3752/D2/T10] INFO Umbraco.Core.Sync.ApplicationUrlHelper - ApplicationUrl: https://www2.[domain].com/umbraco (UmbracoModule request)
2017-11-22 12:13:09,403 [P3752/D2/T5] INFO umbraco.content - Load Xml from file...
2017-11-22 12:13:09,403 [P3752/D2/T5] INFO umbraco.content - Loaded Xml from file.
2017-11-22 12:13:09,418 [P3752/D2/T5] WARN Umbraco.Web.UmbracoModule - Umbraco has no content
2017-11-22 12:13:51,262 [P3752/D2/T10] WARN Umbraco.Web.UmbracoModule - Umbraco has no content
2017-11-22 12:15:14,480 [P3752/D2/T5] WARN Umbraco.Web.UmbracoModule - Umbraco has no content
2017-11-22 12:18:01,275 [P3752/D2/T10] WARN Umbraco.Web.UmbracoModule - Umbraco has no content
2017-11-22 12:18:09,416 [P3752/D2/T22] WARN Umbraco.Web.UmbracoModule - Umbraco has no content
Unpublished welcome page shows instead of published content
Hi,
Apologies if I'm asking a silly or basic question here - I'm quite new to Umbraco v7 (but loving it so far).
I have a new site for a client that's currently partially in UAT (not all content is yet present); they have an existing Umbraco site, based on an earlier version (but still v7). New site version is 7.7.1 (the most current when I started it).
There seems to be an issue where cookies are hanging around after logging in to the backend of the site (the new site is currently on www2.[domain].com, the old one is on www.[domain].com) - sorry I can't share the actual site due to an NDA.
This causes the "no published content" welcome page to show instead of the actual website - the client has to go into Incognito Mode in Chrome (or delete their cookies for the site)
I've confirmed that I can replicate this by logging in to to the backend, logging out, closing the browser completely and then trying to view the site again in the same browser after closing - instead of the home page, I get the "Unpublished content" welcome page for v7.
I can fix this by deleting a cookie called "X-Mapping-[random letters] - after doing this and refreshing the page I get the published content again.
The UAT site is on load balanced servers, configured according to the documentation and using Distributed File Replication but the same issue doesn't seem to be happening on the dev site (which isn't load balanced), so I'm wondering if it's something to do with that.
Is there some way of ensuring this doesn't happen? A configuration setting or something that I'm not aware of?
Many thanks!
Chris.
Some more research indicates that this is actually a cookie set by something called "Stingray Traffic Manager" - is it likely that the configuration issue lies in that rather than Umbraco?
Okay, it isn't to do with the cookie, that was a red herring (it just happens to be a symptom because clearing it forces the load balancer to send users to the server that's actually working).
When I looked at the logs on the second server behind the load balancer (which I should have done before posting) the log file says that Umbraco has no content, so clearly there's something wrong with the configuration here - investigations are continuing (the 2 servers have identical configurations as far as I can see - the only difference is that the other one is the "master" server that will be used for back end functions).
2017-11-22 12:12:57,762 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Determining hash of code files on disk 2017-11-22 12:12:57,778 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Hash determined (took 8ms) 2017-11-22 12:12:57,825 [P3752/D2/T1] INFO Umbraco.Core.MainDom - Acquiring MainDom... 2017-11-22 12:12:57,840 [P3752/D2/T1] INFO Umbraco.Core.MainDom - Acquired MainDom. 2017-11-22 12:12:57,840 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IDiscoverable 2017-11-22 12:12:57,887 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IDiscoverable (took 48ms) 2017-11-22 12:12:57,887 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IApplicationStartupHandler 2017-11-22 12:12:57,887 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IApplicationStartupHandler (took 1ms) 2017-11-22 12:12:57,903 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IDiscoverable 2017-11-22 12:12:57,903 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IDiscoverable (took 0ms) 2017-11-22 12:12:57,903 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving Umbraco.Core.PropertyEditors.IPropertyEditorValueConverter 2017-11-22 12:12:57,919 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved Umbraco.Core.PropertyEditors.IPropertyEditorValueConverter (took 0ms) 2017-11-22 12:12:57,919 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IDiscoverable 2017-11-22 12:12:57,919 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IDiscoverable (took 0ms) 2017-11-22 12:12:57,919 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving Umbraco.Core.PropertyEditors.IPropertyValueConverter 2017-11-22 12:12:57,919 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved Umbraco.Core.PropertyEditors.IPropertyValueConverter (took 1ms) 2017-11-22 12:12:57,934 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IDiscoverable 2017-11-22 12:12:57,934 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IDiscoverable (took 0ms) 2017-11-22 12:12:57,934 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving Umbraco.Web.Mvc.SurfaceController 2017-11-22 12:12:57,934 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved Umbraco.Web.Mvc.SurfaceController (took 0ms) 2017-11-22 12:12:57,934 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving umbraco.interfaces.IDiscoverable 2017-11-22 12:12:57,934 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved umbraco.interfaces.IDiscoverable (took 0ms) 2017-11-22 12:12:57,934 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving Umbraco.Web.WebApi.UmbracoApiController 2017-11-22 12:12:57,934 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved Umbraco.Web.WebApi.UmbracoApiController (took 0ms) 2017-11-22 12:12:59,700 [P3752/D2/T1] INFO Umbraco.Core.DatabaseContext - CanConnect = True 2017-11-22 12:12:59,887 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolving Umbraco.Core.Models.PublishedContent.PublishedContentModel 2017-11-22 12:12:59,887 [P3752/D2/T1] INFO Umbraco.Core.PluginManager - Resolved Umbraco.Core.Models.PublishedContent.PublishedContentModel (took 2ms) 2017-11-22 12:12:59,965 [P3752/D2/T1] INFO Umbraco.Web.Cache.CacheRefresherEventHandler - Initializing Umbraco internal event handlers for cache refreshing 2017-11-22 12:13:00,200 [P3752/D2/T1] INFO Umbraco.Web.Search.ExamineEvents - Initializing Examine and binding to business logic events 2017-11-22 12:13:00,200 [P3752/D2/T1] INFO Umbraco.Web.Search.ExamineEvents - Adding examine event handlers for index providers: 3 2017-11-22 12:13:00,215 [P3752/D2/T1] INFO Umbraco.Core.CoreBootManager - Umbraco application startup complete (took 2571ms) 2017-11-22 12:13:00,559 [P3752/D2/T10] INFO Umbraco.Core.Sync.ApplicationUrlHelper - ApplicationUrl: https://www2.[domain].com/umbraco (UmbracoModule request) 2017-11-22 12:13:09,403 [P3752/D2/T5] INFO umbraco.content - Load Xml from file... 2017-11-22 12:13:09,403 [P3752/D2/T5] INFO umbraco.content - Loaded Xml from file. 2017-11-22 12:13:09,418 [P3752/D2/T5] WARN Umbraco.Web.UmbracoModule - Umbraco has no content 2017-11-22 12:13:51,262 [P3752/D2/T10] WARN Umbraco.Web.UmbracoModule - Umbraco has no content 2017-11-22 12:15:14,480 [P3752/D2/T5] WARN Umbraco.Web.UmbracoModule - Umbraco has no content 2017-11-22 12:18:01,275 [P3752/D2/T10] WARN Umbraco.Web.UmbracoModule - Umbraco has no content 2017-11-22 12:18:09,416 [P3752/D2/T22] WARN Umbraco.Web.UmbracoModule - Umbraco has no content
If anybody else comes across this, check that this setting:
directoryFactory="Examine.LuceneEngine.Directories.SyncTempEnvDirectoryFactory,Examine"
Is added to all of your indexers if you're using Examine 0.1.80+ (see https://our.umbraco.org/documentation/Getting-Started/Setup/Server-Setup/load-balancing/flexible#examine-v0-1-80)!
That was a diverting hour or 2...
is working on a reply...