999 => for -- https://www.linkedin.com/in/some-profile

[xksusha]

Hey, this issue is still not resolved: impossible to make even the first request, I fall directly on the 999 error whereas the

curl -A "Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3" -I --url

works perfectly well.

[yatish27]

Fixed on 1.0.5 latest version

[Torq07]

I have the same issue with version 1.0.5 . Any thoughts?

UPD: Looks like in my case that's because i run it on Digital Ocean instance.

[yatish27]

Can you check if the same issue is on local machine ?

[Torq07]

On local machine all is ok.
Maybe you can help me? What this error is mean? Why it's not working on DO? How can i resolve this issue for DO? I thought that's because DO/AWS and others providers has been blocked by IP, but if i use proxy nothing changed.

[yatish27]

Which proxy are you using ? Try paid proxies from https://instantproxies.com/

[Torq07]

Thanks, will try it now .

[Torq07]

Tried to use proxy from https://instantproxies.com/ and had that same result. 999((( Even if i use it on local machine with this proxy i get this 999 response.

[yatish27]

Give the link of the profile

On Mon, Apr 25, 2016 at 7:10 AM -0700, "Torq07" [email protected] wrote:

Tried to use proxy from https://instantproxies.com/ and had that same result. 999((( Even if i use it on local machine with this proxy i get this 999 response.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub

[Torq07]

It's not working not for some specific profile. It's not working from DO/AWS/RussianVPS with proxy. And if i run it from local machin with proxy it is not working too. Have you tried to run it on AWS or DigitalOcean instance?

[Jasonw152]

I have the same problem with Digital Ocean. Localhost works but server side nope.

Could maybe somebody share a configuration that works? What VPS are you using? Do you use a proxy/vpn in between? What proxy/vpn vendor are recommended to be used?

Thanks in advance
Jason Reto

[Jasonw152]

@yatish27 would you be able to share your configuration?
Thanks a lot

[danielpclark]

I'm receiving this same error on any profile I give. gem install linkedin-scraper

require 'linkedin_scraper'
# => true 
Linkedin::Profile.get_profile('https://www.linkedin.com/in/danielpclark')
#999 =>  for  -- https://www.linkedin.com/in/danielpclark
# => nil 

[danielpclark]

I believe this is an issue with the User Agent being blocked by Linkedin. The user agents in this repo are out of date. I got the same error myself manually scraping with mechanize until I changed the user agent.

May I suggest either requiring people to enter their own agent or grabbing a random one from here http://ua.theafh.net/ . It's a user agent search & listing page. The closer to the top of the page the more recent the user agent.

[yatish27]

The latest version uses randomuser agent, it still doesn't solve the company page browsing issue

[yatish27]

Fixed in master.

[ParthivSavani]

@yatish27 It's awesome. But somehow this gem is not working on heroku. Any solution?

[danielpclark]

@viha4582 I think they block those IP addresses.

[rubenbaden]

Can someone help me update an installed gem after I have made changes to a clone locally?

Im testing wether or not the user agents are bad, so I added mine to a file and removed the other 900 or so.

[rochenka]

I solved the blocking problem by using proxycrawl API, i make get requests to that API which calls linkedin and gives the html data back.