A solution to the challenge error when deploying to a server

[farhankhot]

First of all, thank you for this amazing API! I have tried to solve the challenge error with the help of one's own cookies (you can get it from your LinkedIn homepage). I modified the set_session_cookies to accept cookies and converted them into a CookieJar object. This bypasses the challenge error that may arise due to a difference in IP address. All the functions then work as normal. Getting one's cookies from a valid LinkedIn login session is left up to the user (this is easier to do if you are using it in a chrome extension like I am).

[chrishubert]

Thanks for the pull request,
To ease the review, would you mind minimizing the changes in the file?
You added several print, modified the headers, it makes it difficult to follow your logic.
I'd recommend only editing the bare minimum 🙏

[farhankhot]

Hi! Thanks for the comment. Should I send a new pull request? I am unsure of how to proceed.

[chrishubert]

@farhankhot, you should the same pull request, your new commits will be added automatically

[Sorrycion]

@farhankhot how are you getting the cookies? You said that you are using an extension? Which one?

Is there anything else to setup besides the extension?

[farhankhot]

@farhankhot how are you getting the cookies? You said that you are using an extension? Which one?

Is there anything else to setup besides the extension?

You can create a simple extension that just reads the cookies that are stored in the browser. Let me know if you need some more guidance!

[Sorrycion]

@farhankhot how are you getting the cookies? You said that you are using an extension? Which one?
Is there anything else to setup besides the extension?

You can create a simple extension that just reads the cookies that are stored in the browser. Let me know if you need some more guidance!

Thank you, I was able to do a Chrome extension and get the cookies from there.

I also noticed that with the extension you can get the API calls and responses from Network. So you don't need to call the API again, and reduces the risk of being blocked because of too many calls.