Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

yahoo loads log in click mail 404 error page not found why?

  • 2 odgovori
  • 10 ima ovaj problem
  • 2 views
  • Posljednji odgovor poslao lorddragonstar

more options

I upload yahoo site, log in, click 'mail' and am given a '404' error; page not found... This does NOT happen on Chrome or IE, but the pages of yahoo on IE suck and Chrome won't let me have a single toolbar even though there are all sorts of claim you can have one... (sorry) WHY doesn't FIREFOX let yahoo mail load? I LOVE FIREFOX and ALL THINGS MOZILLA, but after I ran into crappy-sappy babylon... it put a toolbar on IE, CHROME and MOZILLA... I had to delete everything associated with them all, get toolbar sweepers and better uninstall programs to weed their junk out and now MOZILLA, FIREFOX, rather warns no one and makes me submit this rather than help

I upload yahoo site, log in, click 'mail' and am given a '404' error; page not found... This does NOT happen on Chrome or IE, but the pages of yahoo on IE suck and Chrome won't let me have a single toolbar even though there are all sorts of claim you can have one... (sorry) WHY doesn't FIREFOX let yahoo mail load? I LOVE FIREFOX and ALL THINGS MOZILLA, but after I ran into crappy-sappy babylon... it put a toolbar on IE, CHROME and MOZILLA... I had to delete everything associated with them all, get toolbar sweepers and better uninstall programs to weed their junk out and now MOZILLA, FIREFOX, rather warns no one and makes me submit this rather than help

All Replies (2)

more options

Clear the cache and the cookies from sites that cause problems.

  • "Clear the Cache": Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
  • "Remove the Cookies" from sites causing problems: Tools > Options > Privacy > Cookies: "Show Cookies"
more options

Thanks for the reply.... No help, unfortunately... Apparently it's way too difficult for Mozilla to even grasp, let alone solve