Firefox won't let me login into my gmx email - it insists on diverting me to the mobile app instead and adjusting history doesnt help!
I posted this problem last week and tried the solution suggested to right click in the history menu and use the Forget About This Site option. The mobile app site that I was being diverted to wasn't listed in the history, and neither was gmx.com! Nothing I do will make firefox allow me to login to my regular email, so when I want to login to my gmx email, I have to use IE. I notice other people are also having problems with firefox and gmx. For some reason, firefox isn't able to function with gmx. Are firefox developers looking into this? I've already had to remove firefox as my default browser due to the PDF problem, now I can hardly use it at all due to the gmx problem.
ప్రత్యుత్తరాలన్నీ (2)
I don't have an account in GMX.com, but i tried the login page, it works fine for me.
Reload the webpage while bypassing the cache
- Hold down the Shift key and click the Reload button with a left click.
- Press Ctrl + F5 or Ctrl + Shift + R (Windows and Linux)
- Press Command + Shift + R (Mac)
Clear the cache and the cookies from sites that cause problems.
Clear the Cache: Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
Remove Cookies from sites causing problems:
- Tools > Options > Privacy > Cookies: "Show Cookies"
Thank you for your reply. I also can get to the login page just fine, but when I put in my login info and click "login" I am then diverted to the mobile site. You couldn't go far enough to elicit the diversion, because you can't login. HOWEVER, i think I resolved the problem in another way that probably did what you thought. I was using a bookmark to get to GMX. I was getting to the right GMX site - until I logged in, at which time I was diverted. So I deleted the bookmark, closed the browser, reopened it and retyped in gmx.com and went to the exact same gmx site, but now when I logged in, I was taken to my proper email. So by removing the bookmark, I must have cleared the cache, etc. Hopefully, it will stay working correctly!