I am currently trying to deploy a cloud service to Windows Azure but I get the following error message:
"Could not retrieve the list of cloud services.[...]"
Details can be seen on the picture.
It seems to me that VS couldn't find an existing service role in the subscription but my service is available and running, I just can not deploy a new version there.
A few days ago it worked correctly. Any Idea would be appreciated.
Thank you!
After hours of Certificate generation, messing with azure toolkit, etc. I figured out that the problem was that somehow my computer tried to resolve the azure DNS to localhost because Fiddler got crazy and the proxy that Fiddler uses, haven't stopped even after restarting my computer.
I faced same problem, when trying to deploy to azure while fiddler is running. Simply closing fiddler solve the problem.
Go to the previous screen, there will be an option of connecting to Azure using your credentials. Select your subscription and you will be able to download a file to your local machine. That file contains your subscription info as well as the keys. Once you open that file through this wizard, you will be able to publish to your services. You must create cloud services first before you do that.
Related
I have a web app, ironradio.org, that I've deployed on Azure from VSCode. I've made some updates to the site and am now trying to deploy the newest version. Now when I try to deploy using this button:
I get the error 403 - This web app is stopped in the output window:
I've already deployed several versions of the site using the same method and it's never failed before. Also, the app is definitely not stopped because I can still browse to the site and it shows up.
My best guess as to what's going on is that I associated the App Service with a new resource group since the last deployment, so maybe VSCode isn't recognizing that? Does anyone have any idea what's going on here?
I tried the link given in the error message, but it wasn't much help.
Microsoft foreseen this type of error and how it can affected its customers greatly and this is why the deployment slot is for you.
Firstly, you have to delete the app and reupload again except you set up continuous deployment which work mostly with GitHub and other version control platforms.
Apart from this, I will suggest you check out the deployment slot docs. It’s very simple and easy to use
https://learn.microsoft.com/en-us/azure/app-service/deploy-staging-slots
I am a total newcomer to the Azure cloud. I have this .net-core 2.0 app which runs locally on my development PC (Ubuntu Linux 17.10).
I have followed this guide:
https://learn.microsoft.com/en-us/azure/app-service/containers/quickstart-dotnetcore
... and I have deployed my app to the App Service container.
However, when I go to the app in my browser I get:
"503 Service Temporarily Unavailable"
Now, there are probably thousand things which can go wrong. However, I can't seem to find any debug logs/console logs to look into - so I am kinda looking with my eyes closed (It's not easy to debug that way).
It should be noted that I am on a free trial which have given me a $200 credit to use in the next 30 days.
How do one debug when a service is failing (yes, I've already tried the various suggestions on the portal but with no luck)?
How do one debug when a service is failing?
You could check deployment log on Azure Portal.
Click first commit, you will see the log.
Also, you could access Kudu console to check the log. You could access http://<webapp name>.scm.azurewebsites.net
Migrating OP's self-answer from the question:
I solved this by adding this to the PropertyGroup in my *.csproj file:
<PublishWithAspNetCoreTargetManifest>false</PublishWithAspNetCoreTargetManifest>
(as per: https://github.com/aspnet/IISIntegration/issues/476)
Now my app works and gives the expected output.
Installed the Azure Functions Runtime as per the instructions here:
https://learn.microsoft.com/en-in/azure/azure-functions/functions-runtime-install
Configured all the things including the SQL etc correctly.
After doing that when to the https://localhost and tried to create a new Azure functions App.
When trying to create the Azure Functions App, it fails. I verified the Azure Functions Host Activation Service and the Docker Service are running.
Below is the error when trying to create the functions App from the local box:
For me, this issue was actually caused by WebDAV handler not allowing PUT verb. After I allowed all verbs in IIS for FunctionsAPI, it works like a charm.
You can use F12 in your web browser to help identify the root cause of the issue by going through the steps of creating a new function app.
Please check in the following Windows Event log for any errors on the Functions Management Role:
Microsoft-Windows-FunctionsRuntime/Operational
If you don't see any information there, please follow this instructions to capture a trace for the FunctionsAPI website with status code 400-999:
https://learn.microsoft.com/en-us/iis/troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis
What I have:
VS2015U2
ASP.NET 5 MVC 6 website
Deployed to Azure Web App
The site works locally
When I deploy to Azure I get internal server error (500)
I'm unable to Attach a debugger since they messed up something with the latest versions (tried manually too https://azure.microsoft.com/en-us/blog/introduction-to-remote-debugging-on-azure-web-sites/)
I have app.UseDeveloperExceptionPage(); but I guess the site is failing during configuration so it doesn't display any other information.
So how to resolve this? I need to see the .net exception but I have no idea how to do that.
Try adding Application Insights to the app. You should see errors on startup of your application.
I would also take a look at your startup code to see if you are writing to disk anywhere during configuration or app.start. This might be the case if you are using AAD in any capacity.
You can also hit up the KUDU console by targetting https://sitename.scm.azurewebsites.net . You will be able to navigate in the debugging console to see the RAW logs from IIS. That might shed some light into the situation. See KUDU for more info.
I solved this problem like show below.HTTP 500 error interested about that is not allowed to access the server.Go to azure portal address and choose your database.Press"Set server firewall " and Allow Azure services and resources to access this server choose "Yes" save that page and refresh your service.Than you can see your data
Use the KUDU console at https://sitename.scm.azurewebsites.net
Go to web.config file and check if the process path is correct.
I used the Azure Log Stream to help figure out what was going on. As Karishma Tiwari - MSFT said, the issue ended up being my web.config file (which was built for .NET 3.5 and not 4.7)
Here's the tutorial to set up Log Streaming: https://blogs.msdn.microsoft.com/azureossds/2016/09/28/how-to-identifyreview-errors-on-php-applications-in-azure-web-apps-using-log-stream-service/
My particular app's solution was to update my Azure App Service to use .NET 3.5, in its Application Settings, like so:
For me it worked after I turned "Allow Azure services and resources to access this server
" to Yes
I got this error even though I had enabled Application Logging (Filesystem), Detailed error messages and Failed request tracing in App Service logs
This page isn’t working
mysite.azurewebsites.net is currently unable
to handle this request.
HTTP ERROR 500
However by navigating to Log stream and selecting Application Logs I could see a detailed error message:
I know this question has already been answered but here is a recent view of the Azure Portal where I found a solution to this problem
We try to set up a FTP connection in Azure, to use in a Logic App. Seems very straightforward, the instructions are very clear:
https://azure.microsoft.com/nl-nl/documentation/articles/app-service-logic-connector-ftp/
When we click on 'create' (of the FTP Connector, so before we are actually in the logic app), absolutely nothing happens. The button turns grey, but nothing happens. No notifications, no fails, no FTP connector.
When we try to set up the FTP connector directly in logic app, we get the error message 'error fetching the deployment template. please try again'.
We have tested the connection in FileZilla, this works. We have tested with 2 different FTP connections, both same result. We have played with every parameter in the settings, no change.
We searched here on Stack Overflow, but we haven't found anything that helps. Most questions related to FTP connections and Azure describe situations where it is necessary to connect to Azure. In this case, Azure would be the client and we want to pull in data from a third party's FTP server to analyze in a HDInsight cluster.
We'd like to fix this issue, but it's very difficult with no error message and no response. Has anyone else experienced this and how did you fix it? Does anyone have a clue how to further debug?
Thank you for your time and effort - I'm aware there is not a lot of information here, which is exactly the problem.
I followed the same steps as mentions in link. It created FTP connector successfully. Use portal for this https://portal.azure.com. What service plan you are using? I am using pay-as-go service plan where it's allow to create me.