We have setup our website to have a seperate backoffice on one app service and the frontend on another. For the most part this works well, but there have been some instances where publishing content in the back office isn't replicated to the frontend site (this content looks fine in the backoffice).
Has anyone come across this issue, and do they have any suggestions - it doesn't do this all the time, which makes it even more frustrating.
We have followed all the latest guides on setting up the load balanced environment as outlines here:
Also is the content manually published or is it scheduled? If it's scheduled, make sure you have your application URL configured correctly.
If it's manual, I've also seen the same issue on a few v7 sites (7.6-7.10ish). The work around was to restart the production instance site which was annoying, but did work. Occasionally I think we even needed to also clear out the umbracoCacheInstructions table.
I could never figure out exactly what the issue was. From the logs it looked like Azure did something to make the site think it was shutting down, and Umbraco would start the process, including stopping the cache instruction check jobs. But the site didn't actually shut down. And with the checks not happening, any new changes didn't make it to the production servers.
It seemed to get better after we updated the site to the later versions of v7, but I was never convinced that totally fixed it. I haven't done too many sites with v8 and so I haven't noticed the issue on that version.
The version we're using is 8.6.4. Content can be manually published or scheduled, either way the frontend doesn't update. As you mentioned an App Restart fixes the issue, but over time the issue comes back again.
Load balancing in Azure App Service Environment publishing issues
Hello,
We have setup our website to have a seperate backoffice on one app service and the frontend on another. For the most part this works well, but there have been some instances where publishing content in the back office isn't replicated to the frontend site (this content looks fine in the backoffice).
Has anyone come across this issue, and do they have any suggestions - it doesn't do this all the time, which makes it even more frustrating.
We have followed all the latest guides on setting up the load balanced environment as outlines here:
https://our.umbraco.com/Documentation/Getting-Started/Setup/Server-Setup/Load-Balancing/flexible-advanced
https://our.umbraco.com/documentation/Getting-Started/Setup/Server-Setup/azure-web-apps
https://our.umbraco.com/documentation/Getting-Started/Setup/Server-Setup/Load-Balancing/
Any help/insight would be appreciated.
Thanks
Can anyone help on this?
What version of Umbraco?
Also is the content manually published or is it scheduled? If it's scheduled, make sure you have your application URL configured correctly.
If it's manual, I've also seen the same issue on a few v7 sites (7.6-7.10ish). The work around was to restart the production instance site which was annoying, but did work. Occasionally I think we even needed to also clear out the umbracoCacheInstructions table.
I could never figure out exactly what the issue was. From the logs it looked like Azure did something to make the site think it was shutting down, and Umbraco would start the process, including stopping the cache instruction check jobs. But the site didn't actually shut down. And with the checks not happening, any new changes didn't make it to the production servers.
It seemed to get better after we updated the site to the later versions of v7, but I was never convinced that totally fixed it. I haven't done too many sites with v8 and so I haven't noticed the issue on that version.
Hi Kevin,
The version we're using is 8.6.4. Content can be manually published or scheduled, either way the frontend doesn't update. As you mentioned an App Restart fixes the issue, but over time the issue comes back again.
Thanks
is working on a reply...