I have installed 'Web Deploy' on Windows Server 2012.
However it is listening on port 80 (I know this because there is a hardware firewall blocking 8172 and I can still deploy to it).
I have seen a way to do this with the command line - but applying to IIS 6 and using an msi file (I have a .exe for Web Deploy 3.5).
Can the web deploy agent run on a port other than 80 on IIS6?
(I don't want web deploy to be available on port 80 for security reasons - when I use port 8172 I will be using a VPN to get through the firewall).
In 'Management Service' in IIS it states 8172 already not 80.
How can I stop it using port 80 - and make it use 8172 only?
thx
Related
I am trying to setup web deploy to my Azure VM, I followed the steps but it is always showing that error message.
I have checked the Azure Firewall, can telnet to ports 80 and 8172 on the VM.
Both services are running (wmsvc and msdepsvc ). I can't ping the machine but that is because Azure blocks ICMP. I can otherwise reach the server via RDP or opening existing web applications.
I have also checked that the Site names matches the IIS site.
Any ideas?
Thanks
I have hosted an asp.net mvc application on the IIS server. I have used the port number 8080 but when i try to browse the application, I have been shown a message
like "The site can't be reached. Local host refused to connect." Plz help.
The error is caused due to port 8080 being already in use. Try changing port e.g 8081
I'm trying to deploy a Loopback project to live server, all works well on local. On server, after running node ., I get the console log of:
Web server listening at: http://domainname:3000
Browse your REST API at http://domainname:3000/explorer
So it looks like the server is running.
Problem is that I get no response from the server. Neither from domain:3000 or /explorer or any endpoint I created.
Does anyone know what might be the issue?
Thank you very much
I had a similar problem when I was trying to deploy my code. Some of the possible solutions to the problem depending on where and how you are deploying it-
Check if your security group allows connections on port 3000. AWS EC2 by default closes all ports except port 80. You might have to add an exception to your security group and allow port 3000 to be accessed from everywhere.
If you are using a container, check if your container has the ports open and if the container port is accessible by the hardware hosting the container. On Azure, I faced this problem as Azure Web App Container Service by default only listens to port 80 and 8080. So I had to modify my code such that it can use the default NODE_ENV.PORT or 8080.
Little background....
We are already using IIS server 7.5 for our .Net web applications. Now we are developing WEB API in nodejs and wants to deploy the same on the existing Production infra.
Is is possible to use port 80 for both IIS and Nginx?
One of the possible solution I think will work is to have two public IPs configured on the LIVE infra and ask each server ie IIS and Nginx(nginx as proxy for node app) to listen to port 80 for http and 443 for https of respective public IP.
Note : I do not wish to use IIS url rewrite to forward request from IIS to nginx or vice versa.
Would appreciate if you guys can point me to right direction
Thanks
Ok i have successfully created a VM Server 2008 on Azure and installed the TFS 2012 express.
I try to access it via visual studio, web interface but i can't.
Port 8080 at the VM's firewall is open for public, however the port appears closed through a port scan.
Any suggestions ?
Note: I know about https://tfspreview.com/ however i would like to setup my own on my own VM :)
Opening the right ports on the firewall is a good start. But you need to let Windows Azure which ports should be opened externally and forwarded to your VM (also supports load balancing).
In order to make port 8080 externally accessible you'll need to go to your VM in the portal, go to the endpoints tab and add an endpoint here (make sure it maps to private port 8080):