Hi there, @ssstil,
Thanks for reporting this, and for working out a solution by using previous information shared in the forum 🙂
We’d like to know more about how you fixed it, and if the system is returning you any clues that can lead you to think that it’s not a safe solution. The forum thread you mentioned is from two years ago, and we want to be sure you’re all set.
Could you please post your site URL here so that we can have a look, and share more info if you have any? If you want it to remain private, you can also contact us via contact form. If you choose to reach out directly, please include a link to this thread.
Thanks!
Thread Starter
ssstil
(@ssstil)
Dear Mr. Stef,
I did not solve the problem. I wanted to know, if the plug in creators have tested the option of removing that setting in the “hardening” option and if it is safe to use, since I am no technician.
Due to privacy reasons, I can’t publish the site.
If necessary, I will use the contact form to send the URL, but it seems to be a general issue, not just one-person related.
Regards,
ssstil
Hey there, @ssstil,
I agree with you: it looks more like a general issue that could affect sites broadly rather than being specific to just one.
Having a fresh example with your site, along with details of your attempts to address it (step by step actions, how you followed the forum instructions, etc.), will help us reproduce the problem and assess what’s safe. From there, we can determine if it needs to be escalated to our tech team 🙂
I hope that makes sense! We’ll look forward to your email. Totally understand not wanting to share your site URL publicly 👍
Thread Starter
ssstil
(@ssstil)
Dear Mr. Stef,
I did not follow any instruactions, since you did not provided any, in order to test it on my own. Which is why I posted this topic.
Has the company/owner made any attempts to solve the issue and if so, what are the solutions? I am not going to remove anything from “hardening” sections, since I am no technician and I don’t even know what it means.
Has the plugin owner made any attempts to test this input?
Are there any solutions to the situation?
Because so far I am being ask to provide the URL of the site, but no solutions.
Regards,
ssstil
Hi @ssstil,
Thanks for clarifying, that helps a lot. I apologise if my previous communications have been a bit confusing, let me start back 🙂
The issue of XML-RPC being disabled is a common cause of Jetpack “Site Health” misreports, as seen in the thread you linked.
While we can’t diagnose anything without the site URL, here’s what generally helps and what we’d like to confirm, either publicly or privately:
- Return Jetpack functionality: if you disable XML-RPC in security plugins or server settings, Jetpack may appear connected but still malfunction. Ensuring XML-RPC is accessible typically resolves the error.
- Test in context: if there’s any chance to test on a temporary environment with hardening settings disabled, that may help isolate the root cause (we can give you instructions on how to create it).
- Share and secure: if you’re able to share your site privately via the contact form, as mentioned, without posting it here, that would let us examine and advise precisely. Understanding what you’ve already tried and whether the hardening setting is a toggle (unchecked) or removal will help us give targeted guidance.
Hope that’s all a bit more clear now 🙂 Let me know how you’d like to proceed, and if you have any questions about that.
Hey @ssstil,
Do you have updates about that, do you still need help? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!
Thread Starter
ssstil
(@ssstil)
Somehow the problem doesn’t appear anylonger. I can use really simple ssl with jetpack
Howdy @ssstil, thank you for sharing that information with us. If you do ever want to reach out to us to share any details or what you may have changed to ensure everything is working on your end, please do so here: Contact Form
For now, I’ll go ahead and mark this topic as solved.
