Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

yahoo

  • 2 பதிலளிப்புகள்
  • 2 இந்த பிரச்னைகள் உள்ளது
  • 32 views
  • Last reply by jscher2000 - Support Volunteer
  • Archived

caddofab
caddofab

When I try to sign into yahoo account it says the following:

Something's gone wrong We may be having trouble with your connection. Connecting your device to Wi-Fi could help fix the issue or try again later. If you were using an app, close this page. Otherwise, start over.

the only way I can sign in is to change my password. If I log out and try again to log in it does the same error.

When I try to sign into yahoo account it says the following: Something's gone wrong We may be having trouble with your connection. Connecting your device to Wi-Fi could help fix the issue or try again later. If you were using an app, close this page. Otherwise, start over. the only way I can sign in is to change my password. If I log out and try again to log in it does the same error.

All Replies (2)

bwc125
bwc125

I have the same problem. If I switch to MS Edge however my email works fine. In Firefox when I type in https://mail.yahoo.com and hit enter the address changes to https://mail.att.com. I then get the "Something's gone wrong" message.

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer

Other AT&T customers have also reported problems. For example:

I don't know the reason that Yahoo circles back to AT&T's site (where you get the error message).

Another user observed that they can sign in normally when using a private window. This may be consistent with your observation about your password in that some data saved during your Yahoo/AT&T session -- for example, in the web content cache, in a cookie, or in local storage data set by the site -- causes the problem.