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).
Related
I've got various websites on my local machine, and I'm trying to test a client within a VM that needs to access one of the sites. I've added a line to the VM's hosts file that makes localhost point to the Host IP Address.
All of the sites are on https with a certificate assigned to localhost and signed by a CA that's trusted by the VM.
The VM can access all of the sites, apart from one that's running on IIS Express. For the one that's running on IIS Express, I can access it fine with the IP Address or another hostname, but with localhost it comes back as forbidden.
I also put another line in the hosts file that points another domain at the same ip address as localhost, and that worked as well.
So on the VM:
https://localhost/Site1 works, points to another site running on regular IIS
https://localhost:44134 doesn't work, 403 Forbidden, points to IIS Express
https://10.0.11.10:44134 works, points to IIS Express
https://machinename:44134 works, points to IIS Express
https://different.domain.com:44134 works, points to IIS Express
I've checked the binding in IIS Express and it's like this, which I believe is correct:
<binding protocol="https" bindingInformation="*:44314:" />
And the urlacl is this, which I think is correct also:
Reserved URL : https://*:44314/
User: \Everyone
Listen: Yes
Delegate: No
SDDL: D:(A;;GX;;;WD)
Is there something special with localhost? The VM is running Windows 7.
Edit:
I've created a new Asp.net MVC app that runs on http (so not using https this time) and port 57811.
http://localhost:57811 doesn't work, 403 Forbidden, points to IIS Express
http://10.0.11.10:57811 works, points to IIS Express
http://machinename:57811 works, points to IIS Express
http://different.domain.com:57811 works, points to IIS Express
So the issue is nothing to do with https, or the specific site.
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 wanted to test my ReactJS + NodeJS website on another machine on my LAN, so I changed the server host ip from localhost to 0.0.0.0 as described in this answer. I noticed that although I could access the server from a remote machine, all I could see was the title and favicon (the rest was a blank page). I tried another approach of using the ngrok module as described here (which happens to be the answer to the same question as the previous link). I still got the same blank page.
The GET requests to the server are shown below (as shown by ngrok).
/landing is a page I was trying to access. Can someone explain whats happening?
PS: The server is running on a Mac and I'm trying to access the page on an Ubuntu machine. Also, I'm using this react-redux boilerplate. Webpack is also being used along with hot reloading.
Did you try changing port settings in firewall?
Go to firewall settings and allow the respective port for inbound
I've got a ServiceStack application that almost works when self hosted rather than to use IIS.
If I start the service and connect from a remote machine to the ip address of the PC http://10.0.0.5:81 then it's fine and everything works as expected.
However if I start the service and the first connection happens to come in on localhost (say because I'm testing the service is working after it's been installed) then all remote machines get redirected to http://localhost:81. The same is true if I used 127.0.0.1:81 with remote PC's getting redirected to the loop back address.
At that point all I can do is restart the service and connect from a remote machine first to get it working again.
Is there some way to disable what appears to be this caching?
ServiceStack tries to infer the BaseUrl for your services which it can only do at runtime which it then caches for subsequent requests. You can specify it to use an explicit Base Url instead with:
SetConfig(new HostConfig {
WebHostUrl = "http://10.0.0.5:81",
});
I have a node app using vineapple to pull in vine posts. On my local machine all pulls in fine but for some reason whenever I call out to api.vineapp.com on my server, it always fails.
I have tried also just using wget to see if I can access it but it is always returning back a 504 Gateway Timeout Error.
I also manually setup the hosts file so it uses the same ip that my local machine was hitting but all requests simply never get a response back.
Has anyone ever had this experience before with vineapple? My server is simply a cloud server at rackspace and I know port 80 and 443 can be reached out on so not sure really where else to look.