Error executing wp_remote_post: Connection timed out

Please post your Diagnostic Test result.

OS: Linux cloud.klenhost.com 2.6.32-531.29.2.lve1.3.11.1.el6.x86_64 #1 SMP Thu Dec 18 06:49:17 EST 2014 x86_64
HTTP User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.61 Safari/537.36
Platform: PHP Linux 5.4.40 / WordPress 4.2.2 en_US
PHP Dependencies: iconv=Yes, spl_autoload=Yes, openssl=Yes, sockets=Yes, allow_url_fopen=Yes, mcrypt=Yes
WordPress Plugins: Disable Comments, Duplicator, Email Log, Exclude Pages from Navigation, Gravity Forms, New RoyalSlider, Postman SMTP, Quick Page/Post Redirect Plugin, Really Simple CAPTCHA, Regenerate Thumbnails, Search & Replace, Shadowbox JS, Slickr Flickr, Wordfence Security, WordPress SEO, WP-PageNavi, WP Super Cache
WordPress Theme: Portopia
Postman Version: 1.6.22
Postman Sender Domain: gmail.com
Postman Transport URI|Force Email|Name: smtp:tls:oauth2://smtp.gmail.com:587|No|No
Postman Transport Status (Configured|Ready|Connected): Yes|No|Yes
Postman Deliveries (Success|Fail): 121|8
Postman Bind (Success|Fail|Path): No|No|/home/gofun/public_html/wp-includes/pluggable.php
Postman TCP Timeout (Connection|Read): 60|60
Postman Email Log (Enabled|Limit|Transcript Size): Yes|10|128
Postman Run Mode: production
Postman PHP LogLevel: 40000
Postman Stealth Mode: No
Postman File Locking (Enabled|Temp Dir): Yes | /tmp

Postman is not currently in charge of your email. If you go to the settings page you will probably see a giant error message that you have not granted OAuth permission. Resolve the error by completing the authorization.

The timeout is actually being generated by the default WordPress mailer.

Jason-

From my initial post:
“I tried re-verifying one of them through the developer interface, and it also timed out” – that’s referring to trying to grant OAuth permission. It times out when attempting to do that, so it’s not possible to complete authorization.

I see. It wasn’t clear that your timeout was in the grant. That’s a different problem.

This means that you are being prevented from connecting to https://www.googleapis.com on port 443 by a firewall which is dropping (as opposed to rejecting) packets. Are you sure the connectivity test says that it can connect to Googleapis.com??

There are a few people that have had this happen before. The only solution is to open the firewall, or switch to password authentication.

Jason-

It was initially on trying to send, and then upon trying to re-authenticate. Just ran connectivity test, and you’re correct, it looks like it can’t connect on port 443. Must have been a change in the hosting configuration, I’ve reached out to them for assistance.

Thanks for the help!