Yesterday Azure Frontdoor was down for 45 mins, and i could not access my webapps.
Can I put something in front of my Azure Frontdoor to handle this downtime ?
One of the workaround you can follow to resolve the above issue,
As of now i have not faced this issue .
Please Make sure that you have enabled below configuration in your routing rules .
Also in App service configuration by default its of , On this feature for redirect all HTTP traffic to HTTPS . Post that restart your webapp and run.
NOTE:- In backend pool there is configuration Priority and weight which have default value 1 and 50 ,Try to increase the weight as well which has max limit upto 1000.
For more information please refer the below links for Azure front door configuration:-
MICROSOFT DOCUMENTATION|CREATE FRONTDOOR FOR YOUR APPLICATION.
BLOG| Steps to implement Microsoft Azure Front Door Service.
I had the same issue and ended up using Application Gateway when outages are happening. Depending on how you do this it can be manual or automatic.
Hope this helps!
Related
I have an Azure App Gateway connected to 3 different App Service apps all running as part of the same App Service Plan (3 different back-end pools). In the Backend Health section of the AG, one of the app/pool is constantly flipping between Healthy and Unknown states. I have checked the entire network configuration according to this article and everything seems to be configured properly.
I have configured ip restrictions on the app services according to this article specifying the subnet the AG resides in as allowed. I have also temporarily allowed my ip address and every time the health for the 1 app goes to "unknown", I am still able to access the app service using its native .azurewebsites.net url locally on my machine.
Any ideas how I can troubleshoot this?
Please check if below points help to work around the issue.
As a workaround initially,try to restart the application gateway after the backend is deployed .
Also check this discussion on github issue
Sometimes Appgateway will cache the response indefinitely and the fix
maybe "Dynamic DNS" which ensures that the "no existing domain" is not
cached on the Appgw.Also check for the fix using v16.
Also check this > similar issue which says to use custom domain names as the request looks for some domain.
Technical Stack
Imperva WAF
Angular 7
Azure WebApp
We are planning to deploy Angular 7 build in Azure WebApp and will add custom domain to it which will be behind Imperva WAF. WAF will make sure that only whitelisted IPs can access site. WebApp gets WAF IPs instead of client IPs.
In this case, we are not able to trace usage reports for given client IPs. So as per suggestion, we want to add these data into App Insights to make sure we have all to get the usage reports.
How to implement this? Do we have anything to write custom code to implement this?
Please correct me if I misunderstand you.
There is application insights sdk, you can take use of it like use methods trackTrace / trackEvent to add your custom log.
You can also search by google, there're lots of examples of using application insights for logging with code.
Hope it helps.
Hi, I am trying to configure a basic traffic manager on my azure account. But I always got 404 not found when I using the traffic manager URL.
I have two app service for the TM endpoints:
1. xxxus.azurewebsites.net
2. xxxeu.azurewebsites.net
TM Url is:
xxxtm.trafficmanage.net
I was able to use www.whatsmydns.net to check what the tm is heading to.
But when I use the TM url, I got this:
Did anyone has the same issue? Looking forward to your help
Thank you
I ran into the exact same thing and just found the solution - the app service plan needs to be at least a standard SKU. I was using a free tier, and that was causing my 404.
From Microsoft's Traffic Manager documentation:
Only Web Apps at the 'Standard' SKU or above are eligible for use with Traffic Manager. Attempts to add a Web App of a lower SKU fail. Downgrading the SKU of an existing Web App results in Traffic Manager no longer sending traffic to that Web App.
Currently, you could not add web apps from different subscriptions to the same traffic manager configuration since It is not possible to use Web Apps from multiple subscriptions with the same domain name. Refer to this. You can check this on your side. If so, you can remove one website from your endpoint, then add the website to the same subscriptions.
Moreover, the 404 error always happen due to the domain name could not be resolved by its IP address. It may be one of the following reasons:
The custom domain configured is missing an A record and/or a CNAME record.
The browser client has cached the old IP address of your domain. Clear the cache and test DNS resolution again. On a Windows machine, you clear the cache with ipconfig /flushdns.
You can follow the quickstart to create a Traffic Manager profile, then follow this to verify your traffic manager settings.
I encountered similar issue. My problem is one of my app service is a free tier, so I scaled it up to standard one. And delete my traffic manager and reinstalled and add the service endpoint again, the issue gone.
It's strange. Nslookup will take you to the right web app but the browser will show 404. Changing the app service plan to 'Standard' SKU fixed it for me.
We are trying to migrate our ASP.NET web apps to an Azure VM. We have about 5 apps under our website, but we need to do these one by one. The problem is when we migrate one app to an Azure VM IIS, we need to maintain the URL and not disturb the 4 remaining web apps. Below is an image better explaining what I need to do:
See Image
Notice I need to maintain the original URL (https://www.site1.com/App1-1) when moved to the Azure VM. We had thought about doing a reverse proxy for that one app, but I think that would put too much extra traffic going back and forth.
I know this is probably not the best way of migrating things to Azure. Refactoring the app is slated for the future. This is a "lift and shift" interim solution. Any suggestions or tips would be greatly appreciated!
You can do something like:
Migrated the app to Azure VM and test it first to confirm it working
Configure the custom DNS entry to point to the app in Azure. You can read more here
https://learn.microsoft.com/en-in/azure/dns/dns-domain-delegation
Switch off the app from the local server once DNS entry in Azure is active.
Migrate other apps
I have created a CDN endpoint at [id].vo.msecnd.net, and I have deployed a production mvc4 cloud service web role.
It has images in a root-level /cdn folder, but I cannot get those images to load via cdn. I can access them via direct URL. For example, this works:
[site].cloudapp.net/cdn/eb303.gif
but not:
[id].vo.msecnd.net/eb303.gif
The cdn endpoint is enabled and set up under the hosted service that the web role is in. The documentation I have been reading indicates that nothing more is required. I am using a bizspark license, but as far as I can tell that should include CDN endpoints.
Is there a step I am missing?
Thanks!
Sometime it may take up to 1 hour before your CDN endpoint is ready to server your content. It does work with any kind of deployment staging or production.
Do you still have the problem? If you still have the problem you may need to contact Azure Support because if you have enabled the CDN, you should be good to go.