locked
Error 504 Timeout - for CDN RRS feed

  • Question

  • That's how I use CDN to load my files faster. Has added it to my logo and style. When trying to get it through CDN. Then it gives me an error of 504 - Timeout.

    I have through watched content on cloudflare that I have added with cname from xxx.xxx.com to xxxx.azureaage.net.

    The loader who said no files at all.

    I have also tried writing xxx.xxx.com/style/css.css and it also gives 504 timeout.
    Friday, July 7, 2017 10:55 PM

All replies

  • We need the full name of your CDN endpoint and an example URL that illustrates this behavior to investigate further. Also please provide the HTTP response headers that you get back for your example URL. Thanks.
    Saturday, July 8, 2017 1:44 AM
  • Here can u see it.

    Saturday, July 8, 2017 2:51 PM
  • So i have add my site (Url to my site)
    Sunday, July 9, 2017 1:59 AM
  • Your CDN endpoint currently does not point to a valid origin (e.g. your website) and this is resulting in 504s. You currently have your CDN endpoint imgcdnOrdklar2017.azureedge.net pointing to imgcdn.ordklar.dk and also from your DNS provider you have imgcdn.ordklar.dk setup as a CNAME to imgcdnOrdklar2017.azureedge.net. As a result there isn't any origin for the CDN to obtain content from. A request directly to your origin for the same content also results in a 504.

    Monday, July 10, 2017 10:10 PM


  • Its image are from Cloudflare.

    I do not quite understand your message.

    What are you wanting me 100%? Should I make one from imgcdn to my website or what?
    Monday, July 10, 2017 10:50 PM
  • If you want to use Azure CDN with your website, then the origin hostname that you specify for your CDN endpoint must be a hostname that resolves to an IP address for your website. For the following URL: http://imgcdnOrdklar2017.azureedge.net/style/css.css, if the CDN doesn't have this file cached, it will use the origin hostname and origin path you have specified for this endpoint to access this file from your website. With your current endpoint configuration this would result in the CDN using an URL of http://imgcdn.ordklar.dk/style/css.css. As this URL did not resolve to an IP address for your website no content could be retrieved. The origin hostname that you specify for your Azure CDN endpoint must be one that can be used to directly to access your content.

    Tuesday, July 11, 2017 1:48 AM
  • Så det vil sige, at ved Origin path der angiver den fil eller det område, jeg skal have cached? Eller skal jeg gøre det ved oprindelse vært header ?.

    I do not quite understand what you mean with what you write to me?

    Tuesday, July 11, 2017 3:49 PM
  • Both the origin path and the origin hostname are used to specify the location for files that can be cached on the CDN. The origin hostname is a mandatory setting. The origin path is not a mandatory setting. The origin path is used to restrict the content that is available from your CDN endpoint e.g only allow content from a specific directory or to hide the full URL path to your origin. The following are examples to illustrate this for the following file path: https://ordklar.dk/content/StyleSass/custom.min.css.
    1) Allow access from the CDN endpoint to all files on your website
     Origin hostname = ordklar.dk
     Origin path =
     Example CDN URL: https://cssinfo.azureedge.net/content/StyleSass/custom.min.css
    2) Allow access from the CDN to only files from the "content" directory
     Origin hostname = ordklar.dk
     Origin path = /content
     Example CDN URL: https://cssinfo.azureedge.net/StyleSass/custom.min.css
    Wednesday, July 12, 2017 3:26 AM
  • Okay now i have try to make its.

    Wednesday, July 12, 2017 11:52 AM
  • but i have error 1000 on imgcdn site.
    Wednesday, July 12, 2017 3:20 PM
  • But now i have 502 error https://imgcdn...
    Wednesday, July 12, 2017 5:27 PM
  • Please provide an example URL using imgcdn.ordklar.dk  that demonstrates the 502 error you are getting back. 
    Thursday, July 13, 2017 9:02 AM
  • Now i have 404..
    Thursday, July 13, 2017 11:27 AM
  • Update here!

    Thursday, July 13, 2017 11:42 AM
  • Now can i see my logo on 
    Thursday, July 13, 2017 5:11 PM
  • Based on your last response it appears that this is now working for you. If not please let us know what currently isn't working. I noticed you had also posted a question on stack overflow regarding this - https://stackoverflow.com/questions/45085311/get-a-1000-error-i-need-it-as-a-cdn-point. So it wasn't clear if your issue was resolved yet.
    Wednesday, July 19, 2017 11:32 PM
  • Here's how I resolved this issue.  Because you're using two CDN's, namely Azure and Cloudflare, you need to modify your Azure Endpoint Origin settings by specifying your actual web server IP address as the Azure Endpoint "Origin Hostname" and your domain name as the "Origin host header".  You do NOT use your domain name as the "Origin Hostname" as this will resolve Cloudflare IP addresses instead of your actual web server IP address.

    Also, since Cloudflare is also managing your DNS, ensure the HTTP proxy option is disabled for any Azure custom domain names.

    You can leave the Cloudflare HTTP proxy option enabled for your primary domain name with the configuration above.

    Tuesday, January 8, 2019 3:47 PM