Hi Vishal,
Apologies for the delay in following up with you on this. We’re working through a bit of a backlog.
Thanks for letting us know what troubleshooting you’ve tried. I’m curious about what you’re saying here:
etpack plugin is in safe mode on the dev and test environment.
Jetpack has to be actively connected to a publicly accessible website in order for you to be able to connect to our Publicize service. Do you mean that you’ve intentionally kept Jetpack disconnected from WordPress.com? If so, please reconnect Jetpack. Once you do that, you should be able to connect your social media accounts to Publicize.
Alternatively, are you saying that you’ve tried to reconnect Jetpack, but can’t? On our end, I’m not seeing any blocks or anything specific that would indicate why we can’t connect. So, please try deleting Jetpack entirely and reinstall it, then try reconnecting.
Let us know how it goes!
Hello Team,
My hosting provider pantheon had suggested to me that if the Jetpack is installed on the Dev and Test servers, then put it in Safe Mode. Only live website STAGING_MODE is not enabled. Reference: https://jetpack.com/support/staging-sites/
I tried uninstalling the Jetpack plugin and again reinstalling it and configure my account. but still, I got the same error that I was getting earlier. Here is the screenshot: https://tinyurl.com/ydpx3grw
Hi there, @vishal13m,
Thanks for the follow-up – I’m sorry you still haven’t figured this issue out.
I did some more testing on your site, and it looks like there’s still something preventing a working connection between Jetpack and your site.
Can you reach out to your host and ask them if they have any blocks or limits on your XML-RPC.php file? While the page displays okay, I can see a parse error at my end, which can be fixed by your host.
It’s also worth checking whether any Jetpack IP addresses are blocked. The full IP range can be found at the bottom of this page:
https://jetpack.com/support/hosting-faq/
Let me know what you find out and we’ll take it from there.
Thanks for sorting this out with me!
Hello Team,
Can you send me out what error is causing at your end?
Hi @vishal13m,
Have you tried updating the pantheon.yml file and having some values for the protected_web_paths eg:
protected_web_paths_override: true
protected_web_paths:
- /private
- /wp-content/uploads/private
Then it should be pushed from the dev environment up to live
We have this proposed in the Pantheon docs already https://github.com/pantheon-systems/documentation/pull/6184#issuecomment-801541965 so would like to confirm if this works from your end
Thanks!
Hi @carl-alberto,
Yes, I updated the “protected_web_paths value” in the pantheon.yml file and pushed dev to the live environment. But still, the same error is occurring.
Can you please tell me, why this is happening? I got some error notification in WordPress account. See the screenshot.
1) https://tinyurl.com/yhhehsda
2) https://tinyurl.com/yds25oby
This is my demo website on another server. See this screenshot 1) https://tinyurl.com/yzzs7d6q. The error I am showing in the screenshot above is not happening on this domain. I don’t know what actual issue is occurring.
@erania-pinnera
Can you send me out what error are you talking about?
Thanks!
Hey @vishal13m,
Can you send me out what error are you talking about?
Sure thing. When testing the Jetpack connection for your site blog.protiviti.com, I got a “List of available methods do not include jetpack.getUser” error.
I then cURL-A the xmlrpc.php file and I got the following response:
-32700
faultString
parse error. not well formed
This suggests there’s something on the server’s that’s off.
I also checked the connection for bpro.jiffystacks.com, and everything looks great for this site. That confirms my suspects about the connection block happening at your servers for blog.protiviti.com
I hope this helps figure things out with your host! Let me know what you find out.
Hey @erania-pinnera,
Thank you for looking into this. I gave it in pantheon support. Let’s see what we get.
Brilliant! We’ll keep the thread open then, we look forward to your reply 🙂
@erania-pinnera
Thanks for your help in solving this problem.
@vishal13m no problem at all!
We look forward to your updates 🙂
