What's new

RT-N66U Can't login to GUI

  • 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!

Skeptical.me

Very Senior Member
Hi,

I have an RT-N66U Merlin 380_70 that I've setup and each time I setup the router I can't login to the GUI. I've reset and setup the router 4 times and still I cannot login to the GUI. I'm definitely using the correct login details I set.

Has anyone encountered this before?
 
Do you get the login page? Are you sure the router is at the IP address you’re typing in? You’re trying to login by http and not https I assume, but did you also try on port 8443?

This has cropped up before ( though possibly not for the same reasons). I get quite a few hits when I search in the forum for unable to login, but on a cursory look, many are referring to https.

And you’ll have tried on other browsers.

Can you ping the router? (Can you normally ping it, though?)
 
Last edited:
The character limit is 16 for the password. Make sure your password is 16 or less.
 
Do you get the login page? Are you sure the router is at the IP address you’re typing in? You’re trying to login by http and not https I assume, but did you also try on port 8443?

This has cropped up before ( though possibly not for the same reasons). I get quite a few hits when I search in the forum for unable to login, but on a cursory look, many are referring to https.

And you’ll have tried on other browsers.

Can you ping the router? (Can you normally ping it, though?)


Hi,

Yes, I see the login page on a HTTP connection (NOT https) ... the address is 192.168.1.1

I can ping the router.

The password is under 10 characters.

I've used a few passwords as simple as 1234!@#$ and a more complex password.

I have use Safari, and Firefox to try and login.

The error I see is " * Invalid username or password"
 
Hi,

Yes, I see the login page on a HTTP connection (NOT https) ... the address is 192.168.1.1

I can ping the router.

The password is under 10 characters.

I've used a few passwords as simple as 1234!@#$ and a more complex password.

I have use Safari, and Firefox to try and login.

The error I see is " * Invalid username or password"

So, having setup up the router, you had no problem initially logging in as admin/admin, but after you customised the username and/or password, that’s when you hit the problem?

Some thoughts - you’ve probably already done.

Can you ssh in using the new password, assuming you set up LAN-only ssh access?

Clearly, you’ll be resetting again to try and solve it; what about, instead of typing in the new username and password during setup, you paste them in from a file or password manager, and then, when you try to log in later, you similarly paste the credentials in (at least that eliminates any typing/keyboard problems).

Assuming you changed the username from admin, next time just change the password only from admin to, say, test. And see if it can cope with a four-letter password (just for troubleshooting). By now, though, I suspect you’d have a more appropriate four-letter word in mind.
 
Last edited:
Hi,

Yes, I see the login page on a HTTP connection (NOT https) ... the address is 192.168.1.1

I can ping the router.

The password is under 10 characters.

I've used a few passwords as simple as 1234!@#$ and a more complex password.

I have use Safari, and Firefox to try and login.

The error I see is " * Invalid username or password"

The example password is most likely to be the cause of the problem.

Try alphanumeric only, 16 characters.
 
So, having setup up the router, you had no problem initially logging in as admin/admin, but after you customised the username and/or password, that’s when you hit the problem?

Some thoughts - you’ve probably already done.

Can you ssh in using the new password, assuming you set up LAN-only ssh access?

Clearly, you’ll be resetting again to try and solve it; what about, instead of typing in the new username and password during setup, you paste them in from a file or password manager, and then, when you try to log in later, you similarly paste the credentials in (at least that eliminates any typing/keyboard problems).

Assuming you changed the username from admin, next time just change the password only from admin to, say, test. And see if it can cooe with a four-letter password. By now, though, I suspect you’d have a more appropriate four-letter word in mind.

Hi,

I solved it, the problem was I couldn't login to the router's GUI from my Mac, so I tried on my iPhone (Safari) and was able to login. I don't know why this was the case.

So I checked Administration>System>Allow only specified IP address to see if it was enabled and the Mac wasn't included. The setting wasn't even enabled, however, I enabled the setting and added the Mac's IP address and then I was able to login to the GUI from my Mac.

Problem solved.
 
Hi,

I solved it, the problem was I couldn't login to the router's GUI from my Mac, so I tried on my iPhone (Safari) and was able to login. I don't know why this was the case.

So I checked Administration>System>Allow only specified IP address to see if it was enabled and the Mac wasn't included. The setting wasn't even enabled, however, I enabled the setting and added the Mac's IP address and then I was able to login to the GUI from my Mac.

Problem solved.
Excellent. Such snags are really challenging and definitely satisfying when you crack them.
 
Hi,

I solved it, the problem was I couldn't login to the router's GUI from my Mac, so I tried on my iPhone (Safari) and was able to login. I don't know why this was the case.

So I checked Administration>System>Allow only specified IP address to see if it was enabled and the Mac wasn't included. The setting wasn't even enabled, however, I enabled the setting and added the Mac's IP address and then I was able to login to the GUI from my Mac.

Problem solved.
I suspect it was more the restarting of httpd than enabling the restrictions since you wouldn’t have been able to get to the login page if you were truly blocked, since it creates firewall rules for those restrictions.

All’s well that ends well!
 

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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