- Contact Us
I'm a newbie at this, working for an employer. We've been struggling trying to get our webserver/reservation system up and running for a few months. I won't fill this with all the steps I've fumbled through to get to this point. Last week, we started out with a dynamic IP, bought DYN Standard and our own domain. Enabled port forwarding on the router for ports 80 & 443. Enabled firewall rules in Norton NIS 2012 to allow 80 & 443. After discovering we still couldn't access the Internet, we contacted the ISP (Telus) and got a static IP.
Now, we can finally access our site at http://northernmotorinn.ca, but cannot access https which we need for credit cards. I've used online openport tools to check 443 and get a message that it is closed/blocked. The ISP says it doesn't block ports on a static IP. Is there something in DYN Standard that blocks port 443? I have an SSL certificate installed on our webserver, with a mismatched name (long story, holes in setup advice) - shouldn't I be getting a certicate warning when trying to connect to https? All I get is "server taking too long to connect..." error.Thanks for your help
Answer by Cry Havok · Jul 14, 2012 at 08:23 AM
Standard DNS is just a DNS service, once a hostname is resolved to an IP address it has no involvement in what happens - in short it cannot block any ports.Are you forwarding port 443 to the same computer as port 80? Do your port forward settings look identical other than the port number? Can you connect to the web server on port 443 internally? Have you checked the firewall on the web server?
Answer by Cry Havok · Jul 14, 2012 at 07:30 PM
I assume in your web browser you can use
https://192.0.2.5/ (or whatever the IP of the IIS server is)? Or, does it only work from the IIS server?
Answer by RotBlitz · Jul 15, 2012 at 12:05 PM
Your port 443 is open and serviced. However, your server doesn't seem to speak HTTPS on this port, but something else. You need to configure IIS the right way to speak HTTPS. Best is to start getting it work from inside your LAN.
Answer by Suzy · Jul 14, 2012 at 06:50 PM
I figured it probably didn't block any ports, but needed verification.
Yes, forwarding on both ports look identical other than the http & https types. Internally, we can only see port 80 unless I go into IIS and browse *.443 - then on my browser I finally get the message about the certificate error. From that error message I can then select the "continue to this website" and see the right web page. Is there something in IIS I possibly missed? Or is port 443 naturally blocked for public viewing because of the certificate error? I've been assuming I should see this certificate error/navigation blocked on any computer, external or internal, that tries to view https://northernmotorinn.caThe firewall - both ports are set on the same rule, to allow connections to/from other computers.
dyndns not resolving ports 1 Answer
Standard SMTP Exchange 2010 2 Answers
DVR not connecting 1 Answer