Azure CDN responding with strange result - azure-cdn

Our azure CDN suddenly started responding with the following result:
We tried restarting the CDN with no result. Source file is publi availible through the blob store.
Thanks for any help
Larsi

Related

Deploying ionic 4 website to digitaloceans spaces CDN

I'm trying to deploy a basic ionic 4 application to spaces CDN provided by digitalocean.
I uploaded the static website on gitlabpages and the website is working.
I've tried to replicate the results on spaces CDN but the file instead of being opened by the browser get downloaded once opened.
I figured out it could be the --base-href, and I tried to modify it, but without success, the index file provided by the build still get downloaded
At first I build the ionic app
ionic build --prod --base-href="xxx.gitlab.io/xxx" //code used to deploy for gitlab pages
Then for gitlab pages I deployed it using gitlab-ci.yml file, as explained here, while for deploying on spaces I used a python script
I would expect to be able to upload an ionic build into spaces CDN and being able using the link provided to see the website.
I'm not sure if I'm doing something wrong at conceptual level using a CDN, it is actually my first time trying to serve a website using this tech.
UPDATE
I've uploaded to the CDN again, and I realized that if I use the origin link, it actually load the html (even tho it gives me a lot of errors).
While is I use the CDN link, it try to download the file.
I have purged the cache of the CDN so in my opinion the CDN and the origin should behave exactly the same, Am I wrong?

Bluemix cloudant, when my project website started, it seems empty

I could deploy my project on bluemix successfully, but I am not able to see any images. and it shows nothing while I am entering data in the input fields. I took project from your github and followed your steps. What could I do wrong? I will thank your help (Jeff )

Error 403: Project blocked; abuse detected., accessNotConfigured

I have a golang program running on my local laptop. I had a previous Google Cloud account that I used to upload images to a bucket (using gcloud local context). It worked.
I created another company branded Google Cloud account and linked our company card to it.
Ever since then I get the error in the title.
I contacted support and got this:
Hi,
Unfortunately we are not able to identify any abuse related actions taken on your project. To resolve this issue, please reach out to the Google Cloud Platform community support.
Sincerely,
Google Cloud Platform/API Trust & Safety Team
Do you guys have any ideas? Any help would be much appreciated.
The problem turned out to be that the JWT json file being used by my project for authentication was out-of-date.
I had to re-download a new JWT json file from the cloud console and put it in the root of my project folder.

Error while deploying play web app into azure cloud

Hello i am trying to deploy play application into azure cloud using eclipse and application is working fine in azure storage emulator but while publishing the same in azure i am getting invalid publish setting file cannot parse the file error.I deployed code in azure using bit bucket and linked necessary database .When i try to access the URL i get "you do not have permission to view the file" message.
have followed this blog https://msopentech.com/blog/2014/09/25/tutorial-running-play-framework-applications-microsoft-azure-cloud-services-2/ still getting the same invalid publish setting file cannot parse the file error
can any one show me way.
thank you in advance!!

How to deploy WorkerRole project, How to get the exact error during uploading

I have to Work with WorkerRole project to deploy some services to perform the data sync with the other databses. i tried to publish but stuck, Internalization, Starting, Preparing, Recovering and finally aborted.
After getting the above stituation i build a simple workerrole project and tried to upload the result is same.
And i am not able to find out the problem with the same.
Please provide some help.
A typical problem, when deploying, is having a connection string pointing to the local emulated storage. This is the first thing I'd check if the worker role code runs locally in the emulator but fails when being published to Windows Azure.