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?
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 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.
The bot that has been developed runs in the emulator locally without any problem.
But when we hosted it in Azure. We're not getting any reply from bot.
I tried testing the Bot Connection in dev.botframework.com, I get an "Endpoint authorization succeeded message".
can anyone let me know what could be the issue.?
The issue is fixed now.
I removed the database connection string from web.config file and configured it in Azure Web App service -> Application settings.
I gave the connection string name I gave in MessageController.cs while creating it through ConfigurationManager.connectionString
ConfigurationManager.ConnectionStrings["ConnectionStringName"].ConnectionString
Also, I updated the BotBuilder from v3.0.0 to v3.0.1 as it had a bug fix with Bot.Connector which I had used in my code.
Both these changes helped.
Arjun
As you mentioned in the question, it works well in localhost. But when you host inside Azure app services it doesn't work. If end points are working properly you will normally get default message from the Bot whether you're connection to a DB or not. Please check your endpoint,
When you connect to the azure your endpoint will look like,
http://azuregetstartessamplebot.azurewebsites.net
But keep in mind when you adding that URL as your endpoint, include https instead http and add /API/Messages in the end of your URL. Then final endpoint URL looks like,
https://azuregetstartessamplebot.azurewebsites.net/API/Messages
hope this answer will help you. Try it. Cheers!
Our application is making HTTP requests with HttpClient to some websites. In local it always work, but for an unknown reason it fails in production.
Our application is an Azure Website.
We are getting the following error: Unable to connect to the remote server.
We have an IP Based SSL certificate, our IP address is not blacklisted anywhere. It was not happening before 3-4 days.
Depending on the URL we call, it sometimes work, sometimes not, we really don't get why.
UPDATE
It seems to only happen when we make requests to website hosted by GoDaddy, called their support and our IP address is not blocked.
If you isolated that this is not a GoDaddy issue, I would contact support on Azure. It might be a tech issue or networking issue. They will help you isolate the source and fix it.
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!