locked
CDN Endpoint not working anymore RRS feed

Answers

  • Hi Peter,

    As the source URL http://*storageaccount*.blob.core.windows.net/500/5300032-600.jpg worked fine for you, the problem should be related with the CDN or the network between you computer and the CDN, here are steps for your reference to troubleshoot:
    1.Make sure CDN is righted enabled as http://msdn.microsoft.com/en-us/library/ee795176.aspx

    2.After creating a CDN endpoint, it need some hours to apply, so please wait for some time(no more than 24 hours) to test it again.

    3.If after 24 hours, CDN still fails but original storage works, please check the internet routing from the your end to the CDN by:
    ping *id*.vo.msecnd.net to see if it can be resolved
    tracert http://*id*.vo.msecnd.net/500/5300032-600.jpg to see how the request will be routed
    4.Make sure IE cache is cleared.
    5.Test from a different machine.
    6.Check the origin to look for any obvious problems.  Look for storage analytics logs.
    7.Test a different geographic region.  Like test from an Azure VM in a different geographic region.

    if from above, there is no obvious clue on the CDN connectivity, please create a support ticket from your Azure management portal, then support team in Windows Azure will assist you quickly.

    currently new generation of CDN is hosted by Verizon EdgeCast, then if the problem CDN is related with EdgeCast provisioning, Azure support team will involve EdgeCast to resolve very soon. if you are using elder version of Azure CDN, then azure support team could directly troubleshoot and fix. by the way, CDN created from azure management portal after April 2nd, 2014 should be all from EdgeCast.

    let me know if there is any question.

    Jian Wu

    Monday, April 28, 2014 6:46 AM

All replies

  • I've got the same problem. Also I created a new one about 14/16 hours agour and it doesn't work.

    Best regards,

    Thursday, April 24, 2014 11:12 AM
  • Hi Peter,

    As the source URL http://*storageaccount*.blob.core.windows.net/500/5300032-600.jpg worked fine for you, the problem should be related with the CDN or the network between you computer and the CDN, here are steps for your reference to troubleshoot:
    1.Make sure CDN is righted enabled as http://msdn.microsoft.com/en-us/library/ee795176.aspx

    2.After creating a CDN endpoint, it need some hours to apply, so please wait for some time(no more than 24 hours) to test it again.

    3.If after 24 hours, CDN still fails but original storage works, please check the internet routing from the your end to the CDN by:
    ping *id*.vo.msecnd.net to see if it can be resolved
    tracert http://*id*.vo.msecnd.net/500/5300032-600.jpg to see how the request will be routed
    4.Make sure IE cache is cleared.
    5.Test from a different machine.
    6.Check the origin to look for any obvious problems.  Look for storage analytics logs.
    7.Test a different geographic region.  Like test from an Azure VM in a different geographic region.

    if from above, there is no obvious clue on the CDN connectivity, please create a support ticket from your Azure management portal, then support team in Windows Azure will assist you quickly.

    currently new generation of CDN is hosted by Verizon EdgeCast, then if the problem CDN is related with EdgeCast provisioning, Azure support team will involve EdgeCast to resolve very soon. if you are using elder version of Azure CDN, then azure support team could directly troubleshoot and fix. by the way, CDN created from azure management portal after April 2nd, 2014 should be all from EdgeCast.

    let me know if there is any question.

    Jian Wu

    Monday, April 28, 2014 6:46 AM
  • Yes, I did all of those things before I contacted microsoft support on friday afternoon.

    The problem is now solved and it was a problem with EdgeCast.

    From their email:

    ---
    Thanks for waiting. Upon investigating further, it seems the account did not populated on Application layer, in which explain the issue you saw. We manually pushed the configuration.

    The fix will take about an hour for propagation to complete across our network
    ---

    /Peter Larsson


    /Peter Larsson

    Monday, April 28, 2014 8:05 AM
  • I have the same problem. Created CDN endpoint more then 24 hours ago but still blob is inaccessible (404). Tried from 1 computers on different networks. And I can't issue a support ticket because it says I have only billing support option. What can I do?
    Friday, October 17, 2014 12:43 PM