Buzz
From hot news, entertainment to sports, and politics, before spreading worldwide, they will first appear on Twitter. This is the favorite social network of many people worldwide, and users can tweet about anything they want. Just like any other day, you feel like tweeting something on Twitter, but suddenly, you're greeted by a screen containing the message 'Something went wrong. Try again.' You've tried hitting Try Again, pressing F5 multiple times, and even right-clicking, then selecting reload, but Twitter keeps displaying the same error repeatedly. So how do you fix this issue? You can try applying one of the two methods presented in this article.
Fixing the Twitter Error: 'Something went wrong. Try again.'
1. Update your computer's time
Displaying incorrect local date and time can affect some websites like Twitter when the time on your computer differs from the server time of the service. Therefore, adjust and update the time accurately on Windows to fix the 'Something went wrong. Try again.' error with the following steps or refer to how to adjust your computer's time here.
- Press Windows + R to open the Run dialog, type control timedate.cpl and press Enter.
- In the Date and Time window, select Internet Time and click on Change settings.
- Type pool.ntp.org in the Server field and click on the Update now button.
2. Clear Twitter cookies from your web browser
If adjusting the time doesn't resolve the issue, you'll need to delete cookies stored in your web browser as follows:
- Visit the website https://www.twitter.com/ in your web browser.
- Click on the lock icon in the address bar and select Clear Cookies and Site Data.
- A list of domains related to Twitter will be displayed. Click the Remove button to delete cookies and website data stored in the browser's cache.
- Restart your browser and access Twitter again. You may need to log back into your Twitter account.
If you've tried the above two solutions and Twitter still displays such an error, consider switching to a different web browser. This issue could also stem from Twitter, and if so, there's nothing else you can do but wait for their engineers to resolve the issue.
