I'm a satisfied no-ip DDNS subscriber happily using DD-WRT.
In the no-ip settings, I have an A Name record (hostname.com) that no-ip kindly shoots straight to my house.
I also have a www C Name record (www.hostname.com) which gets some magic applied then is sent to hostname.com:webServerPort (hostname.com:8080 in my case).
www.hostname.net goes to my web server. The port 8080 traffic is handled magnificently. That is awesome.
When I type in hostname.com that is translated to my ever changing IP by my DDNS service, it takes me to the control panel of my router which listens for web browser traffic on none other than port 80--
Not so awesome. Sadness actually.
I had everything working again otherwise.
BACK UP YOUR SETTINGS.
You're going to be in there anyway, jeez man it only takes a few seconds.
I checked HTTPS and unchecked HTTP in Administration > Management > Web Access > Protocol
What this does for us is that it sets the router to listen for requests of the web GUI, the control panel, on port 443 and not port 80 anymore.
Save, Apply Settings, Reboot.
I do it whether I really need to or not, this is my house-- not a Data Center of a Fortune 500.
Now the router needs accessed with https://192.168.1.1 , heads up a certificate warning will probably pop up. The router is self certifying itself for encrypted web traffic and it is not on the preferred list of SSL certificate providers, so click whatever you need in order to continue.
After that I rerouted port 80 (since that is where the naked hostname.com from a web browser goes) via the NAT via TCP only to my webserver IP on port 80 in NAT / QoS > Port Forwarding > Port Forward > Forwards
Save, Apply Settings, Reboot.
BACK UP YOUR NEW SETTINGS.
Pure awesomeness. Enjoy.
In the no-ip settings, I have an A Name record (hostname.com) that no-ip kindly shoots straight to my house.
I also have a www C Name record (www.hostname.com) which gets some magic applied then is sent to hostname.com:webServerPort (hostname.com:8080 in my case).
www.hostname.net goes to my web server. The port 8080 traffic is handled magnificently. That is awesome.
When I type in hostname.com that is translated to my ever changing IP by my DDNS service, it takes me to the control panel of my router which listens for web browser traffic on none other than port 80--
Not so awesome. Sadness actually.
I had everything working again otherwise.
BACK UP YOUR SETTINGS.
You're going to be in there anyway, jeez man it only takes a few seconds.
I checked HTTPS and unchecked HTTP in Administration > Management > Web Access > Protocol
What this does for us is that it sets the router to listen for requests of the web GUI, the control panel, on port 443 and not port 80 anymore.
Save, Apply Settings, Reboot.
I do it whether I really need to or not, this is my house-- not a Data Center of a Fortune 500.
Now the router needs accessed with https://192.168.1.1 , heads up a certificate warning will probably pop up. The router is self certifying itself for encrypted web traffic and it is not on the preferred list of SSL certificate providers, so click whatever you need in order to continue.
After that I rerouted port 80 (since that is where the naked hostname.com from a web browser goes) via the NAT via TCP only to my webserver IP on port 80 in NAT / QoS > Port Forwarding > Port Forward > Forwards
Save, Apply Settings, Reboot.
BACK UP YOUR NEW SETTINGS.
Pure awesomeness. Enjoy.
No comments:
Post a Comment