• Resolved NeilJordan

    (@neiljordan)


    I have tried to use this to share to FB and Twitter but it doesn’t seem to work. I think the og codes are there. I do also use Yoast, but the OG data option was enabled – I have disabled it in testing and that is how it is at the moment.

    I am using other plug ins for LinkedIn and Google which appear to work without issues.

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • @neiljordan Our logs are showing Jetpack Social Facebook sharing was skipped for your latest post.

    Did you disable Facebook sharing when creating the post? Did you create a brand new post from scratch, or was it created by duplicating, copying, or editing an existing post?

    It also looks like Jetpack is having trouble accessing the site’s XML-RPC file, which is preventing it from connecting to the site. Jetpack needs to be connected in order for Jetpack Social to work.

    I’d  suggest  checking if  you  have  any  security  plugins  activated that  might  be  blocking  our requests.  If  not,  try  contacting  your  hosting  provider  and  asking  them  to  check  their  security  logs  to  see  if  they  are  blocking  or  otherwise  limiting  incoming  and  outgoing  connections  over  XML-RPC. 

    Jetpack  uses  this  file  to  communicate  with  your  site,  but  some  hosts  block  connection  requests  to  that  file.

    Our  requests  look  like  the  following:

    •  File:   SITEURL/xmlrpc.php 
    • User-agent header:  Jetpack  by  WordPress.com
    • IPs:  https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/

    Please  ask  them  to  allowlist  the  IP  addresses  listed  above.  Note  that  these  IP  addresses  could  change  (or  more  could  be  added)  at  any  time,  which  could  break  your  connection  to  Jetpack.  For  this  reason,  we  actually  discourage  allowing  specific  IPs,  although  with  some  hosts  it  may  be  the  only  option.

    Let  us  know  how  that  goes.

    Thread Starter NeilJordan

    (@neiljordan)

    Hi. We have Wordfence installed but I am not sure if that would block it nor aware of any settings that I could disable/change.

    Our ISP have added the IP addresses, but the post that went live yesterday also has not been posted through to FB etc. These are posts that are created in draft and scheduled by another plug-in. Their sharing works fine to LinkedIn/Google with other plug ins.

    Hi @neiljordan ,

    It’s frustrating, because your Jetpack connection is still showing an issue with accessing your XMLRPC file. Normally, whitelisting the IPs, as JS suggested, resolves this.

    The error we see is this:

    cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received

    This particular error can means that the xmlrpc.php file or this site itself is taking too long to load, causing Jetpack to give up after 5-10 seconds.

    It can also mean that your host is still limiting access to the file. This might be outright (all requests blocked) or based on some sort of rule (specific types of requests) or rate limiting (too many requests triggers blocking).

    So all that said, since you’re using WordFence, the first thing I’d check is that you have the Disable XML-RPC authentication checkbox enabled in Wordfence > Login Security > Settings, and any manual .htaccess blocking to XML-RPC has been disabled.

    Let us know how that goes!

    Best,

    Cena

    Thread Starter NeilJordan

    (@neiljordan)

    I am not quite sure I follow – you seem to suggest ticking the Disable XML-RPC authentication checkbox in Wordfence, which seems counter intuitive, but when I do that, I get an error from Jetpack itself?

    Jetpack is just one of those horrific plugins that is either going to work well or going to cause a gigantic pain in the a#$%!! And it just keeps getting more and more expensive with a horrifying number of upgrades and features that put more stress and non-tech builders who are in my opinion being taken advantage of. Because of lack of experience with web development anyone who has not been given a detrimental Jet Pack plugin. I know that as a WordPress user and developer I have been using it since it’s inception that JetPack used to be a great deal less expensive than what it is currently being offered at. Jetpack social used to be a lot less easier and a great deal less convenient. WordPress is supposed to be open source but the degree of difficulty I feel really really sorry for someone just discovering it and trying to figure it all out. I understand we are in the middle of an economic worldwide crisis, but this should not be a reason to impair those who are just starting out and putting the number of plugins that are required to upgrade to premium features. My opinion for what it’s worth. Having said that Jetpack when it runs well offers a fantastic number of features that puts everyone just starting out on their sites who have no clue about how to get a site running well and which plugins integrate well with the other. It is possible to get a full featured website without paying cash for a plugin to run at a premium.

    Plugin Support Alin (a11n)

    (@alinclamba)

    Hello @neiljordan and @createitwithrach,

    Firstly, I apologize for any confusion. You are correct, Neil, it does seem counterintuitive to disable the XML-RPC authentication. I apologize for the confusion. What we want to suggest was to ensure that Wordfence is not blocking XML-RPC requests. You can check this under Wordfence > Firewall > All Firewall Options > Rules, and look for any rules related to XML-RPC.

    @createitwithrach, I understand your concerns about Jetpack’s pricing and feature set. We strive to provide a balance between free and premium features to accommodate users with varying needs and budgets. While Jetpack does offer premium features, the core plugin is still available for free and includes many valuable features such as site stats, related posts, image performance enhancements, and more. However, if you have any issues with Jetpack, please open your own thread and we’ll be happy to assist.

    As for the issue at hand, @neiljordan, if you’ve checked the Wordfence settings and the issue persists, I recommend reaching out to your hosting provider again to ensure that they have indeed whitelisted the Jetpack IP addresses and are not blocking any requests to the XML-RPC file.

    In addition, since you mentioned that you’re using a scheduling plugin, could you please let us know which plugin you’re using? There might be a conflict between that plugin and Jetpack’s sharing feature that we need to investigate.

    Please keep us updated on your progress, and we’ll be here to help you further.

    Thread Starter NeilJordan

    (@neiljordan)

    Hi

    I can’t see any reference to that in the firewall rules.

    I will try my host again, but I don’t hold out much hope so I might just need to find a different solution here.

    The scheduling plug is this one: https://en-gb.wordpress.org/plugins/the-tech-tribe/

    I kust had to re-insert the API key for it to add new posts as it does monthly, presumably because of the plugins being removed and added back. The posts for this month had already been drafted though and the most recent one published again hasn’t been posted to FB etc.

    Plugin Support lastsplash (a11n)

    (@lastsplash)

    Hi @neiljordan

    Thanks, I would check with your host. We’re still getting the error:

    This error can also occur when your web server is overloaded. I’d ask them to check the load on your server. It took us ~3 minutes to test the connection 50 times and in most cases we see those tests run back-to-back much quicker than that.

    Plugin Support Stef (a11n)

    (@erania-pinnera)

    Hello @neiljordan,

    Do you have updates about that? 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!

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Automatic Share to Social not working’ is closed to new replies.