WP HTTP Error: SSL: certificate subject name '*.wordpress.com' does not match target host
-
I am attempting to pull in a feed from a WordPress.com hosted site into a privately hosted WordPress instance. Using the ‘fetch_feed’ WordPress function results in a WP_Error object containing the following error message:
WP HTTP Error: SSL: certificate subject name ‘*.wordpress.com’ does not match target host name [CUSTOMURL]
The WordPress.com site is using a custom URL (not a 3rd level *.wordpress.com address) managed through the WordPress interface. When viewing the feed URL in Chrome on my local machine, I can see that the certificate is marked as valid. Furthermore, I can see the custom URL listed under the Subject Alternative Name section of the cert.
I’ve attempted to curl the feed via PHP on the private server, and I received a very similar error message:
[error code 51] SSL: certificate subject name ‘*.wordpress.com’ does not match target host name [CUSTOMURL]
Running the same script on my local machine succeed in returning the feed’s content.
I suspect that the issue resides somewhere on my private server and not in the WordPress.com certificate, but I’m open to any and all suggestions.
Thanks!
The blog I need help with is: (visible only to logged in users)
-
I will type modlook into the sidebar tags on this thread for Staff help. How do I get a Moderator/Staff reply for my question? https://en.support.wordpress.com/getting-help-in-the-forums/#how-do-i-get-a-moderatorstaff-reply-for-my-question Please subscribe to this thread so you are notified when they respond and be patient while waiting. To subscribe look in the sidebar of this thread, find the subscribe to topics link and click it.
-
I can’t think of anything on our end that would be causing this. All we can do is provide a valid feed.
If you can provide me the site URL, I will run the feed through a validator, but I am 99.98% sure that it will return the same “valid” result as every other WordPress.com feed.
-
The feed can be found here: https://uwheli.com/feed/
One suggestion that I’ve seen is that the issue is being caused by the images referenced inside the theme. All of the files are being served from “https://heliuw.files.wordpress.com/*”. This would seem to explain the error message containing the ‘*.wordpress.com’ string.
-
Hi there!
What’s happening here is that your server does not seem to support SNI (Server Name Indication), which is required to access custom domains on WordPress.com using HTTPS. Without SNI, only our main *.wordpress.com certificate can be served for your request, which is not valid for your custom domain.
This is likely caused by an outdated version of cURL and/or OpenSSL on your server. We recommend you update (or ask your hosting provider to update) both cURL and OpenSSL to their latest versions.
If this does not fix the error please reply with the version of cURL and OpenSSL you are using.
-
While I have yet to officially confirm that this was the case, I do believe that you are correct. Checking the versions of OpenSSL (0.9.8b) and cURL (7.15.5) on the server against the list of software versions that support SNI (https://en.wikipedia.org/wiki/Server_Name_Indication), they are both just behind the versions that add SNI support; 0.9.8f and 7.18.1 respectively.
Thanks for your help on this one! I’ll post a follow-up within the next day or so with my findings either way.
- The topic ‘WP HTTP Error: SSL: certificate subject name '*.wordpress.com' does not match target host’ is closed to new replies.
WordPress.com Forums 