Title: WordPress could not be reached – (https site) Last modified: July 3, 2017 --- # WordPress could not be reached – (https site) * Resolved [jmgarciabonilla](https://wordpress.org/support/users/jmgarciabonilla/) * (@jmgarciabonilla) * [8 years, 11 months ago](https://wordpress.org/support/topic/wordpress-could-not-be-reached-https-site/) * Hi Steve, * I am a new user of airstory (wanted it mainly because the WP integration). I installed the plugin and connected the account with the token as [detailed here](http://help.airstory.co/importing-converting-and-exporting-content/how-can-i-export-my-airstory-document-to-wordpress). * The [connection seemed to work](https://screencast.com/t/B2Mukz9bm), and [WordPress did not complain](https://screencast.com/t/aWZtO5p7vZer). However, when I try pushing an Airstory document (previously imported from Google Docs) into Airstory my WordPress install (mejorcamara.com), something goes wrong and I end up with a message saying “WordPress could not be reached”. * Any information I can five you to better understand the issue? * Thanks a lot in advanced, Josep Viewing 6 replies - 1 through 6 (of 6 total) * Thread Starter [jmgarciabonilla](https://wordpress.org/support/users/jmgarciabonilla/) * (@jmgarciabonilla) * [8 years, 11 months ago](https://wordpress.org/support/topic/wordpress-could-not-be-reached-https-site/#post-9285072) * Edit: * I have another WordPress install under the same server and it did work (although all Spanish characters (ñ, ´, etc.) were not properly added. * See here the configuration for this one: [https://screencast.com/t/UgtOL7tqGb8q](https://screencast.com/t/UgtOL7tqGb8q) * thx * Plugin Contributor [Steve Grunwell](https://wordpress.org/support/users/stevegrunwell/) * (@stevegrunwell) * [8 years, 11 months ago](https://wordpress.org/support/topic/wordpress-could-not-be-reached-https-site/#post-9290909) * Hi [@jmgarciabonilla](https://wordpress.org/support/users/jmgarciabonilla/), thank you for reporting these issues! * I poked around a bit, and at the very least [I stumbled upon a bug within the error handling](https://github.com/liquidweb/airstory-wp/issues/58), which will be addressed in the next release (likely due this week). While it might not tell us exactly why mejorcamara.com is having trouble communicating with Airstory, it should at least get us a little closer. * On the Tools > Airstory page, there’s a full system report (just below the table you provided a screenshot of) that can help identify anything in the server configuration that may be causing problems; could you please either post the contents of that here or email it to sgrunwell (AT) liquidweb (DOT) com? * With regards to the second server where the export is working but all of the Spanish characters are being corrupted, can you verify that you’re running the latest version (1.1.2, at the time of this writing) of the Airstory plugin? Version 1.1.1 should have tackled this issue, but if you’re still seeing issues I want to make sure we’re able to resolve that promptly. Again, the system report from that site would be helpful, as well as the HTML export from Airstory (so I can test against real content) — as before, you’re welcome to email me directly if you don’t want that information in this public thread. * Thread Starter [jmgarciabonilla](https://wordpress.org/support/users/jmgarciabonilla/) * (@jmgarciabonilla) * [8 years, 11 months ago](https://wordpress.org/support/topic/wordpress-could-not-be-reached-https-site/#post-9292161) * Hi Steve, * Once again, thanks for taking care of all these. * I’ve updated the plugin for mejorcamara.com from 1.1.2 to 1.1.3 (as advised by Airstory support). But it still gives me the same error. * For the other installation (in the same server groundedyogabcn.com), yes, I was using the 1.1.2 version of the plugin and here the report: * ​After I uploaded to the 1.1.3 version of the plugin the connection still works but the Spanish characters still don’t seem to be properly integrated. Here a screenshot of the (updated) plugin. And below the complete report: (I sent you an email with it) * *​*Could the error in the characters be because I am trying to push Spanish characters to a en_US​ ​installation?​*​*​ ​ ​Btw I noticed that for both of the users I connected a Airstory token with​ my old WP passwords did not work and I had to reset them. Is this due to the plugin? * Thanks a lot for your time and help! * **You have reports and more screenshots in the email I sent you.** * Plugin Contributor [Steve Grunwell](https://wordpress.org/support/users/stevegrunwell/) * (@stevegrunwell) * [8 years, 10 months ago](https://wordpress.org/support/topic/wordpress-could-not-be-reached-https-site/#post-9305612) * Hi Josep, * I just sent a response to your email, but wanted to make sure I also thanked you publicly for the details! * [We’re working on preparing version 1.1.4 of the plugin](https://github.com/liquidweb/airstory-wp/milestone/6), due early this week, which should resolve some of the encoding issues that you’ve experienced. We couldn’t fix these bugs without knowing about them first, so thank you so much for reporting them, giving us the details necessary to address them, and your patience! * Thread Starter [jmgarciabonilla](https://wordpress.org/support/users/jmgarciabonilla/) * (@jmgarciabonilla) * [8 years, 10 months ago](https://wordpress.org/support/topic/wordpress-could-not-be-reached-https-site/#post-9306018) * Hey Steve, * Thanks a lot for all your time, effort and good explanations. You are a hard working man. * As soon as I try the new version I’ll let you know how it went. * Cheers, Josep * Plugin Contributor [Steve Grunwell](https://wordpress.org/support/users/stevegrunwell/) * (@stevegrunwell) * [8 years, 10 months ago](https://wordpress.org/support/topic/wordpress-could-not-be-reached-https-site/#post-9308724) * Josep, * I just sent you an email, but wanted to follow up here as well to let you know that version 1.1.4 of the Airstory plugin was just released and should be visible within your WordPress installations’ update screens shortly (if it isn’t already). * Thanks again for your patience and help tracking down the root cause of these issues! Viewing 6 replies - 1 through 6 (of 6 total) The topic ‘WordPress could not be reached – (https site)’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/airstory.svg) * [Airstory](https://wordpress.org/plugins/airstory/) * [Frequently Asked Questions](https://wordpress.org/plugins/airstory/#faq) * [Support Threads](https://wordpress.org/support/plugin/airstory/) * [Active Topics](https://wordpress.org/support/plugin/airstory/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/airstory/unresolved/) * [Reviews](https://wordpress.org/support/plugin/airstory/reviews/) * 6 replies * 2 participants * Last reply from: [Steve Grunwell](https://wordpress.org/support/users/stevegrunwell/) * Last activity: [8 years, 10 months ago](https://wordpress.org/support/topic/wordpress-could-not-be-reached-https-site/#post-9308724) * Status: resolved