Is anyone having problems logging in....

[a-m-k]

I have to search for my username + macrumors online in order to log in. Yes, I know I currently have an issue with my MBP. (I am unable to read what's taking up the space on my HDD.) I had a bracket fixed awhile ago, but it didn't help.

I just tried to go to the macrumors website and log in on my iPhone and it works just fine. My MBP shut down on its one one week ago today. Can my MBP (which at the moment can't get a HDD reading) be the problem since there is no problem logging on to this site from my phone? (I haven't had the time to make a new genius bar appointment since it's so close to Christmas....)

 

[arn]

So what exactly happens when you try to log in with your MacBook Pro?

arn

 

[a-m-k]

I can't log into the site by going to www.macrumors.com. However, I bookmarked forums.macrumors.com and can log in there.

If I go to www.macrumors.com I get https://www.macrumors.com/cgi-bin/redirect.ha. That page won't work. I don't know if this has to do with the fact that I don't have a listed HDD right now. Its just a bad time of year for me to get it fixed or even upgraded to a new MBA.

Every other site I go to seems to work fine, but its just odd that the macrumors page is so complicated for me to log into.

 

[arn]

I can't log into the site by going to www.macrumors.com. However, I bookmarked forums.macrumors.com and can log in there.

If I go to www.macrumors.com I get https://www.macrumors.com/cgi-bin/redirect.ha. That page won't work. I don't know if this has to do with the fact that I don't have a listed HDD right now. Its just a bad time of year for me to get it fixed or even upgraded to a new MBA.

Every other site I go to seems to work fine, but its just odd that the macrumors page is so complicated for me to log into.

The redirect is a weird router issue we've seen before

https://forums.macrumors.com/threads/page-not-found-on-front-page-on-iphone.1680518/#post-18455478

 

[arn]

Clearing cache or quiting and restating Safari may help

 

[a-m-k]

Clearing cache or quiting and restating Safari may help

I'll try that, thank you.