Alternative Linkedin Configuration Not Working

  • Resolved dennisjpitocco

    (@dennisjpitocco)


    4 years, 5 months 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 11 replies - 16 through 26 (of 26 total)
  • Thread Starter dennisjpitocco

    (@dennisjpitocco)

    Hey Patrick,

    Thanks for joining our eternal quest to get some well-deserved attention from SNAP support for an issue that’s been plaguing many for some time. Our search for alternative continue, but so far, only turning up what you’ve already discovered – ample plugins for posting to LI Profiles and Pages, but nothing to Groups. A big issue for us, as we’ve got 30+ Groups. And quite frankly, we’ve had much success with the SNAP plugin and support for many years – all of which seemed to evaporate about a month ago.

    Let us all keep each other updated on any SNAP solutions or alternatives discovered.

    Plugin Author NextScripts

    (@nextscripts)

    This problem has been fixed in the latest API version 4.5.6. Please go to the Help/Support page and click “[Check for API Update]”

    Thread Starter dennisjpitocco

    (@dennisjpitocco)

    The latest (redundant and unhelpful) response from Ludwig (Developer):

    “This problem has been fixed in the latest API version 4.5.6. Please go to the Help/Support page and click “[Check for API Update]”

    We’ve told them repeatedly that we are operating with the very latest API Version and the problem still exists.

    Frustrating, indeed. It’s now been 4-weeks with zero Support Solutions.

    Hi Dennis
    have you tried removing the proxy that was part of their last suggested solution?
    Removing the proxy, posting now worked for me (to a group, too)

    Thread Starter dennisjpitocco

    (@dennisjpitocco)

    Yes, we tried the Proxy suggestion weeks ago and removed it as it didn’t work.

    Plugin Author NextScripts

    (@nextscripts)

    told them repeatedly that we are operating with the very latest API

    @dennisjpitocco the quoted message “This problem has been fixed in the latest API version 4.5.6″ came to you literally 2 minutes after API 4.5.6 was released.

    Please update and try.

    API 4.5.6 completely fixes the 400 error (with and without proxy).

    {“status”:400} [response] => Array ( [code] => 400 [message] => Bad Request )

    So unless you are getting a different error (some users getting error 303, we still working on that) it should work.

    It seems to be working again for us with the lastest api update. Just url links appear to be having wee issues

    • This reply was modified 4 years, 4 months ago by dawngmcgregor.
    Thread Starter dennisjpitocco

    (@dennisjpitocco)

    Thanks, Dawn. And we finally had our EUREKA moment after removing SNAP altogether, reinstalling from scratch, updating the API and it’s working again. Also managed to get the attention of the developer (Ludwig) who’s come to our rescue late in the game, and only after we already got it working….

    Glad you got it all working. I was all set to move before it randomly started to work again.

    Could i possibly use your knowledge of the plugin and do you know why it would be bringing in /n all over the post and adding it to the urls

    ex. TEST SCHEDULED has been published by #FLEETMAXXSOLUTIONS NEWS https://lnkd.in/eK3egAg \nPlease ignore\n #Fleet #FleetNews #FleetManagement #Motoring #FleetManager

    thanks

    Thread Starter dennisjpitocco

    (@dennisjpitocco)

    We’ve seen this before/couldn’t find nor get a solutions response from Support and finally just settled for using Article Text Format: %TITLE% %URL%

    Plugin Author NextScripts

    (@nextscripts)

    Problem with “\n” has been fixed in the new API version 4.5.8. Please go to the Help/Support page and click “[Check for API Update]”

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