I have a server with 2 IP address, each address serves one web application that run on HTTPS.
Currently one of the web app runs on port 443 using IIS, while the other one runs on port 8443 on tomcat.
My goal would be something like this:
https://firstdomain.com => this should be served by the IIS server
https://seconddomain.com => served by Tomcat server
Is the above configuration possible ?
If you have two IP addresses. You can bind one IP for IIS, another IP for Tomcat.
So, both sites can individually use port 443.
For example:
https://firstdomain.com => 192.168.1.2 => IIS
https://seconddomain.com => 192.168.1.3 => Tomcat
IIS IP binding
http://technet.microsoft.com/en-us/library/bb734869.aspx
Tomcat IP binding
How do you configure tomcat to bind to a single ip address (localhost) instead of all addresses?
Related
I want to forward the ip of my localhost server for being publicly accessible.
But while trying to configure my router on port 80(as it is localhost's listening port) it shows "Error: The port of the remote web management is conflicting with of the virtual server."
Is there any fix to it?
I was able to resolve this by updating the Web Management Port to a port other than 80. This setting for me was found under Security -> Remote Management -> Web Management Port.
After updating, I could enable port forwarding on port 80.
I have IIS 7.5 installed on my computer.
I have one site configured on it.
It has binding on port 80 with IP all unassigned.
I want to reach that site from a remote computer i.e. not inside the LAN.
I also configured port forwarding to my LAN IP but I still can't reach it.
Is there something else I need to do in order to achieve it?
telnet from computer to port 80 succeed but from a remote it doesn't succeed.
These are the configurations in my router:
10.0.0.2
External Port Start
1
External Port End
65000
Internal Port Start
80
Internal Port End
80
Ok - it was a problem with my router configurations:
I set port 80 for both external and internal and no I reached my computer
I have a server to which I connect using VPN. I have a deployed a site on this on IIS server. URL for the site is "http://localhost:8080/mysite". when I use this Url on server it is opening up.
But When I use its ip address Lets say http://172.x.x.x:8080/mysite it is not accessible. (not on the server not from my dev machine (Which uses VPN)).
But if I disable firewall on server then It is accessible using the IP and port 8080 also or if I change the port number of deployed site to 80 then also I can access it(without disabling firewall).
Is there any way so that I can use my port number 8080 and also don`t need to disable firewall on server.
Is it possible to run couchdb on port 80? I'm looking to host a couchapp from it and don't want my users to have to type a port number in the url.
When I change the port to 80 in the couchdb config it becomes unavailable, and I have no access to it on 80 or any other port. I have to change the port back in the local.ini file.
Is this not a recommended setup? Would I be better hosting behind a reverse proxy? If so, any tips on how to get it working behind an IIS reverse proxy? I tried that too using ARR and URL Rewrite, with no success.
EDIT:
First, this chapter of the CouchDB definitive guide seems to suggest it is ok to server web apps directly from couch. Curious what the community thinks:
http://guide.couchdb.org/editions/1/en/standalone.html
Second, I installed CouchDB on a second machine that does NOT have IIS installed on it and it ran on port 80 just fine, so I suspect that even though I've turned off all websites in IIS it is still hogging port 80. Any way to make IIS give up port 80?
Ok I figured it out. By default IIS listens for port 80 on ALL IPs. So it also grabs 127.0.0.1 and listens on port 80 there as well, EVEN IF YOU TURN OF ALL WEBSITES listening on 80.
To remedy this you need to add an IP address to the IP listen list. By default this list is empty and IIS decides to just listen to all IPs. But if you add an IP or IPs to this list IIS will only listen to those IPs.
First here's how you can see what IPs are in the listen list:
netsh http show iplisten
If the list is blank IIS is listening on all IPs. To add an IP to the list:
netsh http add iplisten XXX.XXX.X.XXX (where the X's are your IP)
Now IIS and CouchDB can exist together on port 80 in happiness, as long as they both have their own IP's to listen to.
I have an asp.net web application hosted iis on LAN. When i type in my local ip address in the URL box, i can access it. My question is, if i want to access it from outside the LAN, would i have to port forward it to port 80? And intead of typing my local ip address in the URL box, i would now have to type the routers ip adress??
Use your internet and LAN address.and put a net forwarding in firewall or port 80 for your internet address.and yes you need to make changes in your firewall as well.
Yes. If your internet address is 7.7.7.7 and your LAN address is 10.10.10.10 -- you'll need to put a NAT/Port-forwarding entry in your router/firewall to send traffic on TCP Port 80 destined for 7.7.7.7 TO 10.10.10.10. On most home routers this is a pretty simple task.