I am puzzled as I cant find this solutions or even the name of the process. I used to work in an organization where there administrator had ISA server setup to use proxy in such a way that the internet would stop working if the proxy is removed from the browser. I want to do the same thing... Any help will be highly appreciated.
Port 80 is probably blocked in the firewall in the router
Related
I am using GCP, nginx and domain name from "name.com" to deliever my website.
It can be reached on mobile network but doesn't work with wifi.
Although on some wifis you can reach my site with around ~60% (from those i have tests) you cant.
It might have to do something with DNS / DNSSEC but its litearly a guess, I am clueless.
Hey everyone so I have found the problem.
When I looked online for best practice its recommended to use different ports for the backend and frontend.
apparently the port used for the backend was blocked by some routers.
Now the backend and frontend use the same port and it is fixed.
Hopefuly it will help other people who are getting the same problem.
Could you try lower the TTL to 300 seconds for your domain in name.com? It could be that DNS has an old cache which did not yet point to your nginx instance/location. Or you could wait out the default TTL which is probably 12-24 hours.
I'm not sure I can adequately explain my dilemma, but here goes...
Our company has its own web server at xyz.com. I have a Win 7 Pro machine running a non-HTTP server program that communicates with an iPhone app used by our field crews. The path to this machine from outside the network is abc.xyz.com, and it's set for port 5000. The app, then, is programmed to exchange data (ASCII only) with the server at abc.xyz.com:5000. The server program is written in VB, and the system works very well like that.
What I would like to do now is to add IIS to this same machine and open it on port 5001, so I can run asp.net pages that will enhance the functionality of the app for our crews. The URL would be abc.xyz.com:5001, and they will access it through their phone browsers.
I have IIS 7.5 installed on the machine, and I have started it running with the "default web site," and I have the binding set for port 5001. So far I am able to access the IIS "Welcome" page only from the same machine. I can't get it to come up on any other machine either inside or outside the network.
In searching for clues for this problem, all I read indicates that it's pretty much a snap to get a web server running on your Windows 7 machine. But it hasn't been so much a snap for me. I've checked the sharing settings and the security settings, they seem to be ok, as best I can tell.
I am hoping that someone will help me identify some obscure setting somewhere that I am overlooking and get this going. But I also even wonder if this is something that can't be done, i.e. because there's another server program using the same path running on port 5000.
By the way, I am not the network administrator. I try to avoid getting him involved because he's difficult to work with. I am hoping that this is just between me and my server.
Thanks for any insight anyone can give me.
You mention that you can access the website from the machine itself on port 5001, but you can't access the site from another computer within the same network - this suggests to me that the Windows 7 built-in firewall is blocking the request - as it's a non-standard IIS port.
You should configure the firewall to allow incoming requests on port 5001. Open a command prompt (as administrator) and run the following:
netsh advfirewall firewall add rule name='IIS Website on Port 5001' dir=in protocol=TCP localport=5001 action=allow profile=any
I found the answer elsewhere on StackOverflow. I needed to add IUSR to the list of authorized users. So far I have tested it on my iPhone browser using 3G and it came through. Seems likely that it will work from anywhere, but I'm not yet ready to declare total success.
We have deployed our website to the live webserver, Windows Server, IIS 7.5. Website asp.net, .NET 4.5
I have configured the website bindings to allow https requests for this website.
Asked the hosting provider to open up the port 443.
I can access the website over internet with port 80, no issues at all. (http://mysite.com)
But I can not access via https, (https://mysite.com).
But I can access the site via SSL from the server itself, that means SSL configurations are fine.(https - localhost)
But I can telnet (telnet mysite.com 443), it responds to GET request via telnet.
I have rechecked the certificate and changed it to a self-signed certificate, issue is still there.
These requests not being tracked in IIS logs as well, seems like the request is not reaching IIS. Hopefully something goes wrong before it reaches the server.
But, when I access the website as http://mysite.com:443, it works.
I m bit confused with this behaviour. Obviously the port 443 is open by the hosting company. But something is wrong with requests over HTTPS, which is supposed to send a request to port 443. Please help.
Because your site is working when you access http://mysite.com:443, I am almost sure that you created wrong binding on IIS. Instead of selecting https from combo box you selected default http.
There is a tutorial on how to do this on youtube: Changing IIS 7.5 Bindings by David Johnson
You've establish that the port is open and the hostname binding is there, otherwise http://mysite.com:443 would not work. Its the SSL part that's not working, hence you can connect directly by port and telnet (port 443 but not SSL) but not a browser via https. It's only a browser connecting to a https url that will expect SSL.. I'm pretty sure I've had the same issue, but cannot recall the exact cause but it was definitely related to an invalid SSL configuration or SSL binding.. The behaviour was like there is no connection, nothing, which is unusual, its the bad config causes the browser to abort the connection. If I remember what, I'll update or comment below.
So you can access the site using https://localhost? Your question is not quite clear on this point... what is the exact URL you are using? If it's https://localhost, that is actually an indication that your certificate is configured incorrectly. You seem to be interpreting this as an indicator that it's working OK and that is not the case. The domain name is tied to the certificate and SSL will work only when accessing the site using that domain name. So if it works for "localhost", something is wrong.
Finally I found the solution. Issue was a setting in the load balancer of the hosting provider. I have asked the question from them and they have figured out the issue. Anyways it was a good learning curve for me. And this knowledge is going to help others.
The firewall was already allowing both HTTP/HTTPS, which is why we could telnet through and run a GET / and still pull down content from the 404 page of the IP address.
It appears there was a certain profile applied to the HTTPS configuration in the load balancer which would only work for HTTP, so they have disabled that.
When they set this up for HTTP and HTTPS they were not able to test HTTPS, because to do so would require an SSL certificate in IIS - which it appears we have already provided.
Thanks everyone for your help on this!
I am using Weblogic seever for local testing..
I cannot cannot access http://my_machine_name in Firefox (e.g. http://xyz123)
The same can be accessed in IE/Safari
Please help me. Thank you
There's no fundamental reason why one browser would work and the other fail, so it's likely down to configuration of the browsers.
Following up JoseK's question - can you access your local WebLogic Server instance using an IP address rather than the machine name?
Also, is it possible that you've got a corporate HTTP proxy server configured for Firefox, but that it's not being used in IE? (I've hit this before on client site myself)
Last of all, can you definitely check via WebLogic Server's server log files or netstat that it's definitely binding to your public IP address on port 80 (and not using something else like a loopback address, for example?)
I am not sure if it has something to do with your problem but i know that firefox has its own dns-cache. Maybe (and only maybe) would it help to turn it off.
I have tried to access a website that i created in my xp machine that have iis 5.1 from the LAN , but without any success i have tried what is suggested in the following link How to access your website through LAN in ASP.NET , but also without any clue . I open my site in my PC(locally) like this "192.168.1.252/pse" and it works , but from other pc in the LAN , its not displayed at all.
Any Help will be most appreciated.
Thanks,
Saed
Is your Windows Firewall turned on?
You say, "its not displayed at all". What happens instead of it being displayed? Is there an error message?
Most likely, your firewall software is blocking external access. If external users can find your machine using ping, then that suggests a firewall is blocking access.
Please do what the two previous posts suggested, check to see if you can ping your computer from a different computer within the network and then check your firewall also.
When you are done checking the above suggestions, if you still have trouble viewing your page from a different computer, check to see if your computer has port 80 open. And if it is using port 80 and everything looks ok, please provide the error number you are receveiving, I am guessing it is 404 - Page not found.
Hope this helps!
It was firewall and Antivirus problem , they were blocking the port 80.
Thanks All for your Help.
Saed