Title: V5.0.3 and update.php errors Last modified: August 21, 2016 --- # V5.0.3 and update.php errors * Resolved [adanguswp](https://wordpress.org/support/users/adanguswp/) * (@adanguswp) * [12 years, 1 month ago](https://wordpress.org/support/topic/v503-and-updatephp-errors/) * I have updated to v5.0.3 on two sites just now. * As a result of the upgrade process I received failure indications that a connection to WordPress.org had been lost with two or three lines in update.php being indicated as problems. I have never seen this error before. * The sites appear to be functional after the upgrade. If dropping XML-RPC was the only change, perhaps there is some trigger in that process that hits a link to WordPress.org in a call to update.php??? * Both sites run on a CentOS Linux VPS with whm/cpanel, for whatever that might be worth to know. I am on the latest versions of those after updating for Heartbleed and the Jetpack flaw. * [https://wordpress.org/plugins/wordfence/](https://wordpress.org/plugins/wordfence/) Viewing 5 replies - 1 through 5 (of 5 total) * Thread Starter [adanguswp](https://wordpress.org/support/users/adanguswp/) * (@adanguswp) * [12 years, 1 month ago](https://wordpress.org/support/topic/v503-and-updatephp-errors/#post-4801577) * Just did another one after making sure that the disable XML-RPC feature was disabled in the v.5.0.2 plugin: ——-Start error warnings———– Disabling Maintenance mode… * Warning: An unexpected error occurred. Something may be wrong with WordPress. org or this server’s configuration. If you continue to have problems, please try the support forums. (WordPress could not establish a secure connection to WordPress.org. Please contact your server administrator.) in /”path-hidden”/wp- includes/update.php on line 120 * Warning: An unexpected error occurred. Something may be wrong with WordPress. org or this server’s configuration. If you continue to have problems, please try the support forums. (WordPress could not establish a secure connection to WordPress.org. Please contact your server administrator.) in /”path-hidden”/wp- includes/update.php on line 272 * Warning: An unexpected error occurred. Something may be wrong with WordPress. org or this server’s configuration. If you continue to have problems, please try the support forums. (WordPress could not establish a secure connection to WordPress.org. Please contact your server administrator.) in /”path-hidden”/wp- includes/update.php on line 417 ———–End error warnings———– * Note that I edited out the exact path on the server above /wp-includes/ * [spark190](https://wordpress.org/support/users/spark190/) * (@spark190) * [12 years, 1 month ago](https://wordpress.org/support/topic/v503-and-updatephp-errors/#post-4801692) * Ditto!! I have the same issues… * Plugin Author [Mark Maunder](https://wordpress.org/support/users/mmaunder/) * (@mmaunder) * [12 years, 1 month ago](https://wordpress.org/support/topic/v503-and-updatephp-errors/#post-4801759) * Hi, * I don’t think it’s Wordfence causing this and we pulled the XMLRPC feature completely in version 5.0.3. This seems to be a common problem: * [https://www.google.com/search?q=An+unexpected+error+occurred.+Something+may+be+wrong+with+WordPress.org+or+this+server%E2%80%99s+configuration.+If+you+continue&oq=An+unexpected+error+occurred.+Something+may+be+wrong+with+WordPress.org+or+this+server%E2%80%99s+configuration.+If+you+continue&aqs=chrome](https://www.google.com/search?q=An+unexpected+error+occurred.+Something+may+be+wrong+with+WordPress.org+or+this+server%E2%80%99s+configuration.+If+you+continue&oq=An+unexpected+error+occurred.+Something+may+be+wrong+with+WordPress.org+or+this+server%E2%80%99s+configuration.+If+you+continue&aqs=chrome).. 69i57.231j0j7&sourceid=chrome&espv=2&es_sm=119&ie=UTF-8 * Regards, * Mark. * Thread Starter [adanguswp](https://wordpress.org/support/users/adanguswp/) * (@adanguswp) * [12 years, 1 month ago](https://wordpress.org/support/topic/v503-and-updatephp-errors/#post-4801769) * I admit that this particular error seems to have been reported on-and-off over the years. I too checked back through Google and found the threads that you just identified. Some of these seem to be associated with the introduction of WP 3.8. * However, I’m at 3.8.2 on all my sites and have been for a while. The only plugin I was updating was WF to 5.0.3. I have since updated another plugin (Google XML site maps) without any similar result. Some of the other users that noted issues before discovered that they had failed to complete the configuration of their WP site in the General settings area; e.g., no entry for a site URL. My sites have been running for years and have no missing entries. Also, no proxy is involved. I’ve never seen this particular error on any of my sites before. I’ve got about 8 active right now. * I might add that I went and tried disabling the XMLRPC option on one site before I did the update. This seemed to have no impact on the arrival of the errors listed above; that is, they still occurred. I’m going to see about deactivating WF before I do the upgrade and see if that makes any difference. I believe I’ve done three or four sites now, with four or five to go. * The good news is that I cannot discover any negative result as a consequence of the warnings. I also haven’t checked update.php to see what happens at lines 120, 272, and 417. I’ll also observe again that the warning refers to an inability to setup a secure connection to WordPress.org, and that this is post an openssl update to avoid the Heartbleed flaw. The sites that I’ve updated do not have an SSL certificate; however, one of my sites did, it had the flawed version of openssl, and I updated it per the instructions on the Internet through WHM and“ yum update” and a site reboot. Having said that, I assume that the secure connection referred to in the warning would have been an ssl socket established at the WordPress. org side. What might be a hypothetical connection here is some interaction between a reset to XMLRPC and re-establishing openssl to WordPress.org, arguably after their certs, credentials, or other link parameters have been modified. * So this may amount to nothing. It’s just that I don’t imagine that I’m the only one seeing this warning, and it might be worth some effort trying to figure out what’s behind it. * Thread Starter [adanguswp](https://wordpress.org/support/users/adanguswp/) * (@adanguswp) * [12 years, 1 month ago](https://wordpress.org/support/topic/v503-and-updatephp-errors/#post-4801770) * So, I just ran an update in the following manner. I disabled the XMLRPC option in v5.0.2. Then I deactivated the plugin. Then I did the update to v5.0.3. Finally I reactivated the plugin. I should note that I made sure that the Wordfence tables were maintained so that I didn’t lose any configuration information in this process. * Those warnings did not occur with this procedure. I should add that all my sites have more or less the same complement of plugins. Viewing 5 replies - 1 through 5 (of 5 total) The topic ‘V5.0.3 and update.php errors’ is closed to new replies. * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865) * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/) * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq) * [Support Threads](https://wordpress.org/support/plugin/wordfence/) * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/) * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/) * 5 replies * 3 participants * Last reply from: [adanguswp](https://wordpress.org/support/users/adanguswp/) * Last activity: [12 years, 1 month ago](https://wordpress.org/support/topic/v503-and-updatephp-errors/#post-4801770) * Status: resolved