I used the following guide to set up IdentityServer for deploying to Azure: http://weblogs.thinktecture.com/cweyer/2013/01/running-thinktecture-identityserver-v2-in-a-windows-azure-web-role-from-zero-to-hero-a-walkthrough.html
I got all the way until actually running the Azure site locally, but when I attempt to start it, I receive a 500.19 error in IIS Express.
I have googled this error endlessly, but every solution has failed. Oddly, if I start IISExpress for the WebSite from the Command Prompt, I'm able to visit the site without issue. I'm certain this is an issue with the Azure Emulator, but I'm not sure how or why...
Thanks!
Related
I have been facing a very weird issue with a simple web application that I have recently deployed using IIS. This is an already working application in a server in NA region. I re-created the same exact IIS environment in a new server from a different region. When I try to login using the new URL, I get the following error message.
I have double-checked multiple times that my IIS configuration is exactly same as my old (working) server.
Here is what I have selected for the Authentication setting of the server.
Kindly help with the pointers. Thank you.
I am getting below error while deploying app service via Azure DevOps. I tried to search for this issue but could not found root cause of this.
Error :
2021-03-15T06:01:27.7479723Z ##[error]Error: Error Code: ERROR_COULD_NOT_CONNECT_TO_REMOTESVC
More Information: Could not connect to the remote computer ("web-app.scm.azurewebsites.net") using the specified process ("Web Management Service") because the server did not respond. Make sure that the process ("Web Management Service") is started on the remote computer. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC.
Error: The remote server returned an error: (403) Forbidden.
Error count: 1.
'''
I tried everything until I spotted (after reading this) that my (dev) shared App Service service plan was out of storage space! When I upgraded it to a bigger one I could deploy again!
According to this document, the error is caused by that Web Deploy cannot connect to the remote service. Please refer to the follow points to troubleshoot your problem:
Please make sure Azure app service works fine. You can ping the remote machine.
That the msdepsvc(“Microsoft Web Deployment Agent Service”) or wmsvc(“Web Management Service”) service is started on the remote server.
Your firewall is not blocking incoming connections of your ports on the destination. If you used the default installation, then it would be 80 for msdepsvc and 8172 for wmsvc.
In addition, you could try to add -retryInterval:6000 -retryAttempts:10 to Additional Arguments in Azure App Service Deploy task as this thread stated.
BTW, if this issue still exists in Azure pipeline, please check if this issue exists locally. You could refer to this thread: Got 403 Error when doing Web Deployment and Web Deploy results in ERROR_COULD_NOT_CONNECT_TO_REMOTESVC for more guidance.
Thank you Edward for insightful explanation for possible root cause. Issue is resolved now.
Root cause was the agent pool selected did not have rights for deployment(IP are not whitelisted for production App service) since
We are not using agent provided by DevOps directly for production environment.
An instance that'd worked great for years starting giving me this error yesterday during Web Deploy. No changes from our side. No amount of poking around non-invasively solved it, but simply hitting the Restart button on the Azure app service Overview page put it to bed quite easily.
In short: Double-check your publish profile (each element).
Bit longer: In my case, my publish profile contained a ResourceGroup element which pointed to the wrong resource group. (I'm using WebPublishMethod: MSDeploy) I went over all elements and made sure they point to the correct resource, credentials and whatnot.
That seemed to solve the issue.
In my case, I had modified machine.config to captur traffic in Fiddler
<system.net>
<defaultProxy
enabled = "true"
useDefaultCredentials = "true">
<proxy autoDetect="false" bypassonlocal="false" proxyaddress="http://127.0.0.1:8888" usesystemdefault="false" />
</defaultProxy>
</system.net>
and this was interfering with the VS deployment to Azure
I am deploying my ASP.NET Core 3.1 app to Azure App Service. While creating the new app service, I chose Linux as Operating System. In deployment center, when I deploy the app, it prompts me to enter a startup command. Everywhere I read about it it says startup command is optional. But when I deploy, it doesn't get further without this.
I have recently deployed other app services on windows and this was not the problem then. The startup command I am entering is dotnet <project.dll>. It deploys successfully. But after the deployment whenever I hit an API endpoint, it gives 500 Internal Server Error.
My question is:
What is the purpose of startup command? Why is this returns with 500 when deployed to linux.
S
It seems your startup command is correct refer to this.
You could check if this setting had been set already in Configuration, and check if the .dll file name is correct. As far as I known, this setting is necessary under Linux environment.
For 500 Internal Server Error, it's a error from server side, sometimes it means your web app is not prepared, and restart it would solve the problem.
If not solved, check the wwwroot file structure in kudu. ->.scm.azurewebsites.net If the file structure not correct, try another way to deploy.
Update
As your own reply, you connected your app to database. If issue still here, try add sql server policy like this:
I diagnosed the problem. My deployed app service is not whitelisted to access database. That is the reason for 500 Internal Server Error
I am building a Office 365 application using ASP.net Visual studio 2015 Enterprise. When I run the application in visual studio using IIS Express it run fine everything works. I am able to authenticate with Azure AD and be routed back to my start page. However, when I deploy it to the IIS SERVER, I am able to authenticate but after authenticating I am routed back to a WHITE screen.
FIREWALL is off
I DO NOT WANT TO HOST IN THE CLOUD!!
I tried using Fiddler but that didn't help me that much. Have anyone ever ran into this problem or similar? Were you able to get around it without hosting in the cloud?
I had this same problem - it worked fine in IIS Express, but in IIS I would get a 400-Bad Request (header too large) error and the page would just spin. To fix this:
Make sure your app login and your reply URL are the same in Azure. Make sure the PostLogoutRedirectUri in your app matches as well.
That URL in step 1 should not be a page! This is what got me I think. I had https://localhost/testdirectory/default.aspx when I should have only had https://localhost/testdirectory/. Once all 3 places matched, things started working in IIS as well.
You probably know this but make sure you're using HTTPS, not HTTP.
I am having an issue getting an HttpClient to work from a Windows Azure website. When running the site from my local machine or a local server it is able to connect to the web services without issue. However, once I publish it to Azure it returns a 404 error from the SendAsync method. I would assume a network problem except that if I do a $.getJSON(...) call to the exact same service from the exact same site I get the response back with no issue. I have tried everything I could think of but am currently out of ideas, has anyone experienced anything like this?