Azure CDN returning 503 error

Question

I have created a CDN endpoint, waited till everything has been setup (propagation of DNS) and it has "enabled" status. But when I would like to reach this CDN endpoint, it keeps returning me a "Service Unavailable" 503 error.

I do not know, what to look, where to look. I was thinking if CDN would work properly I should get exactly what would I get at my hostapp/cdn, as this is default CDN endpoint pointing address.

Do you have any ideas? How to configure Azure CDN to really point to your application? Http 503 error mean that the server (CDN, I presume) is "down". Why? So it seems as CDN would not be enabled, although it says it is ...

Application behind this CDN works normaly and it is in production environment.

CDN Url: az79642.vo.msecnd.net

Answer 1

Hi, first try to wait for more time. It takes time for CDN to be available. In addition, make sure you have a cdn folder in your web role. All contents you wish to push to CDN must be put under that folder. For example, http://name.cloudapp.net/cnd/something.txt is valid, but http://name.cloudapp.net/something.txt will not be served via CDN. Refer to http://msdn.microsoft.com/en-us/library/windowsazure/09e9ab98-e26f-47b3-a1ea-692c103a3e3a#blobs for more information. If nothing works, contact our custom support on https://support.microsoft.com/oas/default.aspx?prid=14234&st=1&wfxredirect=1&sd=gn to check what's wrong with your account.

---

Please mark the replies as answers if they help or unmark if not.
If you have any feedback about my replies, please contact [e-mail].
Microsoft One Code Framework

Answer 2

 

Thank you for your answer. I have waited now for a few days to leave CDN set itself. I understand how Azure CDN should work, that is serve content thru my application /cdn path. But we will agree that I should get the same content what I get thru myapp.com/cdn and az79642.vo.msecnd.net URL, right? But that is not the case there. Is seem like my app CDN IIS site is down.

Many thanks for the support links.

 

Answer 3

Hi,

Yes, it should work. The issue is likely to be something in the CDN provision process. Contact our custom support on https://support.microsoft.com/oas/default.aspx?prid=14234&st=1&wfxredirect=1&sd=gn to check what's wrong with your account.

 

Best Regards,

Ming Xu.

---

Please mark the replies as answers if they help or unmark if not.
If you have any feedback about my replies, please contact [e-mail].
Microsoft One Code Framework

Answer 4

There are two CDN types available now on Windows Azure; One is storage CDN and the second is for the Hosted Service.

It is important to know that this issue has arised with the second one - for the Hosted service.

When the hosted service is deployed to Azure, one must provide it's URL prefix name. This is the URL by which the hosted service is by default addressed to. When the web role is deployed this is also it's default host header name but it's not neccessarily the one that really serves the web role but it is used by the CDN to access it.

And this is what happened in this case.
The web role was configured to accept custom host headers only, the default one was excluded. The CDN role used the default one to access the web role and couldn't.

Solution is to add the correct host header to the web role ServiceDefinition.csdef file.

 

Best regards,

Pu.