This is probably something very simple. I set up a simple ASP-based web server on Server 2012R2 and IIS6. The IP address of the web server is 192.168.18.142. I then opened up a browser (Chrome). Any of these URLs bring up the website on the web server just fine.
http://localhost/
http://127.0.0.1/
http://192.168.18.142/
Then I went to a different machine (behind the same router), opened the browser and tried to bring up:
http://192.168.18.142/
However I received this error in the browser:
500 - Internal server error. There is a problem with the resource you are looking for, and it cannot be displayed.
I even tried turning off the Windows Firewall on the web server to no avail. Any idea what configuration settings to look at?
Why does the URL work when on the web server but not from other machine?
Related
I purchased a VPS server, installed IIS, setup domain and published static index.html page. It worked if I go to mydomain.com but 1 or 1.5 hours later it stopped working and I can only see the message The site can't be reached.
The VPS is accessible via Remote desktop and if I locally run the IE I can access mydomain.com but It does not work from outside of the VPS.
If I reboot the VPS server then after a while the page can be accessed again but again it lasts for around 1-1.5hours.
What could be the reason of this?
If it is caused by idle timeout, then your index.html page will not be displayed, this error means that your browser cannot establish a connection with the website you try to reach, because your Internet connection has been interrupted or because your internet service provider has blocked the access to the website.
You can try the following methods to solve this error:
Restart your Internet Router.
Try to visit other websites, to make sure that your Internet connection is working.
If you own another computer/device in your place, then try to visit the website where your receive the "ERR_CONNECTION_CLOSED" error, in order to make sure that the site you 're trying to visit is not blocked from your ISP.
If you have setup a VPN connection, then disconnect from it.
Temporarily disable the Firewall application.
I am trying to send requests to Zoom API via a HTTP request. When testing on my local machine it works perfectly but when I try it on our production server I get the following error:
msxml6.dll error '80072efe'
The connection with the server was terminated abnormally.
We use Cloudflare for security with our website, does anyone know what the resolution here maybe?
The server is running on Windows Server 2008 R2 using IIS 7.5.
I found the cause of the issue.
It wasn't CloudFlare, it was the server object I was using in my function.
I changed the following line from this:
Set ServerXmlHttp = Server.CreateObject("MSXML2.ServerXMLHTTP.6.0")
to this:
Set ServerXmlHttp = Server.CreateObject("MSXML2.XMLHTTP.6.0")
Problem solved.
I have one windows server already running sharepoint on 80/443 and the site works correctly.
We're trying to add more functionality by installing NodeJS and Apache
I've set apache to listen on 8080 and the default website comes up.
Node is running on 3000 and I can access the explorer that way as well.
My questions come from this. The server has a complete certificate chain installed on it and https://:8080 comes up correctly, but I can't get the node stuff to work on https: Secondly it appears while I have proxy pass set up correctly within my httpd.conf, either something is wrong within that as if I goto the https://:8080 /api/and anything beyond that, I get 503 errors and the page can't be displayed.
I'm unsure what I'm doing incorrectly here as from reading the documentation on proxy module, it seems that everything is setup and configured correctly.
Netstat shows listening on 3000 and 8080 and 80/443 for my SharePoint farm.
I had to configure the ssl settings for the proxypass to use the IP address of the local machine. After doing that I was able to connect correctly.
This allowed for connecting on :3000 via telnet to the localmachine and allowed for explorer to be viewed with https://:8080 the correct way enforcing our certificates.
I am checking accessing an IIS on a local system. When I deploy an application to the server and check locally using localhost and local IP it works fine. When I open the port it is listening on via my router and try to access via the router IP it always returns a 400 error. The router has been configured to forward the call the the system IS is on. I can test the port with a port checker and it is showing as being open. I read messages that indicated that the header may not be present and would cause this type of error if multiple app are deployed. I tried to put headers on the apps but no difference. I then cleared all the apps except the original one that comes with IIS. But still cannot access the app. Can someone indicate what I'm missing with the IIS configuration (as I'm feeling it must be IIS related).
I hired a VPS (Windows Server 2008) with the aim of hosting a website. So i configured IIS 7.5 to run a html website. The website reads data (HTTP GET requests) from a little node.js application running on the same VPS on port 3000. I am getting the data as follows:
$.get( "http://localhost:3000/myfunction", function( data ) {
});
Inside the VPS if I go to chrome a type localhost it works perfectly. On the other hand if i insert the VPS's IP address the HTTP calls are not working...
Chromes JS Console says:
Failed to load resource: net::ERR_CONNECTION_REFUSED http://localhost:3000/myfunction
I need the node.js app not to be visible from outside the VPS so that sensible data in the code is not reachable...
I finally managed to solve this using a reverse proxy (IIS's ARR and URL Rewrite) as it is explained in the following guide:
http://www.gitshah.com/2013/06/how-to-use-iis7-as-front-end-to-java.html