I have a LAMP based wordpress installation running on an azure VM. its working fine and publicly accessible.
I wanted to try azure CDN - Verizon for serving my images.
I made cdn, using the new resource manager, added my endpoint of filmycurry.com (my origin server). I am using http only, hence configured the same in endpoint.
My problem is that even after 48 hours. I still cant access any media using cdn. you may try the below links
working - vm based - http://filmycurry.com/wp-content/uploads/2016/05/yu-2.jpg
not working cdn - http://filmycurry.azureedge.net/wp-content/uploads/2016/05/yu-2.jpg
pls note, I had also configured the path correctly to /wp-content/uploads, since beginning.
Related
Where can I locate the staging url for my Azure Verizon Premium CDN
Currently I'm using Azure storage & then using Azure Verizon Premium CDN infront of it to handle all the traffic.
The issue I have is the site is live now & making changes to the rules is not without issue on a live site. I'm trying to find where the staging url lives.
According to the documentation: https://docs.edgecast.com/cdn/index.html#HRE/Environment.htm#Staging
referenced from Azure docs:https://learn.microsoft.com/en-us/azure/cdn/cdn-verizon-premium-rules-engine-reference
Requests may be directed to the Staging environment by prepending "staging." to the hostname defined in a CDN URL.
Sample CDN URL (Production):
http://wpc.0001.edgecastcdn.net/800001/myorigin/marketing/brochure.pdf
Sample CDN URL (Staging):
http://staging.wpc.0001.edgecastcdn.net/800001/myorigin/marketing/brochure.pdf
Applying to a sample file on my domain would be (Production, Staging): http://wpc.0001.edgecastcdn.net/8011BE84/atsworkspacewebapp/atsworkspacewebapp/index.html http://staging.wpc.0001.edgecastcdn.net/8011BE84/atsworkspacewebapp/atsworkspacewebapp/index.html
Through the Postman app I can get to Production (must disable SSL verification), but not Staging. That domain is void.
Where would I find the staging url?
I'm using Azure Storage Blobs and have Azure CDN in front of it serving static images and videos. I have been trying to get my website to use HTTP2 for a while now, but have run into issues with how Azure containerizes .NET Core applications on Linux machines. So, the website (using Kestrel), is only serving files over http/1.1 even if they're local files.
I thought that I could "offload" somethings by moving them to a storage blob container, then using Azure CDN. This article suggests that it should be available: https://learn.microsoft.com/en-us/azure/cdn/cdn-http2
Is there something else I need to configure within my CDN profile or the Storage account to enable http/2? Or is it because my server is serving it as http/1.1?
Thanks,
AJ
After some searching, I found a thread on Stack Overflow (sorry, on mobile and it's a pain to copy/paste links) about how some anti-virus softwares intercept requests to do SSL checking. Anyway, I use Bitdefender and when I went to Protection > Online Threat Prevention and disabled "Encrypted web scan" and then reloaded my domain, sure enough all traffic poured in over http2. I'm not sure why Bitdefender treated Akamai differently, but at least we know why now!
Hope someone can assist me in correcting this. I am on the last step to enable my CDN endpoint with a custom domain. currently the static website on storage works correctly the following ways.
1 - Storage Account endpoint
2 - Azure CDN xxxxxx.azureedge.net
CNAME is created and correctly configured and validated in azure for my cdn.customdomain.com but when I try to connect to it I get a ERR_CONNECTION_RESET when using a browser or 404 using curl. Any advice anyone can provide.
You could verify the followings:
Configuration. Make sure you select the Custom origin as the origin type and static website URI as the origin hostname.
Networking related. ISP blocks some websites. Firewall blocks specific websites. Internet connection is disabled or interrupted. Refer to this.
Browser error like Chrome. Clear your browser's cache and all locally stored data including cookies or try to use another browser. Refer to this.
Moreover, you could verify this via accessing the cdn.customdomain.com in an Azure VM, which is a different environment from the on-premise network.
I have Windows 10 Azure VM and trying to play videos from CDN (vid.pluralsight.com), but it cannot connect to this cdn. Tried tracert to this cdn but it is timing out. this cdn is on http://www.cachefly.com/.
Anybody knows where to enable this?
ICMP is disabled on Azure VM's, so your tracert calls will timeout/fail (even with http/UDP supported packages). That being said, I would reach over to PluralSight support, it would be logic on their end in their CDN configurations denying access to certain IP's or ranges, or without proper auth tokens. They likely can assist you further. The issue does not appear to be with the CacheFly CDN because other CacheFly CDN enabled content is served appropriately on the Azure VMs I've tried (both Windows/ Linux). If you have a CacheFly account you should be able to pre-warm a few cache locations and pull those with url filters, etc. and see that you can expire content, get geo-cached items, etc.
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.