Can’t connect LinkedIn for shocial sharing

Viewing 6 replies - 16 through 21 (of 21 total)
1 2
  • Plugin Support lastsplash (a11n)

    (@lastsplash)

    2 years ago

    Hi @jikamens –

    We’ve heard back from our development team.

    To help isolate the issue, could you try connecting to either Tumblr or Facebook and let us know if that works? That will allow us to see if the problem is with just the LinkedIn connection flow.

    Additionally, we are still seeing issues with the Jetpack connection. You can see this when testing at:

    https://jptools.wordpress.com/debug/?url=https://blog.kamens.us/

    To fix the connection issue, I’d recommend allow listing our IPs via your host. You can get a list of those here:

    https://jetpack.com/support/how-to-add-jetpack-ips-allowlist/

    Let us know how it goes connecting another social network and if you can get the connection issue fixed.

    Thread Starter jikamens

    (@jikamens)

    2 years ago

    Tumblr fails to connect as well.

    We’ve been through all this connectivity nonsense before. I’m tired of rehashing the same ground in this ticket.

    Adding Jetpack’s IP’s to Wordfence’s allowlist does not fix the problem. Disabling Wordfence entirely does not fix the problem. Wordfence’s WAF logs do not indicate that it is blocking any requests from Jetpack. There is no other firewall between my blog and the outside world.

    When I visit the debug page it’s clear from my logs that Jetpack is able to successfully access my site:

    192.0.100.247 – – [01/May/2023:10:06:42 -0400] blog.kamens.us “POST /xmlrpc.php HTTP/1.1” 200 181 “https://blog.kamens.us/xmlrpc.php” “Jetpack by WordPress.com” in=675 out=4581
    192.0.100.247 – – [01/May/2023:10:06:42 -0400] blog.kamens.us “POST /xmlrpc.php HTTP/1.1” 200 181 “https://blog.kamens.us/xmlrpc.php” “Jetpack by WordPress.com” in=700 out=4580
    192.0.100.247 – – [01/May/2023:10:06:42 -0400] blog.kamens.us “POST /xmlrpc.php?for=jetpack&rand=925741894 HTTP/1.1” 200 463 “https://blog.kamens.us/xmlrpc.php?for=jetpack&rand=925741894” “Jetpack by WordPress.com” in=738 out=4864
    192.0.100.247 – – [01/May/2023:10:06:42 -0400] blog.kamens.us “GET / HTTP/1.1” 200 161545 “https://blog.kamens.us/” “Jetpack by WordPress.com” in=508 out=167411
    192.0.100.247 – – [01/May/2023:10:06:42 -0400] blog.kamens.us “POST /xmlrpc.php?for=jetpack&token=[deleted]&timestamp=1682950002&nonce=[deleted]&body-hash=[deleted]&signature=[deleted] HTTP/1.1” 200 179 “https://blog.kamens.us/xmlrpc.php?for=jetpack&token=%5Bdeleted%5D&timestamp=1682950002&nonce=%5Bdeleted%5D&body-hash=%5Bdeleted%5D&signature=%5Bdeleted%5D” “Jetpack by WordPress.com” in=1269 out=4579
    192.0.100.247 – – [01/May/2023:10:06:42 -0400] blog.kamens.us “POST /xmlrpc.php?for=jetpack&token=[deleted]&timestamp=1682950002&nonce=[deleted]&body-hash=[deleted]&signature=[deleted] HTTP/1.1” 200 1249 “https://blog.kamens.us/xmlrpc.php?for=jetpack&token=%5Bdeleted%5D&timestamp=1682950002&nonce=%5Bdeleted%5D&body-hash=%5Bdeleted%5D&signature=%5Bdeleted%5D” “Jetpack by WordPress.com” in=1257 out=5647

    There’s nothing in the error log.

    Jetpack’s own uptime monitoring shows no downtime for my site going back to at least April 21.

    It is beyond frustrating that you continue to ask me to debug and solve this on my end when there is literally nothing I can do about it on my end.

    It’s clear that if Jetpack is having trouble connecting to my site the only way we’re going to figure out why is to look at the detailed error logs ON YOUR SERVERS, because there’s zero evidence that the problem is on my end, zero insight into the problem in any of my logs, and nothing you have suggested I do on my end to fix it has had any effect whatsoever.

    • This reply was modified 2 years ago by jikamens.
    Plugin Support lastsplash (a11n)

    (@lastsplash)

    1 year, 12 months ago

    Hi @jikamens –

    Thanks for the additional information. I have shared it with our development team and we’ll let you know as soon as we have a response.

    Plugin Support lastsplash (a11n)

    (@lastsplash)

    1 year, 11 months ago

    Hi @jikamens –

    Thanks for your patience.

    Our development has looked into this by investigating the logs on our end. They see that there is an intermittent issue with the Jetpack connection to your site. They believe this is the underlying cause of the issue here. When we test the connection, we’re seeing the error:

    Jetpack: [http_request_failed] cURL error 7: Failed to connect to 45.79.160.233 port 443 after 6 ms: Couldn't connect to server

    The 500 Error you mention is from the API request to create the connection, but if the site isn’t connected properly, that is the underlying cause of the issue. If we encounter any errors during the connection process, the API call will fail.

    Looking at our logs, it appears that despite this, Jetpack was able to successfully create LinkedIn and Tumblr connections on the blog, but were deleted almost immediately.

    We think that because the connection is being being created ok, the error is coming from the final step when we try and contact your site. Even though an error might show, please try reloading the page after reconnecting. When you do that, do you see a “Disconnect” button next to the social media connection? If so, it means it has worked.

    That said, our development team recommends that you address the underlying connection issue.

    Let us know how it goes.

    Thread Starter jikamens

    (@jikamens)

    1 year, 11 months ago

    Thank you. With this useful information I was finally able to figure out what’s going wrong and fix it. It turns out that the problem was an overly aggressive fail2ban configuration which was being triggered by the Jetpack requests to my xmlrpc.php and causing fail2ban to temporarily block connections from Jetpack right in the middle of its attempt to configure sharing. I’ve reconfigured fail2ban to avoid the problem and now I am able to connect LinkedIn successfully. Looking forward to when I’ll be able to add Mastodon as well.

    JS (a11n)

    (@julesomattic)

    1 year, 11 months ago

    Excellent, glad to hear it. I’ll mark this as resolved.

Viewing 6 replies - 16 through 21 (of 21 total)
1 2
  • The topic ‘Can’t connect LinkedIn for shocial sharing’ is closed to new replies.

Tags