Help! Turned on https access and now can't use web interface

[Cthomsen]

I was playing with some of the administration options and turned on Web access from the WAN and changed the authentication to https.

Unfortunatley it presented a different port then the standard https port but I did not pay attention before I applied it (I think it was a port in the 500-600 range. It also apparently applied these changes to web access from the LAN also.

Now I cannot log in with http://192.168.1.1 or https://192.168.1.1 without the proper port number. I can still get to the router via ssh so is there a file or nvram variable I can look at or reset to be able to access the web interface again?

I just don't want to have to reset all the settings to gain acess again!

Thanks

 

[wiz]

log in to your asus with ssh and do a netstat -l. It will show all the listening ports on your asus so you have a chance of figuring out what port you have set it to.
or do a nvram show |grep http to see all http settings.

good luck!

 

[seth_space]

back to default settings is an option, depends on how much work your current config costs.

Reset button: pressing the Reset button while power-up, will put this ASUS router in recovery mode.
That is: press and hold the reset button, keep pressing the reset button while plugging in the power, then keep holding the reset button pressed for about ten seconds until the power led is blinking slowly, then release the reset button. The router is now in recovery mode.

WPS button: pressing the Red WPS button while power-up, will clear the NVRAM. All settings are stored in NVRAM of this ASUS router. Clearing the NVRAM is the most efficient way to reset the router to default settings.
That is: press and hold the WPS button, keep pressing the reset button while plugging in the power, then keep holding the WPS button pressed for about ten seconds, then release the WPS button. All settings have now been wiped, and default settings will be used.

 

[RMerlin]

I was playing with some of the administration options and turned on Web access from the WAN and changed the authentication to https.

Unfortunatley it presented a different port then the standard https port but I did not pay attention before I applied it (I think it was a port in the 500-600 range. It also apparently applied these changes to web access from the LAN also.

The default https port is 8443.

 

[Cthomsen]

Thanks guys.

Net stat showed https listening on all ports but nvram show showed that https_lanport and misc_httpsport_x set to 8443 just as RMerlin indicated.

I was able to connect with https on this port with no problems.

But now I have a smaller secondary issue. If I try to change any of these settings on the administration > system page I get a pop up indicating that

https://192.168.1.1 This port has been used for HTTP LAN port

And the change is not made.

This happens if I try to change the authentication method, the HTTPS LAN port, change web access from WAN or change the port for web access for wan.

Apparently I can only made these changes from a ssh shell if I knew how.

At any rate I can live with the current changes.

All this because some late night experimentation.

 

[RMerlin]

But now I have a smaller secondary issue. If I try to change any of these settings on the administration > system page I get a pop up indicating that

https://192.168.1.1 This port has been used for HTTP LAN port

And the change is not made.

This happens if I try to change the authentication method, the HTTPS LAN port, change web access from WAN or change the port for web access for wan.

This is a known bug in Asus's build 354 code. I already fixed it on my end for a future Asuswrt-Merlin release. Asus incorrectly checks for port conflicts - if you disable regular HTTP, then it tries to ensure that HTTPS uses a different port from... HTTPS.

 

[pepemosca]

This is a known bug in Asus's build 354 code. I already fixed it on my end for a future Asuswrt-Merlin release. Asus incorrectly checks for port conflicts - if you disable regular HTTP, then it tries to ensure that HTTPS uses a different port from... HTTPS.

Ha!
I send the issue to the ASUS support and they told me to do an RMA because the router was broken.

Of course, I laught!

 

[RMerlin]

Ha!
I send the issue to the ASUS support and they told me to do an RMA because the router was broken.

Of course, I laught!

Unfortunately, I'm not really impressed by Asus's first line of tech support (to be honest, I've rarely been impressed by ANY company's first level tech support). They seem to be too eager to fallback to "Send it for RMA" whenever someone reports an issue which they can't troubleshoot. I think they should escalate many of these issues to a second level rather than always dismiss it as defective hardware - too often I've seen it happen.

 

[Kenneth]

This worked for me in the last firmware after a factory reset:

"Change both the port number in "HTTPS Lan port" and the "Port of Web access from WAN" fields simultaneously. Then before hitting apply, I made changes to other fields I wanted and then hit apply"

 

[redsn0w]

If anyone else is having trouble logging into their Asus router after enabling HTTPS, try this first before resetting it:

Open your web browser and put this into the URL bar: "https://192.168.1.1:8443"
Replace the IP address with your routers IP (default is 192.168.1.1)
Replace the port with the port number you assigned in the web interface (by default it is 8443 as previously pointed out)

The reason I was having trouble is that I forgot to put the "https://" first in my URL bar, something pretty simple but easily forgotten when switching to HTTPS.

I hope this helps someone else out there so they don't have to reset their running-config, especially if they forgot to enable SSH or make a backup of running-config like me

Cheers