rcharbonxx

@erania-pinnera
No, I meant what should I see with the “?for=jetpack” appended?

Please tell me what I

should

see, don’t just provide a link.

@erania-pinnera
I asked a simple question (What response should I get when I click on the amended link?). An answer, other than the boilerplate copied to everyone in this situation, would be appreciated.

@wpkaren:
What response should I get when I click on the amended link?

Shouldn’t the Troubleshooting FAQ be amended with the new info?

Thanks,
Ray

@erania-pinnera I have: https://www.ads-software.com/support/topic/jetpack-connection-error-5/
Still hoping for a response.

More info:
Jetpack, for the most part seems to be fine. I found the issue when I was putting up a new post. When I tried to publish I got an alert saying I needed to reconnect to LinkedIn, and when I clicked on the alert to try to reconnect, all I got was a blank screen. So I went to WP.com and saw “The site cannot be accessed”.

replying so I can turn notifications on.

I have the same 409 error in Jetback debug with the site https://www.gemsofwisdomconsulting.com/
That site is already using HTTPS and Really Simple SSL. I’ve already disconnected and reconnected Jetpack and that went well, but WordPress.com says the site cannot be accessed.
Site Health says the Wpcom test fails and recommends reconnecting, but as noted, that doesn’t help even though reconnection seems successful.
https://www.gemsofwisdomconsulting.com/web/xmlrpc.php responds just fine.

Thanks @nickpapag ! If you don’t mind my asking, why did you happen to have this around? (And do you have access to others, so I can slowly/safely upgrade to the current version?)

Fixed it. Needed to resave wp-config.php as UTF-8 (without BOM).

Please read the entire post before replying. “Disabling all plugins doesn’t help.”

• This reply was modified 5 years, 4 months ago by rcharbonxx.

FYI: I needed to flick some options off, then on again to get them working again.

I upgraded to the latest version of the theme and WP5 a couple days ago. the upgrades ruined the headers on my site. Support from Customizr has been useless so far. Sigh.

Disabling “Include sitemap in HTML format” resolved the problem.

BTW, the HTML version wasn’t validating properly anyhow.

I disabled “Include sitemap in HTML format” on the problem site. We’ll see what happens…