I have an Umbraco 8 application v8.14.1 which is running on Azure and is setup to run as Admin and Public instances using 2 App Services.
Admin is the master instance and used to make any CMS content changes.
Public is purely used to serve content.
I have configured these as Load Balanced Azure Web Apps using the following documentation - https://our.umbraco.com/Documentation/Fundamentals/Setup/Server-Setup/Load-Balancing/azure-web-apps-v8
Everything was working correctly for several months, I make a change in the Admin backoffice and this would be visible in the Public site within a few seconds.
However, all of a sudden this stopped working and changes made in the Admin backoffice would not be visible in the Public site, even after a couple of hours.
I had to clear all of the caches using Diplo's God Mode, make a new content change and this correctly displayed on the Public site.
My question is, what went wrong and is there any way to stop this from happening?
The logs did not show any errors.
Any help would be greatly appreciated.
Related
I have one Azure app service,where multiple (web app)app services with different names are running.
I have to modify already implemented cookie banner which says “We are doing ....”
The banner is showing when website load. From browser, After doing “F12” I can see, where are the text written.However, when checked the source code from Visual Studio, I can’t find the text ( that is, Checked in “Index.cshtml” page from the code. ). Searched the text in entire solution as well.
Is it somewhere implemented in App services?, so that it will be visible for different applications “Index.cshtml” page load? Or am I missing something?
Note, as per my previous on prem application, it should be implemented in the code itself. Quite unsure,why am I unable to find this.
Please help.thanks.
I am launching a new redesigned website on windows hosting. I am wondering what is the best way to launch this new website without having any downtime on the existing one?
MY only fear is having a user go to visit a page and it's not there or the supporting files are not uploaded yet.
One of the simplest ways to handle this is to put a load balancer or proxy server in front of the application server. Then set up another application server with the new code. Once it is ready, you can change the proxy server to point to the new application server with the new code. Once you are sure nobody is using the old application server, you can shut it down. This, of course, relies on your ability to get that setup in place. If you are on a budget, you might be able to do it all on a single box. For instance, you could use nginx as a reverse proxy to your application on the same box. Getting that in place could potentially cause a tiny window of downtime - not sure if that's acceptable. Then you might be able to set up the new application on the same box with a different port - again, I'm not sure if that would work for your setup. Anyway, the reverse proxy approach is a pretty common one, and one of the great reasons for deploying to the cloud. You only pay for the short period of time when you need both boxes.
You should make sure that your new website launches all at once and that you set up the proper redirection rules for all previous pages. Once you are launching the new website, pick a time at night where you have low traffic volume, and simply upload all the new code at once to the webserver. This eliminates the fear you have of the "supporting files not uploaded yet". One of the key things to do is make sure all your old pages redirect and map over to new pages on the site just in case anyone clicks into your site using external links.
Two good resources to read:
http://www.rise.net/blog/ideal-way-launch-website-rebrand
http://googlewebmastercentral.blogspot.com/2008/04/best-practices-when-moving-your-site.html
The best methos is to upload the site via FTP, and if you have RD access to login into the Windows server and to copy the new site for a few seconds. In this way you will not have any downtime as when you directly upload the site via FTP.
I inherited a mess of servers which host multiple applications on IIS6, protected by R6 SiteMinder. The environment is soon going to R12, and we have also received some new servers with IIS7.5. (Lots of change, all within the next 60days.)
I am not an expert, and so am having trouble with some of the more detailed steps of configuration. Thus far, on the new server I am able to create and apply SiteMinder to the DefaultWebSite (and everything contained within), and any custom Sites that I create. Unfortunately in our environment, it is already set up with a handful of applications that live underneath DefaultWebSite, only some of which we desire SiteMinder protection.
In IIS6 I was able to simply add a site to SiteMinder authentication by applying the ISAPI6WebAgent.dll in the wildcard mappings. In IIS7.5, this does not seem to work. I follow the specific details in the installation manual and it seems like it is either an all-or-nothing situation: everything under DefaultWebSite is protected, or nothing is.
This will cause a SIGNIFICANT amount of additional work in my environment (and it also means upgrading in place is not possible, so all applications that require SiteMinder authentication will need to be migrated in the next 60 days.) Is there ANY workaround for this? Google has not provided me with any solutions, and my SiteMinder team is claiming "it is no longer possible with IIS7.5" to keep the environment the way it is currently set up.
Any and all help appreciated.
For those that care, if you are running under an Integrated App Pool, you can simply add and remove the SiteMinder modules to control which sites are protected by SiteMinder. This DOES work on apps below a virtual directory - and using the config files you can both inherit protection by default, or have it unprotected and add it later by simply "Configure Native Module" and adding it back.
I have recently installed a website project on Azure and that was relatively easy to do thanks to great docs online. We are having a problem with the back office (admin) login though, it's a bit strange, as it didn't happen straight away, I shall elaborate....
When I go to http://www.keelycattschoolofdance.co.uk/umbraco/ it takes me to the login page, which seems fine.
(The url at this point becomes www.keelycattschoolofdance.co.uk/.../login.aspx)
I then login, which works and it starts to display the admin panels but then bounces back to the login and the URL becomes www.keelycattschoolofdance.co.uk/.../login.aspx
I am running this on Azure using the Accelerator, latest version of Umbraco and using SQL CE 4.0 rather than SQL Server.
has anyone seen this before?
Please let me know if you need more information, I shall respond :-)
Thanks in advance
Nick
It sounds like it may be a Session error. This is a problem for Azure and Umbraco because Azure uses round robin load balancing.
The normal way of setting up an Umbraco site using the accelerator would be to have a separate session DB where the shared session state is stored.
Make sure you are using this accelerator for Umbraco on Azure as it's the latest and best.
http://waacceleratorumbraco.codeplex.com/
We have several large production sites using this and I can confirm they all work fine (including the backend editing environment).
Things to watch out for are that you need to follow the instructions closely as they are easy to get wrong :-)
Make sure you don't have dashes in your db names as this makes things go wrong as well.
Finally if you are using more than one web role the Umbraco preview can sometimes yellow screen, as the preview XML may not be on the server that gets to the preview request. This is again because of the round robin load balancing.
So I have a site setup on a server. It has been working for ever. All of a sudden it stops working. I tried going to it even by IP. It just says, "Under Construction..
Under Construction
The site you are trying to view does not currently have a default page. It may be in the process of being upgraded and configured..."
I check to make sure it was pointing at the right virtual dir and that the default page was set in the documents list. The default page does exist in the dir too....
Nothing has been changed via code. Nothing has been altered on the server. I have a bunch of other sites running on the same server and they are all coming up. Just wondering if there was something that may have happened or overlooked. Any thoughts or ideas?
Thanks a million.
Double check your bindings are set correctly. Perhaps a new site was created which conflicts with the bindings of your site?
Edit
Make sure .net is set to the right version. I've seen where pages are not served up when the web is set to 1.1 on a 2.0 site.
Also does the site work locally on the box? Have you ruled out firewall issues / changes or other network related elements.
It sounds like your request is being handled by another IIS site. Make sure that the host header is set correctly.
With your comment, the "Bad Request" error means that the default web site was handling the request. There are a couple of things you can check:
If this is not the site that you expected to serve your app, then you still have a website identity issue.
If your app is hosted on the default web site, then make sure that the default document is set correctly.
Also make sure that you don't have a file named "app_offline.htm" in your app's root.
Well we rebooted the server and now it works again. I guess I should have tried that in the first place. It was just odd that all the otehr sites were working. Anyway thanks for suggestions everyone.