This problem is driving me crazy.
I have set up a few websites in IIS 10.0, enabling only the https protocol. Worecard Certificate installed with no problem. Accessing web sites from the internet works. Accessing from inside the server doesn't! I get a 404 resource not found error message. Tested http and It works both from outside and inside the Windows server.
Any idea?
Thanks
D.
the issue has been solved. It was caused by the AAAA record pointing to a different server IPv6 address. Why Windows prefers IPv6 address for SSL and IPv4 for http remains a mystery to me.
D.
Related
I've installed an apache web server to one of my windows 11 machines. I forwarded the ports 80 and 443 to this machine. I can access it by my world wide ip and machines local ip through browser but when i try with domain name it sometimes works but generally it waits a while and then connection times out.
I also added A records at my domain provider like below: (TTL = 1 hour)
Also gave permission from windows firewall for both private and local networks.
What am i missing here?
Ok i figured it out, although i wrote plain domain name in the browser chrome was changing it to https version of the site and that was causing the error.
I have create a very simple site in IIS Server version 8.5 using port 85. The site only have one index.html that shows the word "test" the page. When I access the site inside the server I can access it successfully: "http://localhost:85" is working.
Trial 1:
I try accessing it from my computer that is connected to the same network with the server using url "http://servername.test.com:85", the browser goes loading for long time and finally ends in with error "Connection Reset".
Trial 2: I try updating the Site Binding's Host name with our "Vanity Name" and "IP Address", but after this I still get a "Connection Reset" error.
Trial 3: Now I also check for opened ports using netstat, and I can see that port 85 is open. So I don't know why I'm getting Connection Reset error
Trial 4: I added Connection timeout value on the settings. But still I'm getting Connection Reset error.
Please kindly help with advise how to fix this Connection Reset issue. I can't find what is the reason behind this issue. Thank you in advance.
According to your description, I guess you may not bind the right IP address for the servername.test.com domain or use the wrong ip address bind with servername.test.com domain.
I suggest you could firstly try to use the server's ip address to access your web application to make sure you firewall setting and IP setting is right.
If your client server and the IIS server are in the same domain and you have installed an DNS server, then you could access the web site by domain. Details about how to set the DNS server, you could refer to this article.
If you just want to test, you could try to modify the hosts file in the C:\Windows\System32\drivers\etc path in your client server.
For example:
127.0.0.1 www.example.com
I've found the solution. I issue was caused by Firewall enabled on the server and the ports are not opened by the Network Administrators. So I just opened the Ports that I will be using and it works now. Installing IIS Failure Tracing help me catch the error also. Thank you for all those who answered.
As title, I have a IIS WebAPI on Compute Engine, always responses 400 Bad Request Invalid Hostname.
My API is just like:
http://[2600:1905:0:6563::]:80/Hello/
But I have another websocket program on Tomcat,and it works fine. So I guess the problem is on IIS?
Can't IIS recognize IPV6 format address or should I add some settings at somewhere?
Using address literals in URLs is strongly discouraged. The best practice is to create a hostname in DNS with an AAAA record pointing to your IPv6 address.
I followed all kinds of instructions all day to get my first server up and running. I tested it on 3 devices and thought I had it... until my friend tried it and discovered "site can't be reached."
In double-checking on my end, I found that if I disconnected my phone from wi-fi, sure enough, I couldn't reach my server.
I realize there could be a million things wrong, but I don't know where to start. I am not even sure what additional information I should include to help find the issue. If I had to guess, I'd say I failed to open the firewall on my server port 80. But I really have no clue. Ubuntu is new to me.
Can you include details about your setup? How is the Ubuntu server configured? If it's your own hardware, have you forwarded the ports on your router? Do you have a Dynamic DNS server in place? Is there an internal firewall (ufw?). Is the Node.js server bound to the loopback? Is Nginx in proxy_pass mode?
As mentioned by the OP, the ports weren't forwarded.
I am trying to connect to a university server using a VPN client. I can connect to the client. Also, if I ping the server by name and by IP address, they both work:
ping servername
ping serveripaddress
However, I cannot access the server from the browser if I type:
\servername
\serveripaddress
and also I do not see anything in Network apart from my own computer. I changed my Workgroup to the correct Workgroup, and it still doesn't work.
Also, as my DNS suffix I use the domain name as well as the FQDN, but it doesn't work either.
I restarted after each of these changes, but it didn't help.
I read that when I have a VPN connection working and I am also able to ping the server to which I want to connect, it is most probably DNS resolution problem. But I do not know anymore what to do (I checked and tried the correct DNS suffixes).
Do you know what should I do more? I am using Windows 7.
Thank you.
It sounds like you're trying to use UNC pathing. Assuming that you're getting your network settings from DHCP, are you getting a WINS server?