Mechanize::ResponseCodeError: 999 => for -- https://www.linkedin.com/in/jeffweiner08

[washingon]

linkedin-scraper (2.1.1)

irb(main):001:0> require 'linkedin-scraper' => true irb(main):002:0> profile = Linkedin::Profile.new("http://www.linkedin.com/in/jeffweiner08") Mechanize::ResponseCodeError: 999 => for -- https://www.linkedin.com/in/jeffweiner08

[pinymax]

Same for me. Works well on local machine, but doesn't work on Heroku or AWS. Is any way to use proxy or somehow fix this problem?

[natemcguire]

Same here. Looks like we need to set the user agent for mechanize.

https://github.com/sparklemotion/mechanize/issues/336

[pinymax]

@natemcguire "The latest version uses randomuser agent" So I guess, it wouldn't ihelp

[CodeCompiler]

Need to put a proxy service like storm proxies into this so the IP resolution doesn't come back

[yatish27]

@CodeCompiler Any suggestion PRs

[chamnap]

@CodeCompiler, does the storm proxies work for you? I used myprivateproxy, but it doesn't work at all.

[rcavezza]

I just bought 10 proxies from instantproxies and I can't get a single valid response, whereas I can get a few responses per day without using a proxy. I'm only passing proxy_ip and proxy_port, not username and password.

[rcavezza]

I also bought a few IPs from StormProxies and I am having the same issues. I'm now using username and password on localhost - same result, 999 Mechanize error.

[rcavezza]

I created a PR, but it didn't fix my issue. If anyone has any insight into why this is occurring for me and can point me in the right direction on how to fix it, I'd really appreciate it. I can't tell if this is happening for everyone, or a small subset of people (based on the previous comments).

[rcavezza]

I have not been able to get over this issue. I'm going to attempt to use the mechanize gem without linkedin-scraper in hopes that I will be able to get it to work correctly. If I find a solution, I will come back and apply the fix to this repo.

[iliasnaamane]

Same error here /home/youpi/.rvm/gems/ruby-2.2.0/gems/mechanize-2.7.5/lib/mechanize/http/agent.rb:949:in `response_read': 999 Kindly help me, thanks

[Startouf]

Hey, any updates on this ? Also it seems like a duplicate of https://github.com/yatish27/linkedin-scraper/issues/70

I have tried StormProxy, limeProxies instantProxies and all IPs were already blocked apparently, even those who were said to be "linkedin proxies"

[matsossah]

@iliasnaamane @rcavezza @chamnap @yatish27 @CodeCompiler @pinymax @natemcguire @washingon Has anybody been able to resolve this issue? @Startouf and I work together and haven't found a single solution yet :/ Thanks in advance for any help you could provide!

[borenstejn]

Hi Guys,

I'm just trying to use the gem locally and after having succeeded twice, I end up with the same message: Mechanize::ResponseCodeError: 999 => for -- http://www.linkedin.com/in/jeffweiner08

I thought it was a problem with my IP address so I used a VPN (betternet) to trick LinkedIn, but i still have the same error coming. Do you have any clue for me ?

Thanks a lot

[Startouf]

Hey @borenstejn I actually got a mail from a Proxy company that explained to me it was very hard nowadays to get a hold of proxys that work with Linkedin since they've become very aggressive.

FYI list of proxies already tried

• InstantProxies.com
• stormproxies
• limeProxies
• shader (who reported to me what I wrote just above)
• betternet (reported by @borenstejn)

I'd be glad to have your feedback in case you find something that works, thank you very much.

[georgenicholas]

Did anyone ever figure this out? I'm getting the 999 error, it hasn't worked even once yet. I'm running this locally.

[shantilal-narola]

Any update on this?

[tp00012x]

Has somebody figured this out?

[sakinho]

This error happens to me locally with no proxy. Any idea of how to solve it?