id summary reporter owner description type status priority milestone component version severity resolution keywords cc focuses 27722 Don't fire a warning when the WP API timeouts — or do so properly. Denis-de-Bernardy johnbillion "At the time of writing, I'm systematically getting the following error from within the WP admin area's update core section: {{{ An unexpected error occurred. Something may be wrong with WordPress.org or this server's configuration. }}} Two things bother me: 1. It only fires when SSL is used. 2. The raw_response content suggests a connection timeout. I think the warning itself is of dubious merit. If we decide to keep it, it should be more explicit as to what is going on. And it should always fire, regardless of whether SSL is getting used or not… A possible exception I'd make is when it's a request timeout — in that case WP should silently try again a few minutes later — without a warning or notice." defect (bug) closed normal Upgrade/Install 3.7.1 normal maybelater needs-patch