Viewing 15 replies - 1 through 15 (of 21 total)
  • Are you trying to connect a personal LinkedIn account or a Company Page?

    Jetpack doesn’t currently support Company Pages on LinkedIn, but we’re looking into supporting them in the future.

    Thread Starter jikamens

    (@jikamens)

    Personal account.

    Plugin Support Tamirat B. (a11n)

    (@tamirat22)

    Hi @jikamens,

    Thanks for getting back to us.

    I see that your xmlrpc endpoint is publicly accessible as you mentioned earlier.

    However, I see that your site’s connection to Jetpack is currently broken and throwing a communication error as shown here: https://jptools.wordpress.com/debug/?url=https://blog.kamens.us

    As a first step, I would recommend re-installing and reconnecting Jetpack as shown here: https://jetpack.com/support/reconnecting-reinstalling-jetpack

    Once you have done the above, please try adding your LinkedIn connection again and get back to us if the problem persists.

    Best,

    Thread Starter jikamens

    (@jikamens)

    I have subscribers and image hosting through Jetpack. Jetpack has also been collecting stats on my site for years. Will all of that get erased if I disconnect and reconnect Jetpack, or will it be preserved and still be there after I reconnect?

    Thread Starter jikamens

    (@jikamens)

    Note that at least as far as my server is concerned the connection is fine. All the requests your debug tool is sending to my server are getting back 200 response codes:

    192.0.99.45 – – [30/Mar/2023:12:51:16 -0400] blog.kamens.us “POST /xmlrpc.php HTTP/1.1” 200 181 “https://blog.kamens.us/xmlrpc.php” “Jetpack by WordPress.com” in=966 out=5260
    192.0.99.45 – – [30/Mar/2023:12:51:16 -0400] blog.kamens.us “POST /xmlrpc.php HTTP/1.1” 200 181 “https://blog.kamens.us/xmlrpc.php” “Jetpack by WordPress.com” in=991 out=5260
    192.0.99.45 – – [30/Mar/2023:12:51:16 -0400] blog.kamens.us “POST /xmlrpc.php?for=jetpack&rand=1515987319 HTTP/1.1” 200 463 “https://blog.kamens.us/xmlrpc.php?for=jetpack&rand=1515987319” “Jetpack by WordPress.com” in=1031 out=5545
    192.0.99.45 – – [30/Mar/2023:12:51:16 -0400] blog.kamens.us “GET / HTTP/1.1” 200 211500 “https://blog.kamens.us/” “Jetpack by WordPress.com” in=799 out=218194
    192.0.99.45 – – [30/Mar/2023:12:51:16 -0400] blog.kamens.us “POST /xmlrpc.php?for=jetpack&token=[deleted]&timestamp=1680195076&nonce=[deleted]&body-hash=[deleted]&signature=[deleted]” 200 181 “https://blog.kamens.us/xmlrpc.php?for=jetpack&token=%5Bdeleted%5D&timestamp=1680195076&nonce=%5Bdeleted%5D&body-hash=%5Bdeleted%5D&signature=%5Bdeleted%5D” “Jetpack by WordPress.com” in=1572 out=5276
    192.0.99.45 – – [30/Mar/2023:12:51:16 -0400] blog.kamens.us “POST /xmlrpc.php?for=jetpack&token=[deleted]&timestamp=1680195076&nonce=[deleted]&body-hash=[deleted]&signature=[deleted]” 200 1249 “https://blog.kamens.us/xmlrpc.php?for=jetpack&token=%5Bdeleted%5D&timestamp=1680195076&nonce=%5Bdeleted%5D&body-hash=%5Bdeleted%5D&signature=%5Bdeleted%5D” “Jetpack by WordPress.com” in=1556 out=6346
    192.0.101.52 – – [30/Mar/2023:12:51:17 -0400] blog.kamens.us “POST /xmlrpc.php?for=jetpack&token=[deleted]&timestamp=1680195077&nonce=[deleted]&body-hash=[deleted]&signature=[deleted]” 200 181 “https://blog.kamens.us/xmlrpc.php?for=jetpack&token=%5Bdeleted%5D&timestamp=1680195077&nonce=%5Bdeleted%5D&body-hash=%5Bdeleted%5D&signature=%5Bdeleted%5D” “Jetpack by WordPress.com” in=1281 out=4581
    192.0.99.45 – – [30/Mar/2023:12:51:16 -0400] blog.kamens.us “GET /?rest_route=%2Fjetpack%2Fv4%2Fconnection%2Ftest-wpcom%2F&timestamp=1680195076&url=https%3A%2F%2Fblog.kamens.us&signature=[deleted]” 200 89 “https://blog.kamens.us/?rest_route=%2Fjetpack%2Fv4%2Fconnection%2Ftest-wpcom%2F&timestamp=1680195076&url=https%3A%2F%2Fblog.kamens.us&signature=%5Bdeleted%5D” “WordPress.com; https://jptools.wordpress.com” in=1773 out=5519

    Plugin Support lastsplash (a11n)

    (@lastsplash)

    Hi @jikamens

    Sorry for the delay in responding.

    Those settings are stored on our servers, so you won’t lose them when reinstalling Jetpack.

    Please give that a try and let us know how it goes.

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    Hello @jikamens,

    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!

    Thread Starter jikamens

    (@jikamens)

    I disconnected Jetpack, deactivated the plugin, uninstalled the plugin, reinstalled the plugin, reconnected and reconfigured it, and finally once again attempted to enable the connection to LinkedIn for sharing, and I got exactly the same error.

    In short, “turning it off and turning it back on” didn’t work. Do you have any other suggestions?

    Plugin Support Ajay Kumar Jain (a11n)

    (@akumarjain)

    Hi @jikamens,

    It looks like XML-RPC is still not responding correctly on your site. You can test this yourself by running the following command from the command line:

    % curl -A 'Jetpack by WordPress.com' -d 'demo.sayHello' https://blog.kamens.us//xmlrpc.php

    The cURL test returned the following invalid result:

    <?xml version=“1.0" encoding=“UTF-8”?>
    <methodResponse>
      <fault>
        <value>
          <struct>
            <member>
              <name>faultCode</name>
              <value><int>-32700</int></value>
            </member>
            <member>
              <name>faultString</name>
              <value><string>parse error. not well formed</string></value>
            </member>
          </struct>
        </value>
      </fault>
    </methodResponse>

    Please provide this information above to your host, so they can correct the server settings and allow cURL access. Let us know how it goes!

    Thread Starter jikamens

    (@jikamens)

    I don’t know why you think the way you’re invoking xmlrpc.php above is valid, because it’s not.

    It’s called **XML***rpc for a reason. You send requests to it in XML.

    My xmlrpc is working just fine:

    $ python3
    Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] on linux
    Type "help", "copyright", "credits" or "license" for more information.
    >>> import xmlrpc.client
    >>> proxy = xmlrpc.client.ServerProxy("https://blog.kamens.us/xmlrpc.php", verbose=True)
    >>> print(proxy.demo.sayHello())
    send: b'POST /xmlrpc.php HTTP/1.1\r\nHost: blog.kamens.us\r\nAccept-Encoding: gzip\r\nContent-Type: text/xml\r\nUser-Agent: Python-xmlrpc/3.11\r\nContent-Length: 107\r\n\r\n'
    send: b"<?xml version='1.0'?>\n<methodCall>\n<methodName>demo.sayHello</methodName>\n<params>\n</params>\n</methodCall>\n"
    reply: 'HTTP/1.1 200 OK\r\n'
    header: Date: Sat, 15 Apr 2023 20:54:57 +0000
    header: Server: Apache/2.4.53 (CentOS Stream) OpenSSL/3.0.7
    header: X-Powered-By: PHP/8.1.14
    header: Connection: close
    header: Vary: User-Agent
    header: Transfer-Encoding: chunked
    header: Content-Type: text/xml; charset=UTF-8
    body: b'<?xml version="1.0" encoding="UTF-8"?>\n<methodResponse>\n  <params>\n    <param>\n      <value>\n      <string>Hello!</string>\n      </value>\n    </param>\n  </params>\n</methodResponse>\n'
    Hello!
    >>> 
    Plugin Support Alin (a11n)

    (@alinclamba)

    Hi @jikamens,

    The XMLRPC file appears to be accessible at this point, as demonstrated by the following link: https://blog.kamens.us/xmlrpc.php?for=jetpack. We appreciate your notification on the matter.

    Nonetheless, it seems that the Jetpack connection remains disrupted, suggesting an inability to determine the site’s URL. For instance, visiting https://www.blog.kamens.us/ results in an DNS_PROBE_FINISHED_NXDOMAIN error. To resolve this, kindly ensure that the site loads using a single URL, with other URLs redirecting to it, such as https://blog.kamens.us/.

    Let us know if you can do this.

    Thread Starter jikamens

    (@jikamens)

    I don’t understand why you people keep offering me suggestions that are wrong and irrelevant.

    My site’s URL is https://blog.kamens.us, not https://www.blog.kamens.us. There is no need for DNS to resolve for the latter because the latter is not the correct host name for my site.

    My site has been https://blog.kamens.us for nearly 18 years. It has always been that way, with no “www” in the host name, and has always worked fine that way.

    The fact that I am able to establish a Jetpack connection proves that http://www.blog.kamens.us not resolving is not the problem.

    The fact that when I try to enable LinkedIn sharing, I see a successful xmlrpc call from your server to mine in my log before your app says it failed, LOG ENTRIES WHICH I HAVE ALREADY SHARED WITH YOU EARLIER IN THIS CONVERSATION, also proves that http://www.blog.kamens.us not resolving is irrelevant to this problem.

    Is there someone there you can escalate this ticket to who isn’t going to waste my time offering pointless, wrong suggestions and understand actually figure out what’s wrong?

    Hi @jikamens,

    Thanks for getting back to us and apologies for the back and forth on this. I checked and at present your website is properly connected with Jetpack.

    You can test this here https://jptools.wordpress.com/debug/?url=https://blog.kamens.us/

    Can you please try re-connecting Linkedin to the website and let us know if its working for you now?

    Best,

    Thread Starter jikamens

    (@jikamens)

    Jesus.

    I’ve already told you that it’s still not working.

    My site’s connection to Jetpack was never broken and that was never the problem. We’re exactly where we were when I first opened this ticket. Again: is there anyone there who can actually help me?

    i just tried again and at least the error is slightly more informative this time:

    https://photos.app.goo.gl/1tAhqL1f4cNm9P3Z6

    In case you can’t see it, the error in the screenshot is, “500 status code for “POST /sites/139453603/publicize- connections/new”” . Note that 500 error is coming FROM YOUR SERVER, not from my blog. As I’ve been telling you all along, THE PROBLEM IS ON YOUR SERVER, not on my blog.

    Plugin Support lastsplash (a11n)

    (@lastsplash)

    Hi @jikamens

    Thanks for the additional information.

    I’ve escalated this to our development team for them to take a look. We’ll let you know as soon as we have an update.

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