Site can’t be reached
-
I seem to have an issue with JetPack. It disappeared from one of my sites but when I try to re-download it I’m told the files already exist. It shutdown another site until my host was able to disable all plugins so I could gain access once again.
So two part question: how do I understand what’s going on with JetPack and how do I re-establish a connection with WordPress for the site ‘that cannot be reached’?The blog I need help with is: (visible only to logged in users)
-
-
Hi and thanks for the response.
My sites are ChildrensMinistryLeader.com and GregJBaird.com. CML was the one that was showing it couldn’t be accessed, but now both of them are saying they can’t be accessed in WordPress.com.
I’m a novice so I really have no idea what I’m doing here. Thanks for any help.
-
I also am repeatedly getting messages when I try to update plugins, like this one I just got after being told Yoast couldn’t be updated and then tried to activate it:
Warning: require_once(/home/content/a2pnexwpnas01_data01/21/3521821/html/wp-content/plugins/wordpress-seo/wp-seo-main.php): failed to open stream: No such file or directory in /home/content/a2pnexwpnas01_data01/21/3521821/html/wp-content/plugins/wordpress-seo/wp-seo.php on line 48
Fatal error: require_once(): Failed opening required ‘/home/content/a2pnexwpnas01_data01/21/3521821/html/wp-content/plugins/wordpress-seo/wp-seo-main.php’ (include_path=’.:/opt/remi/php72/root/usr/share/pear:/opt/remi/php72/root/usr/share/php:/usr/share/pear:/usr/share/php’) in /home/content/a2pnexwpnas01_data01/21/3521821/html/wp-content/plugins/wordpress-seo/wp-seo.php on line 48
-
Hm yes ok. Those are self-hosted WordPress.org site, which we really can’t help with here.
To clear up any confusion, WordPress.com and WordPress.org are two different entities: http://support.wordpress.com/com-vs-org/
WordPress.org has complete documentation for self-hosted/installed versions of WordPress.org at https://wordpress.org/support/ and support at https://wordpress.org/support/forums/
For that plugin error, I recommend reaching out at https://wordpress.org/support/plugin/wordpress-seo/
As for Jetpack, I don’t see anything that would outright block it, so I recommend contacting them at https://jetpack.com/contact-support/?rel=support
-
Thanks for the explanation. So is there any reason for my sites to be in WordPress.com as they are? Is there any purpose for me to access this?
-
To add the sites as they are to WordPress.com, you’d need the Jetpack plugin to be connected to your WordPress.com account.
If you’re talking about completely moving the sites to WordPress.com, following this guide https://en.support.wordpress.com/moving-from-self-hosted-wordpress-to-wordpress-com/ but please be aware of the differences: https://en.support.wordpress.com/com-vs-org/
-
I’m having the same problem with gsbands.org — all was well until I updated Jetpack today. Now I am getting an error on WordPress.com saying that the site cannot be accessed, and I am getting an error when I try to log in to the WordPress control panel on my actual website. Any help would be appreciated!
-
Please don’t post into other people’s threads.
As this is a Jetpack issue, please contact Jetpack support directly at https://jetpack.com/contact-support/?rel=support, or you can post in the Jetpack forums at https://wordpress.org/support/plugin/jetpack/
- The topic ‘Site can’t be reached’ is closed to new replies.