HI
I develop the wcf service for hosting in IIS. test service in computer(which is service host in itself IIS) and as result this service work fine.
But When I try use that service from other Computer, service not responding and service cant be find!!!
This could be:
A security problem, what are the security settings on IIS?
The port is blocked, what firewall settings do you have?
Or that you have an address with localhost (as already answered)
Related
Is it possible to disable FTP on the public IP of my web application by default, or do I need to purchase a web application firewall? It's hard to believe that a basic firewall is not part of the default web app in Azure.
You would have to go the route of getting an App Service Environment if you wanted to implement this restriction. I searched the feedback site and there aren't any plans I know of bringing FTP restriction to multitenant environments. An App Service Environment would be overpriced if that's all you needed and therefore wouldn't recommend it.
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 have an Azure virtual machine, on which a process listens on a certain port. A Node.js application on my local computer is able to connect to this process using the VM's public IP address. But the same Node.js application, deployed as an app service on Azure, is apparently not able to connect using any IP address, despite the fact that the VM allows all incoming traffic on all ports.
(Details: The VM process is running "q" (kdb+), and the Node.js application is using the "node-q" package to connect to it. Both the Azure VM and the Azure app service are Linux, but the local version of the app service is on Windows. The Azure app service is able to connect to my Azure SQL database.)
Any insights into this problem would be appreciated.
There are many reasons for Bad gateway error, probably you could verify these factors on your side:
Azure VM side. Make sure the Azure VM is running and the process port is listening when you request a connection from an application. You could run sudo netstat -plnt on Linux VM to check the listening ports. Or, a server can crash if it has exhausted its memory, due to a multitude of visitors on site or a DDOS attack.
Firewall blocks a request. You should allow all incoming traffic or Azure web app service outbound traffic on this listening port on the VM. In this scenario, you could verify the Network Security Group configuration for the VM and firewall inside the VM if you have. You could find NSG settings by clicking Virtual machine--Settings---Networking---inbound port rules on the Azure portal.
Faulty programming. It seems the Node.js application could work locally.
Temporary issue. Sometimes, there is no real issue but your browser thinks there is one thanks to an issue with your browser, a problem with your networking equipment, or some other reasons. You could refresh your web browser or clear cache and cookies to get the page back what you are looking for. More details you can refer to fixing 502 error.
If you still have any question, feel free to let me know.
It was faulty deployment. I didn't include all dependencies in the upload to Azure. Thank you.
I am new to the Azure platform so hopefully this is an easy question:
I am currently setting up a Sharepoint web farm through Azure. My current architecture looks like this:
A WIN2008 VM serving as my Domain Controller. I have the domain setup and AD running
A WIN2008 VM SQL2012 serving as my db server
A WIN2008 VM serving as my sharepoint web server.
All of the VMs belong to the domain.
I have sharepoint up and running on the sharepoint web server and I can access the sharepoint sites using //localhost. However, I cannot access the sites from an external computer (port 80). I cannot ping it with the IP Address or the *.cloudapp.net address. I have already ensured the firewall ports for 80 are open for all profiles. I have also setup an endpoint for port 80 on the sharepoint VM.
Any thoughts? I appreciate your help in advance.
To elaborate on the endpoint reference above:
There is a configuration page in the Azure portal that you need to check out to ensure that the proper ports are open AS WELL AS the ones on the Endpoints page for your windows VM. I assume the same would apply for other hosted OS VMs like Linux, etc.
When I came across the Endpoints tab for the VM in question on the Azure portal I noticed that there were RDP and PowerShell ports listed but no HTTP. After adding that I found that I could hit my IIS server on the VM. In a nutshell its like there are two firewalls, the one on your server and one on the Azure portal.
I believe that Azure will block ping requests
http://social.msdn.microsoft.com/Forums/en-US/windowsazuredevelopment/thread/7ce4e4c5-c714-492f-8cd6-424c01552195
Looks like you have an answer, but of note is that you have to set up endpoints for anything that you want to hit.
I have a typical Silverlight 5 application created on Azure with a web project that hosts the site hosting the Silverlight XAP file and another web project that hosts a collection of WCF Data Services.
Together the two sites run in a single Azure role but on different ports. Port 80 hosts the WCF Data Services and Port 8081 hosts the actual Silverlight application.
I am having a cross-domain issue with this configuration. In watching through Fiddler, it appears that when my Silverlight application calls the Service, it is, as expected, looking for the clientaccesspolicy.xml and crossdomain.xml files from the WCF Data Services site to be allowed cross-domain access. However, the Silverlight application is sending the request to http://127.0.0.1 and not the correct URI for the domain in which the WCF Data Services are hosted.
Can anybody explain to me why the application is trying to go to 127.0.0.1 and not the correct URI?
Thanks
Your Silverlight application has a file named "ServiceReferences.ClientConfig". That file has been created when you added the service reference. And because you added the service reference from 127.0.0.1, your file is configured that the service endpoint is on 127.0.0.1.
What you have to do, is to manually change the ServiceReferences.ClientConfig file, before you deploy, to fix the service endpoint address (and set it to the domain you are using).
Or you can use mine approach to handle this kind issues.