The iPhone app has an option to "restart" a service plan. Can anybody tell me where this is located in the portal? I can't seem to find it.
Thomas Woelfer's questions
I have a windows VM and update management configured. The machine is off most of the time. However, when i need it, i don't want to wait for updates to be installed. Thus, i configured a schedule in update management, so that updates are installed every day at night. (When the machine is normally turned off.)
I was expecting for update management to boot the machine in order to install updates and turn it off after updates have been applied. This, however, doesn't seem to happen.
Am i doing something wrong? Should the machine be turned on for updates? (if update management can't do this: is there another way to do this?)
i'm trying to use the recently announced (in preview) managed certificates for azure app service. one of the limitations is, you can't get one for naked domains. eg.: you can get one for www.domain.com, but not domain.com.
in my wb.config, i'm redirecting from 'naked' to 'www' anyway using rewrite rules, so beeing limited to 'www' is not a real problem. However, as the redirect takes place at the web.config level, that is, after the request has hit the webserver, this is too late: when 'domain.com' gets hit and tried to redirect, the browser has already seen the insecure connection to the naked domain (depending on browser) will display a warning page.
so how is one supposed to do deal with the "naked" domains? No more redirects at all? Or are there other methods to do this besides web.config configurations? i did look, but did not find anything.
I have an azure web app (S2 app Service plan) that is set to autoscale but has a min instance count of 1. As it mostly idles, the real instance count also is 1 almost all of the time.
Last week "something" happened and the site was no longer available. Every request was answered with http status 500. This went on for about 10 hours, and all of a sudden the site was available again. I did not change anything a few day prior to the error condition, nor did i do anything to make the site come back again.
I started a support reuqest for that and a support engineer has been looking into this. According to him the reason for the problem was:
the root cause is pointing at the Windows Process Activation Service, which was unable to run the process related to your application and the platform was unable to recover it in the specified time Frame
Given that i have no way to configure WPA, i assume this to be a problem with the platform. The support enginneer confirmed.
I think this means that azure should deal with a state like this and do whatever is necessary to bring the app back up again. As it took 10 hours for the service to come back online, i assume this happened by chance and azure has not done anything here. Should i post a bug report concerning this incident? (The support engineer isn't really helpful here...)
Also, the support engineer insists that having more than one instance would have solved the availability problem, because
instance so I can confirm that the redundancy failover option in this scenario would be for you to scale out the site to a minimum of two instances. This way, if one of the instances is unavailable, the second one would take over.
i think this simply cannot be correct because the web app was reported as "healthy" by azure and did respond to request, albeit with status 500.
Would, in this case, azure really send traffic only to the instance that was not returning status 500? And also, given that i do not know what caused the WPA problem in the first place - is it not possible the exact same problem would have also turned up with the second instance?