I'm new to setting up in IIS 7.
Apparently I have to use port 443 for a site but I cannot bind it since DNS Server is already using port 443.
Is there a way I can use 443 for my site while DNS Server is also using the same port?
Related
Let me start by saying I'm very new to this:
We have a linux server behind secure environment (No internet access). I was running apache webserver on that machine in port 8080 and it was accessible within the company network. Recently we asked networking team to configure us Proxy address so that the server can access Internet to perform yum, wget and few other maintenance related task.
The networking team configured http and https proxy on port 8080 and gave us a proxy address to use (http://someproxyaddress.com:8080). Now the port 8080 is connected to proxy server and apache service has been kicked out from that port. hence, it's unreachable. what kind of configuration changes do I have to make so I can access the apache web server from another machine within the company?
The scenario:
I'm using a dedicated old PC to host a website from my dorm.
I have a domain that I buy from hosting provider such as 1&1, namecheap, &etc
But I have no control over router to enable port forward/trigger.
Since it's the college network.
But I'm using a VPN that allow port forward.
And I have open some port to listen, and able to access the website from internet using the open port. Eg: www.example.com:33333 or vpn_ip:33333
Apache server is set to listen to port 33333 since it's the port number that I open from VPN provider.
My question is:
How do I access the website from internet just using www.example.com. without port number at back
Is there anyway of doing it?
My idea is something like this..
I'm accessing the website using the link www.example.com (port 80)
Then,,, it is possible for domain provider to do something like forward or redirect or etc using something like A record, Cname record & etc
After it successfully forwarded port 80 to 33333. The website is accessible using port 80
Note: I know its impossible access the site using vpn_ip:80 since the vpn itself may use port 80. but how about the domain name?
I have changed port 80 to 8081 for IIS default website on Azure Windows 2019 server and also opened all ports, all sources and all destinations in azure portal inbound networks but still cannot access the site using port 8081
I have been debugging for elasticsearch port 9200 connection issue then found out same issue with others as well like 8081.
I have IIS Installed on Azure VM with one Website running on PORT 80 which is exposed over the internet via the following Azure Firewall Role
if I try to bind incoming traffic on any other port that is not PORT 80, for some reason the Firewall doesn't seem to allow it.
for Example, if have a website running on PORT 8080 and I try to Set Firewall roles from EXTERNAL IP to the Internal IP via PORT 8080... the Website is unreachable.
If the website runs on PORT 80 and the Firewall Role is via PORT 80.. than the site works.
does anyone have any idea/suggestions?
I would like to be able to Expose websites over the internet from the Same Web Server using different PORT for each one.
I've found the answer to my problem via this URL:
https://manage.accuwebhosting.com/knowledgebase/2886/How-to-configure-IIS-to-access-website-using-IP-address.html
Basically After create Inbound Firewall Role from Azure on port 8080, the next step is to Add in Windows Firewall a New Role to allow Incoming HTTP traffic via port 8080 or any other port that the Wibsite is binding.
hope this will help others.
I have a problem configuring IIS for my needs. Let's start with the situation that I have:
Application listening on IP address A.A.A.A on port 443.
IIS website listening on IP address A.A.A.A on port 80.
IIS website listening on IP address B.B.B.B on port 443.
My machine is configured to have two IP addresses A.A.A.A en B.B.B.B. My application only binds to the A.A.A.A:443 endpoint. I want that IIS only uses A.A.A.A:80 and B.B.B.B:443. The site binding are correct, but IIS still binds to both A.A.A.A:80, A.A.A.A:443, B.B.B.B:80 and B.B.B.B:443. Because it binds to A.A.A.A:443 my own application cannot listen to it anymore and fails to start.
I have tried to use the netsh http add listener, but I cannot restrict IIS to use specific IP/port combinations. I can only specify IP addresses, so it will still bind to A.A.A.A:443.
Does anyone know a solution? I think it's kind of crazy that IIS binds to all available IP addresses even when I set the site binding to only a single IP address.
It is not IIS that is listening to the IP. It is the HTTP driver which is utilized by many services, not just IIS. Unfortunately the only to accomplish what you want is for the application outside of IIS to utilize the HTTP driver. I believe this easiest way is to use WCF.
See Exposing WCF Services Via HTTP when not hosted in IIS
This can be done with netsh, see the instructions here
http://support.microsoft.com/kb/954874
You can tell IIS which IP address to bind too.