Hey there,
Many thanks for reaching out – is the Jetpack plugin installed on the site? or are you getting this warning after it’s installed?
Many thanks in advance!
Hi, yes Jetpack is installed, activated and connected/configured…
Hey there,
Strange, ok – is this plugin installed also: https://ww.wp.xz.cn/plugins/full-site-editing/?
Hi Adam, I should mention that the site is running on a Multisite installation. Here is a list of active plugins:
Akismet Anti-Spam Version 5.2 by Automattic
Beehive Analytics Version 3.4.7 by WPMU DEV
Classic Editor Version 1.6.3 by WordPress Contributors
Easy FancyBox Version 1.9.5 by RavanH
Easy FancyBox - Pro extension Version 1.9 by RavanH
Jetpack Version 12.2.1 by Automattic
LiteSpeed Cache Version 5.5 by LiteSpeed Technologies
MarketPress Version 3.4.0 by WPMU DEV
MetaSlider Version 3.31.0 by MetaSlider
Module Control for Jetpack Version 1.6 by RavanH
Multisite Enhancements Version 1.6.1 by Frank Bültge
Royal Scroll to Top Version 1.0.2 by SM Mehdi Akram
WordPress.com Theme Updates Version 1.0 by Automattic
WP-dTree Version 4.4.5 by Ulf Benjaminsson
XML Sitemap & Google News Version 5.3.4 by RavanH
Plus, I’m seeing an error in Site Health, and I suspect the session_start is coming from the abandoned plugin MarketPress:
A PHP session was created by a session_start() function call. This interferes with REST API and loopback requests. The session should be closed by session_write_close() before making any HTTP requests.
Could that be causing the admin message by Pictorico?
Hey there,
Many thanks for that additional information, OK so is this appearing on other installations within that multisite? Additionally, has this been added via the network admin?
Many thanks!
Hi Adam, I’ve reproduced the issue on a test site running WordPress 6.3-alpha-55973 with Pictorico and only one plugin active: Jetpack latest.
This is a single WP install so it appears not network related, nor a conflict with other plugins… I can send you a temporary admin access if you like.
Hey there,
Many thanks for that.
I’m wondering if this may not be a theme issue, but a Jetpack issue.
What is the URL of the site? I wouldn’t need admin access at this stage.
Many thanks!
Hey there,
Many thanks!
Interestingly, it doesn’t look like Jetpack is connected: https://jptools.wordpress.com/debug/?url=dev.status301.com
It looks like this is a dev site – is there anything on the environment that would restrict access or a connection via Jetpack?
Many thanks.
Hi, no there should not be anything that restricts the jetpack connection. From the admin, I get a “Your Jetpack setup looks a-okay!” on the Jetpack Debug page and Site Health does not warn about connection problems either…
It is indeed a test site. The site where I first noticed the issue, is https://artfairgalerie.com/ which shows “Oops! Jetpack Blog not found.” on https://jptools.wordpress.com/debug/?url=artfairgalerie.com but on the admin side, in JP Debug or Site Health all appears to be working well.
Strange.
UPDATE: I tried de/reconnecting Jetpack but that did not change anything…
UPDATE 2: in fact, any one of my sites that I select in the “Select a blog” dropdown is now responding with an “Oops! Blog not found.” Something wrong with my account at wp.com?
Hey there,
Thanks for that additional information and triaging there!
UPDATE 2: in fact, any one of my sites that I select in the “Select a blog” dropdown is now responding with an “Oops! Blog not found.” Something wrong with my account at wp.com?
I wouldn’t say there’s an issue with the account, but it would be the connections via Jetpack that would be an issue.
I’d certainly recommend reaching out here: https://jetpackme.wordpress.com/contact-support/
Something like this, is likely to occur when changing domains, or migrating sites from location to another, so it’s worth looking into – to make sure everything is as it should be.
Very strange. The connection on the dev site is a completely fresh one, and de-/reconnecting on the live site does not change anything.
Anyway, thanks for your time and attention so far. Maybe someone else will run into this issue and be able to find out more…
