I recently deployed an ASP.NET MVC4 website to Azure website. However anytime I am on a proxy network, I wouldn't be able to connect to the services.
How to connect Visual Studio Azure SDK1.3 to the Azure Website Over proxy server. Below is error message:
There was no endpoint listening at https://management.core.windows.net/3e541adf-2b85-4ff1-b066-a40f11f6e4a6/services/?servicelist=WebSite&expandlist=Service that could accept the message.
This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
The remote name could not be resolved: 'management.core.windows.net'
The very last line of the error says it all:
The remote name could not be resolved: 'management.core.windows.net'
The proxy you are using blocks or has DNS resolution issues for the management.core.windows.net domain. There isn't much you can do about it, besides using another proxy or not using proxy at all.
If you're able to whitelist domains on your proxy, or know someone that can, you will want to whitelist management.core.windows.net.
This may help, it explains how to use a Port Bridge to get around your problem.
http://www.dotnetsolutions.co.uk/blog/connecting-to-sql-azure-without-changing-your-firewall
Related
I have an Azure app service and in some cases I need to send a web request to a non-azure webserver. What do I need to do to make it possible.
Currently the web request fails with no clear error message.
In response to a HttpClient Put request I get a System.Net.WebException exception which says there were errors.
THe same request works from a desktop application.
If your webserver is reachable from the internet you should be able to access it through your App Service. Try to log a ping to your webserver and google (8.8.8.8).
If your App Service is in a VNET you should enable some outbound rules to your webservers IP adress.
The server I am connecting to is an other Azure service. After some more investigating, It appears that I can connect to it if I do not use SSL (i.e. http://) but the connection is immediately closed when using SSL (https://). I assume that the problem must be related to the use of SSL.
I am trying to configure a server code 2016 VM on Azure to allow access from IIS on a remote server (outside of Azure) - I have been following documentation from here and here.
When I try to connect to the Azure servercore server from IIS (File, Connect to a Server, provide server name/port and credentials), I am getting the following error:
"Could not connect to the specified computer.
Details: Unable to connect to the remote server"
I have added the firewall rule as noted in the steps I have been following with no success. I believe that this may be a security group issue, but web searching has drawn a blank - I have not been able to find anything on connecting IIS to a VM on Azure in order to allow web server administration.
Any help would be much appreciated, preferably in simple steps - I'm a programmer who has had a devops task dropped on him, and as such have minimal understanding of Azure's mechanics and terminology!
Thanks!
So the error was due to the misconfigured NSG. Need to open up port 8172.
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 can't seem to be able to deploy a site to a windows server 2012 r2 running IIS and Web Deploy in Azure VM. I have verified that the port is open, the credentials are correct and the site name as well. I tried using http: and https: also tried using msdeploy.axd end point and the MSDEPLOYAGENTSERVICE one nothing. Check is the services are running and if I can connect to the machine which at can on port 80 to the default site. Tried connecting from multiple connections I get the same result...
Could not connect to the remote computer ("<computer name>.cloudapp.net"). On the remote computer make sure that Web Deploy is installed and that the required process ("Web Deployment Agent Service") is started. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE. Unable to connect to the remote server.
After dealing with this for about an hour now, I figured out how to fix this on my Azure Virtual Machine.
First the obvious
Check that port 8172 (if you're using default settings) is open in your firewall
Check that the processes MsDepSvc and WMSVC are running.
Check that the site name is correct.
Management Service
In ISS, at the root level of the server, check your settings under Management Service.
It should have Enable Remote Connections checked:
Did you download the full package
This was the one that got me, I hadn't installed everything.
On the bottom of the WebDeploy page: http://www.iis.net/downloads/microsoft/web-deploy
You can download the full package, and then just install everything.
You don't mention if you have an endpoint configured for your Azure VM. If not, make sure you create an endpoint with a private port of 8172.
EDIT: Here is a troubleshooting guide for web deploy that includes the error message you've encountered. Additionally, from my own experience I have managed to mistype the site name and not install .NET and seeing similar errors.
Helpful but in the end in our case it was TLS mismatch. Check both machines can do TLS 1.2 if you are forcing it. Have put more detail here https://fuseit.zendesk.com/hc/en-us/articles/360000328595. Cheers
I configured the Default website in IIS for SSL by creating a CSR using the IIS itself, submitted it to a CA, and assigned the issued certificate as the server certificate. That's all is required in this world to setup server SSL. But when I open the https url it says "Internet Explorer cannot display the webpage". Which pillar should I bang my head against to get it working? The only help from microsoft I could find is that useless arcicle http://support.microsoft.com/?id=290391 that presupposes you are configuring a non-default website for SSL and goes on and on about port conflict. I'm using default website for https.
I'm using windows xp, IIS 5.1 and Microsoft Management Console 3.0.
Please help or courier me a shotgun for shooting myself.
Edit: After I configured IIS for SSL, the Apache Tomcat server which had been configured on port 8080 has suddenly stopped working. The 8080 urls just timeout. What is the connection?
Edit: Because I can't live without Tomcat on my machine, I used another machine to setup IIS SSL after stopping the tomcat there. I face the same problem there, "Internet Explorer cannot display the webpage". Please help before I shoot myself.
Don't shoot!
XP has given me fits with SSL... have you tried setting the application pool to high/isolated setting up the website with an identity under COM?
That seemed to solve some issues for me.
Also - did you make sure to set it up in the correct stores? Is this an application that is running under your account or a service account? If it is a service account you may need to do a RUN AS on the certificate management console and add under that user's personal store as well as under the appropriate store for the machine/computer.
Good luck.