Title: Twitter API now requires HTTPS
Last modified: August 21, 2016

---

# Twitter API now requires HTTPS

 *  ResolvedPlugin Author [Joe Dolson](https://wordpress.org/support/users/joedolson/)
 * (@joedolson)
 * [12 years, 5 months ago](https://wordpress.org/support/topic/twitter-api-now-requires-https/)
 * Hello!
 * To head off what will undoubtedly be some support requests, I wanted to let you
   know about a change in the Twitter API as of January 14th, 2014.
 * The Twitter API used to accept either HTTP or HTTPS connections for posting status
   updates and other interactions. Because some servers are not configured correctly
   to handle making HTTP queries, I’ve included a toggle so that you could switch
   WP to Twitter to make queries on HTTP instead of HTTPS.
 * As of January 14th, 2014, Twitter has shut off HTTP access to their API. 403 
   errors will now be returned when an HTTP query is made, and your status update
   will be rejected.
 * If you have been dependent on HTTP support, you’ll need to talk to your hosting
   company about fixing the problem. I’m afraid that there’s nothing I can do.
 * [https://dev.twitter.com/discussions/24239](https://dev.twitter.com/discussions/24239)
 * [http://wordpress.org/plugins/wp-to-twitter/](http://wordpress.org/plugins/wp-to-twitter/)

Viewing 15 replies - 1 through 15 (of 16 total)

1 [2](https://wordpress.org/support/topic/twitter-api-now-requires-https/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/twitter-api-now-requires-https/page/2/?output_format=md)

 *  [mundomariah](https://wordpress.org/support/users/mundomariah/)
 * (@mundomariah)
 * [12 years, 5 months ago](https://wordpress.org/support/topic/twitter-api-now-requires-https/#post-4504320)
 * Thanks. I had http and it seems my server supports https too.
 *  [Jai_wordpress](https://wordpress.org/support/users/jai_wordpress/)
 * (@jai_wordpress)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/twitter-api-now-requires-https/#post-4504398)
 * Hi
 * I have been using the WP-To-Twitter plugin in my Word Press blog for almost a
   year, and now it has stopped working. As the twitter is not supporting http anymore
   I just want to know what options do I have. Do I need to install SSL certificate
   on my server in order to get it working again ?
 * Your help is much appreciated.
 * Many Thanks
 *  Plugin Author [Joe Dolson](https://wordpress.org/support/users/joedolson/)
 * (@joedolson)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/twitter-api-now-requires-https/#post-4504400)
 * No, you don’t need an SSL certificate, but your server needs to be able to communicate
   over the HTTPS protocol. If you don’t know how to change that, you’ll need to
   communicate with your host.
 *  [Jai_wordpress](https://wordpress.org/support/users/jai_wordpress/)
 * (@jai_wordpress)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/twitter-api-now-requires-https/#post-4504401)
 * we are hosting the website on our own web server and the word press is under 
   our main web site. for example: [http://www.website.com/wordpress](http://www.website.com/wordpress).
 * So do I need to ask our System Administrator to allow our web server to communicate
   over https protocol? is it just making some changes in the Firewall?
 *  Plugin Author [Joe Dolson](https://wordpress.org/support/users/joedolson/)
 * (@joedolson)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/twitter-api-now-requires-https/#post-4504402)
 * I can’t really answer that question without knowing more about your server. Turn
   on OAuth debugging in WP to Twitter, get the full data from your attempt to communicate
   with Twitter, then talk to your system administrator. They should be able to 
   solve the issue.
 * It varies – it can be a problem with certificate verification, with open ports,
   firewalls, etc.
 *  [timjal](https://wordpress.org/support/users/timjal/)
 * (@timjal)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/twitter-api-now-requires-https/#post-4504429)
 * At the risk of asking a silly question, where is the toggle you added?
 * I cannot see it in my WP to Twitter settings anywhere and have had the error 
   for a long time now.
 * Please help!
 *  Plugin Author [Joe Dolson](https://wordpress.org/support/users/joedolson/)
 * (@joedolson)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/twitter-api-now-requires-https/#post-4504430)
 * I’ve removed it. It used to be part of the plugin, but in 2.8.1 I removed it,
   since it no longer served any purpose.
 * If you’re having a related issue,please start a new support thread.
 *  [timjal](https://wordpress.org/support/users/timjal/)
 * (@timjal)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/twitter-api-now-requires-https/#post-4504431)
 * I tried to contact you directly through the plugin support though my blog. Hopefully,
   that came through to you.
 * If not, when I’m next home, I’ll post the issues here too.
 *  Plugin Author [Joe Dolson](https://wordpress.org/support/users/joedolson/)
 * (@joedolson)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/twitter-api-now-requires-https/#post-4504432)
 * I don’t see it, but I don’t know what name, email, or site I should be looking
   for, so it’s hard to say. I respond to every email support message I get, but
   there are many reasons for them to sometimes not get to me.
 *  [timjal](https://wordpress.org/support/users/timjal/)
 * (@timjal)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/twitter-api-now-requires-https/#post-4504433)
 * I will check when I’m home.
 * If it helps, my name is Tim and the blog is about art nudes. It was sent yesterday.
 *  Plugin Author [Joe Dolson](https://wordpress.org/support/users/joedolson/)
 * (@joedolson)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/twitter-api-now-requires-https/#post-4504434)
 * I don’t see that request, and it’s not in my spam filters, either. Can’t say 
   why; but it didn’t get to me, for whatever reason.
 *  [jclandin](https://wordpress.org/support/users/jclandin/)
 * (@jclandin)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/twitter-api-now-requires-https/#post-4504435)
 * Hi Joe,
 * I’m another affected for the “Error 403:…” while trying to send tweets. The weird
   thing is that everything worked fine until Feb 7st (four days ago) when those
   errors started. I thought that if WP-to-twitter worked since Jan 14th my server
   was able to use https.
 * “Check support” succesfully contacts goo.gl shortening service and fails to submit
   an update to twitter. My server time and Twitter time difference is only six 
   seconds. Editing a post and clicking “Tweet this” works fine.
 * Before opening a support thread I wanted to see the OAuth connection debugging
   data… but I can’t find it although “Get Debugging Data for OAuth Connection” 
   is checked. Where is that information? Any idea about where to look why tweets
   aren’t being automatically published?
 * Thanks,
    Juan Carlos
 *  Plugin Author [Joe Dolson](https://wordpress.org/support/users/joedolson/)
 * (@joedolson)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/twitter-api-now-requires-https/#post-4504436)
 * Please, Please, Please: Start your own support threads. It is not at all helpful
   to me to try and manage multiple support requests in the same thread. You may
   believe that you’re experiencing the same issue, but it’s actually quite unlikely
   that you are.
 * Please post a new support thread.
 *  Plugin Author [Joe Dolson](https://wordpress.org/support/users/joedolson/)
 * (@joedolson)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/twitter-api-now-requires-https/#post-4504437)
 * FYI, you can only see the OAuth debugging data when you make a connection to 
   OAuth, because it’s a data exchange that only happens in that circumstance. Disconnect
   from Twitter and reconnect to see those interactions.
 *  [jclandin](https://wordpress.org/support/users/jclandin/)
 * (@jclandin)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/twitter-api-now-requires-https/#post-4504438)
 * Ok. Sorry…

Viewing 15 replies - 1 through 15 (of 16 total)

1 [2](https://wordpress.org/support/topic/twitter-api-now-requires-https/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/twitter-api-now-requires-https/page/2/?output_format=md)

The topic ‘Twitter API now requires HTTPS’ is closed to new replies.

 * ![](https://ps.w.org/wp-to-twitter/assets/icon-256x256.png?rev=2997308)
 * [XPoster - Share to Bluesky and Mastodon](https://wordpress.org/plugins/wp-to-twitter/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-to-twitter/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-to-twitter/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-to-twitter/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-to-twitter/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-to-twitter/reviews/)

 * 16 replies
 * 5 participants
 * Last reply from: [timjal](https://wordpress.org/support/users/timjal/)
 * Last activity: [12 years, 4 months ago](https://wordpress.org/support/topic/twitter-api-now-requires-https/page/2/#post-4504439)
 * Status: resolved