Alternative Linkedin Configuration Not Working

  • Resolved dennisjpitocco

    (@dennisjpitocco)


    4 years, 1 month ago

    Can’t seem to get a response to our Support Tickets (latest Ticket #12776)

    Normal Linkedin Configuration with NextScripts API doesn’t ever work for us (for posting to Groups), so we’ve been using alternative configuration (Session ID li-at) for many months without a problem. Stopped working over a week ago. Tried new Session I.D. still not working. Tried with just passwords, still not working. Disabled all plugins, but no conflicts. Cron test fine. HELP!

    Here’s a copy of the error message:

    Array ( [postID] => [isPosted] => 0 [pDate] => 2020-10-07 13:51:39 [Error] => Post Problem: Array ( [headers] => Array ( [cache-control] => no-cache, no-store [pragma] => no-cache [content-length] => 14 [expires] => Thu, 01 Jan 1970 00:00:00 GMT [set-cookie] => li_mc=; Domain=.linkedin.com; Expires=Thu, 01 Jan 1970 00:00:00 UTC; Path=/; Secure [x-restli-error-response] => true [x-restli-protocol-version] => 2.0.0 [x-li-service-worker-blacklist] => control [expect-ct] => max-age=86400, report-uri=”https://www.linkedin.com/platform-telemetry/ct” [x-xss-protection] => 1; mode=block [content-security-policy] => default-src ‘none’; style-src ‘none’ ‘report-sample’; script-src ‘none’ ‘report-sample’; report-uri https://www.linkedin.com/platform-telemetry/csp?f=jv [x-frame-options] => sameorigin [x-content-type-options] => nosniff [strict-transport-security] => max-age=2592000 [x-li-fabric] => prod-ltx1 [report-to] => {“group”:”network-errors”,”max_age”:2592000,”endpoints”:[{“url”:”https://www.linkedin.com/li/rep”}],”include_subdomains”:true} [nel] => {“report_to”:”network-errors”,”max_age”:1296000,”success_fraction”:0.00066,”failure_fraction”:1,”include_subdomains”:true} [x-li-pop] => afd-prod-eda6 [x-li-proto] => http/1.1 [x-li-uuid] => KYoW9Ra6OxawxGArkSsAAA== [x-msedge-ref] => Ref A: 7D06A0EFDF9F4853952CB482309F06AA Ref B: NYCEDGE1316 Ref C: 2020-10-07T13:51:40Z [date] => Wed, 07 Oct 2020 13:51:39 GMT ) [body] => {“status”:400} [response] => Array ( [code] => 400 [message] => Bad Request ) [cookies] => Array ( [0] => nxs_Http_Cookie Object ( [name] => li_mc [value] => [expires] => 0 [path] => / [domain] => .linkedin.com [secure] => ) ) ) )

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

Viewing 15 replies - 1 through 15 (of 26 total)
  • dawngmcgregor

    (@dawngmcgregor-1)

    Hi

    I am experiencing the exact same issue with all our linkedin account.

    Did you find a solution?

    Thanks
    Dawn

    Thread Starter dennisjpitocco

    (@dennisjpitocco)

    Wish I could say YES, Dawn, but it’s near impossible to get a response these days from the SNAP Support team. We’ve tried everything to get their attention, but zero response. Been happy customers for about 8 years, but seriously considering ditching SNAP and demanding a refund. Do let me know if you learn of a solution to the Support Issue you mentioned.

    dawngmcgregor

    (@dawngmcgregor-1)

    I have two tickets open they have responded to one last night and awaiting on their next reply but will let you know if i here from them.

    Slightly glad to know others are having same issue and not just me and banging my head off walls to think what else to try to get it to work

    Thanks

    Thread Starter dennisjpitocco

    (@dennisjpitocco)

    Very much appreciated Dawn – as your relay of the solution may save us as a SNAP customer.

    Thread Starter dennisjpitocco

    (@dennisjpitocco)

    Hi Dawn – have you managed to get an update on this issue that we share?

    dawngmcgregor

    (@dawngmcgregor-1)

    Hi. Afraid not. saw there was an update this morning but no joy from it.

    Thread Starter dennisjpitocco

    (@dennisjpitocco)

    Indeed, we had hoped as well that the update was going to solve the issue. What’s interesting, is we’ve taken the nuclear option by deleting all of data (regrettable) and starting from scratch. Using the NextScripts API, same problem as before. Using the LinkedIn API, we were able to successfully post to a LinkedIn Profile, but just once. Any posts after the first “test post” resulted in the same error message that this whole adventure began with.

    Still no responses from my 11-day old ticket. We’ve even gone as far as to write directly to the Ludwig (the Developer). Dead silence. We’ve had such a great experience with this plug-in over many years, which makes their non-responsiveness even more perplexing.

    We’re now (reluctantly) researching the next best alternative to SNAP as we wait for a glimmer of hope from these folks.

    Thanks for keeping me in the loop!

    dawngmcgregor

    (@dawngmcgregor-1)

    Hi Dennis

    Have you seen the support doc that mentions linkedin can possibly block ip addresses – it doesint give an example of this error but as ours both mention the word blacklist wondering if it is this.

    It says a way around this is using a proxy and setting it up under the advanced tab for each linkedin profile

    Thread Starter dennisjpitocco

    (@dennisjpitocco)

    Haven’t seen the support doc you mentioned here, Dawn – appreciate the advice, we’ll give it a try..

    dawngmcgregor

    (@dawngmcgregor-1)

    Hi Just wondering if you had any luck with this?

    Thread Starter dennisjpitocco

    (@dennisjpitocco)

    Good morning, Dawn. Wish I could offer you some good news, but our frustration has gone well beyond the tipping point with SNAP Support. Took them 13 days to respond to our Ticket regarding the above issue and the best they could do was suggest that we were being blocked by LinkedIn (referring us to use the Proxy approach), despite the fact that we confirmed that we are not being blocked. We are freely able to share directly with our various Pages, Profile AND our 32 Groups –which would not be possible if we were being blocked. Just out of curiosity, we tested the Proxy approach and got the exact same error message.

    Never in our many years of dealing with SNAP support have we experience such a deplorable speed and quality of response. Barring a (serious) speedy reply, we’re on the verge of ditching SNAP altogether and adding our scorched-earth review to their Plugin page.

    Do let us know if you get a more productive response from SNAP!

    dawngmcgregor

    (@dawngmcgregor-1)

    Thanks for the update. I have yet to have an answer to our two tickets. We are currently looking at alternative plugins they only downfall is cant see another with a linkedin setup similar so will have to do the app route for all the linkedin profiles we use.

    Thread Starter dennisjpitocco

    (@dennisjpitocco)

    We’ll let you know if we find a reasonable alternative & please do the same. Ps. Not sure what you mean by the “app route”?

    Thread Starter dennisjpitocco

    (@dennisjpitocco)

    Hi Dawn – we chased the Developer (Ludwig) again this morning and just got another worthless response:

    “Apologies for the delayed response. Please update to plugin Version 4.3.19 and API version 4.5.5.”

    We did this update 2 weeks ago, hoping that it would include a fix, but it did not. Back to the chase!

    pboch

    (@pboch)

    Hi Dawn and Denni –
    just to let you know that I’ve experienced the same issue – both in technical terms and in the slow response from SNAP.
    I’m still hoping there will be an answer to my tickets soon, but I’ll also start searching for alternatives.
    So far, most alternatives only seem to be able to post to profiles and pages, not to groups. Have you been successful in either finding an alternative or getting an answer from SNAP?
    THanks
    Patrick

Viewing 15 replies - 1 through 15 (of 26 total)
  • The topic ‘Alternative Linkedin Configuration Not Working’ is closed to new replies.