What's new

No access to router with IP

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

FredTheDog

Occasional Visitor
IHi,

I have been using the guides here to configure my new router, information here is fantastic.......but

Was setting up port forwarding to get at a NAS box thru Aicloud. I have set something I shouldn't as I now cannot get to my AC66U using its IP address, I see a grey screen with the following:

Settings have been updated. Web page will now refresh.
Changes have been made to the IP address or port number. You will now be disconnected from RT-AC66U.
To access the settings of RT-AC66U, reconnect to the wireless network and use the updated IP address and port number.


Luckily enough I set up access from WAN and I can get to it with using https the DDNS name and port 8443.

I have rebooted the router and my machine, disabled Port Forwarding on the router, disabled WiFi on my mac and connected via ethernet directly to the router, router address is 192.168.0.1, my Mac's IP addr is 192.168.0.214. I can ping the router and telnet to it too with the same IP addr

What have I done????

Please help

update: I have loaded a config I saved from Saturday when everything was working perfectly and still cannot get access using IP addr on any browser, in fact I now cannot access with DDNS thru firefox, but I can with Safari and FireFox was working before I loaded the backup config
 
Last edited:
IHi,

I have been using the guides here to configure my new router, information here is fantastic.......but

Was setting up port forwarding to get at a NAS box thru Aicloud. I have set something I shouldn't as I now cannot get to my AC66U using its IP address, I see a grey screen with the following:

Settings have been updated. Web page will now refresh.
Changes have been made to the IP address or port number. You will now be disconnected from RT-AC66U.
To access the settings of RT-AC66U, reconnect to the wireless network and use the updated IP address and port number.


Luckily enough I set up access from WAN and I can get to it with using https the DDNS name and port 8443.

I have rebooted the router and my machine, disabled Port Forwarding on the router, disabled WiFi on my mac and connected via ethernet directly to the router, router address is 192.168.0.1, my Mac's IP addr is 192.168.0.214. I can ping the router and telnet to it too with the same IP addr

What have I done????

Please help

update: I have loaded a config I saved from Saturday when everything was working perfectly and still cannot get access using IP addr on any browser, in fact I now cannot access with DDNS thru firefox, but I can with Safari and FireFox was working before I loaded the backup config

Run this over telnet:

Code:
ps w | grep http

It should return the web server process. See if it shows a port number (i.e. httpd -p 8443), in which case that means you probably enabled HTTPS-only mode - you will have to use https://192.168.0.1:8443 (replace 8443 with the number after -p).
 
Thanks Merlin,

I see "httpd -s -p 8443" which I assume is what you refer to but with a "-s" as well.....whatever that means

With regards to Firefox no longer working I cleared the application cache where Firefox stores data from applications for offline use (Preferences > Advanced > Network) which had a reference to 192.168.0.1 and I can now get to the router with https.
 
Last edited:
Thanks Merlin,

I see "httpd -s -p 8443" which I assume is what you refer to but with a "-s" as well.....whatever that means

With regards to Firefox no longer working I cleared the application cache where Firefox stores data from applications for offline use (Preferences > Advanced > Network) which had a reference to 192.168.0.1 and I can now get to the router with https.

"-s" means SSL. So you disabled regular HTTP access and enabled HTTPS, that's why you were unable to access it. It only responds to https: and on port 8443 now.
 
Fantastic......Thanks Merlin

I knew I'd done something stupid somewhere, guess I didn't realise that setting Authentication method to HTTPS set access from both WAN and LAN....I'll go sit in a dark room
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top