Reputation: 189
A few stackoverflow questions make reference to the widely used method of using
https://www.linkedin.com/sharing/share-offsite/?url={url}
to let users share content from your site to their linkedin pages, but this results in a "something went wrong" error from linkedin or just the linkedin header logo on a blank page when used with any URL, percent encoded or otherwise.
The developer docs point to an oauth2 method of sharing, but that's total overkill for a share button on a website.
Was there an announcement? I can't find any and lots of websites (Youtube, NYT, ABC(AU)) are currently using this method of sharing including, ironically the very Microsoft developer doc that instructs you about oauth2 sharing.
Upvotes: 8
Views: 9523
Reputation: 31
It is 2024 and this seems to be the one thing that is working:
https://www.linkedin.com/feed/?shareActive=true&text={ url }
Upvotes: 3
Reputation: 31
I just ran into the same problem today and found this question and this thread.
In our case it was because we switched our CDN and webservers from minimum TLS version v1.2 to v1.3 - not a problem for all modern browsers, but obviously a problem for LinkedIn :-( Reverting the minimum requirement back to TLS v1.2 solved the issue, the share-offsite URL works again.
This is a also bad surprise because the LinkedIn Post Inspector (see https://www.linkedin.com/post-inspector/ ) didn't come up with an information or warning. It seems to be fine with TLS v1.3.
And one final note: Using "{url}" instead of {url} as one comment says does not seem to make a difference.
Upvotes: 0
Reputation: 34
Issue is fixed for me
If you still have an error check if you don't have
this :
https://www.linkedin.com/sharing/share-offsite/?url="{url}"
instead of this :
https://www.linkedin.com/sharing/share-offsite/?url={url}
Upvotes: -1
Reputation: 31
As far as I can tell, that method is still a viable way to share to LinkedIn. That error message and this issue seem to be impacting major websites so it appears that something has broken on LinkedIn's side of things. I have been unable to find any acknowledgement of the issue but can attest my users started noticing it yesterday.
Upvotes: 2