How To Resolve TweetDeck Connection Issues: “Unable to connect. Please check your network.”


When it comes to desktop Twitter clients there aren’t many options. If you’re looking for a freebie there are even fewer choices. TweetDeck is far from perfect but it’s one of the better desktop clients available and it’s the one I’ve come to rely on when I’m not using my iPhone or iPad. Back in October I upgraded my pc’s to Windows 8. After reinstalling TweetDeck I was confronted with a fatal error; TweetDeck failed to login to my account and displayed the error message “Unable to connect. Please check your network.” Tweetdeck connection issues are not limited to Windows 8. I’ve seen similar issues on Windows 7 — but this was the first time the issue failed to work itself out. I tried reinstalling TweetDeck. I tried manually setting firewall rules for TweetDeck. I tried running TweetDeck as Administrator. Nothing resolved the error. Weeks after installing Windows 8 I was still without my precious TweetDeck. Since there wasn’t an update to address the issue I decided to investigate where the hangup was occurring. It turns out the problem is easy to resolve. Security changes to Windows 8 have left TweetDeck without the ability to validate ssl certificates associated with the Twitter API. All one has to do is use Microsoft Internet Explorer to validate the certificates. Then TweetDeck will function normally again!

To work around this error follow these steps:

1) Open Microsoft Internet Explorer (You HAVE to use IE. This will not work in another browser!!!)
2) Enter the following url in the address bar and wait for the page to load: https://api.tweetdeck.com
3) Within the same internet explorer windows & tab enter the following url in the address bar ad wait for the page to load: https://api.twitter.com
4) Close Microsoft Internet Explorer
5) Open TweetDeck, enter your credentials, and log in.

That’s it! TweetDeck should connect without any issues from now on.

«A Crane Collapse In Long Island City Shave The Stache For Sandy Cash (Ended -- $200 Raised!) »

      

Leave a Reply

32 Responses to How To Resolve TweetDeck Connection Issues: “Unable to connect. Please check your network.”

  1. The fix didnt work for me, but it was to do with an anti virus update it seems as another laptop in this house was having issues connecting to the internet following an AV upgrade. My problem is fixed, and its possibly to do with this new virus out there, all the software companies are going haywire working on fixes. Anyhow, problem solved. Tweetdeck works again.

  2. I’m not sure if I have the same issue, but regardless, Tweetdeck on my desktop isn’t working. It fails to load properly and just hangs up. The problem started when I installed the update this week but that just caused it to go wonky. So I uninstalled it and reinstalled it, and now I get the blue page, notice that I have one DM and that’s about it. I tried your solution but I really don’t think I understand step 3. If I figure it out, I’ll post my resolution. I’m still at a loss as to what the update might have done.

  3. Thanks a lot man. i was confuse for the last couple of days, before i found your workaround. thank you so much *kisses*

  4. Fingers were crossed but this didn’t work for me. The tweedeck api link seemed to work ok, but the Twitter api one just shows “Sorry, that page doesn’t exist!”

    It may still just be my work network that is the issue, but I decided to hunt for fixes, and yours was the first. Sounds great, and i’m glad its work for so many others.

  5. Do you have a spam issue on this blog; I also am a blogger, and I
    was wondering your situation; many of us have created some nice practices and we are looking to trade techniques with
    other folks, please shoot me an e-mail if interested.

    my website … John

  6. Thanks a lot. I had tried everything possible and had lost my faith in using Tweetdeck with Windows 8. You have saved my life.

  7. If you don’t want to use IE, you can use an IE emulator (like IE Tab) for your Firefox or Chrome browser. Just did that and it worked fine.

  8. Wooow! I have no clue why this worked out, but it did! Didn’t work with Firefox, but on the first try with IE.
    Thank you very much :)