为什么LinkedIn API返回"999:请求失败"?信息? [英] Why is LinkedIn API returning "999: request failed" message?

问题描述

一段时间以来，我一直在使用LinkedIn API并没有遇到麻烦，今天突然可以正常工作的调用开始失败.该API返回标题为"999:请求失败"的HTML页面.页面正文显示:抱歉，由于您的网络连接流量异常，我们目前无法满足您的请求."

I have been using the LinkedIn API without trouble for a while and suddenly today calls that used to work started failing. The API returns an HTML page titled "999: request failed". The body of the page says "Sorry, we are unable to serve your request at this time due to unusual traffic from your network connection."

LinkedIn的异常活动"是什么意思?

What does LinkedIn mean by "unusual activity"?

LinkedIn是否对我的应用程序每天可以拨打的电话数量实施限制?如果是这样，它们是什么?

Has LinkedIn implemented limits to the number of calls my application can make in a day? If so, what are they?

或者，他们是停止从应用程序的VPC的IP地址发出呼叫吗?有没有确定原因的方法?

Or, are they stopping calls from the IP address of my application's VPC? Is there a way to determine the reason?

推荐答案

通过任何更改，故障都是断断续续的，并且仅在几天前才开始?

By any change are the failures intermittent, and only started a few days ago?

在过去的两天里，我在两个不同的Linkedin应用程序，两个不同的服务器上都遇到了相同的问题，间歇性失败导致无法进行oAuth连接和进行API调用.我本人也张贴了一个类似的主题:间歇性地收到来自LinkedIn API的999个请求被拒绝.原因代码1,2,1指的是什么鉴于它是断断续续的，并且发生在两台服务器上的两个应用程序上，自两天前以来，我不敢相信它是异常活动的IP阻止.我自己的使用率非常低.

I've been suffering from the same problem, on two different linkedin apps, on two different servers, over the past 2 days, intermittent failures both to do an oAuth connect, and to make API calls. I posted a similar topic myself: Intermittently receiving 999 Request Denied from the LinkedIn API. What does reason code 1,2,1 refer to Given its intermittent and happens on two apps on two servers, since two days ago, I cannot believe its an IP block for unusual activity. My own usage was very very low.

在过去的几天里，有人通过Twitter与我联系，他的问题同样也是断断续续的，而且在过去的几天里(还有在我所在的Linode上).他们认为问题归结于通过IPv6进行连接，并且自从禁用与LinkedIn的连接中的IPv6以来，问题已经得到解决.

Someone kindly got in touch with me via twitter, who had the same problems also intermittent, and for the past couple of days (and also, on Linode which is where mine are hosted). They suggested that the problem is down to connecting over IPv6, and that since disabling IPv6 in connections to LinkedIn it has resolved for them.

当我使用标准的开放源代码库进行oAuth和共享时，我现在不得不在服务器级别禁用IPv6，并且一切似乎都在进行.我使用这种方法禁用了IPv6- https://askubuntu.com/Questions/440649/how-to-dis-disable-ipv6-in-ubuntu-14-04 .这显然不是一个长期的解决方案.我希望LinkedIn上的某人会对此做出答复，这将导致他们的服务错误地阻止了事情.

As I'm using standard open source libraries to do the oAuth and sharing, I've had to disable IPv6 at a server level for now, and things seem to be working. I used this approach to disable IPv6 - https://askubuntu.com/questions/440649/how-to-disable-ipv6-in-ubuntu-14-04. This obviously isn't a long term solution. I'm hoping that someone from LinkedIn will reply to this and it will turn out to be an issue with their services blocking things incorrectly.

LinkedIn API 集成现在又对我有用了，至少现在是这样.但是，我仍然希望LinkedIn成员能提供一些解决方案.

LinkedIn API integration is working again for me now, for now at least. However I'm still hoping for some resolution from a member of LinkedIn staff.

作为背景，发现故障后，我能够从身体得到异常活动"消息，如您所见.它也包含指向取消阻止形式的链接，尽管没有引用与阻止有关的内容.我完成了此操作，并着重指出了问题，并且还指出，有几周前，有报道称Google Compute Engine被意外阻止(LinkedIn工作人员回复，确认这是一个错误-Linkedin正在做Google云/App Engine块)))，如果这是类似的问题-我的服务器使用的是Linode，那么可能是他们错误地阻止了更多云提供商.不幸的是，我只是对我提交的表单作了全面的答复，没有明确的指示，并要求我在此处进行张贴(这很困难，因为这实际上不适合Stack Overflow).LinkedIn似乎并没有使开发人员与他们合作变得容易，因为没有机制可以报告您认为API方面存在问题的事情，加入他们的合作伙伴程序来访问支持似乎是唯一的选择我可以看到.

For background, after spotting the failures I was able to get the "unusual activity" message from the body as you have found. This also contained a link to an unblock form, though with no references to what the block was in relation to. I completed this, and highlighted the problem, and also pointed out that there had been reports on here of Google Compute Engine being accidentally blocked a couple of weeks ago (which was replied to by LinkedIn staff confirming it was a mistake - Linkedin is doing a google cloud / App Engine block)) and wondering if this was a similar problem - my servers are with Linode, and so possibly they were blocking more cloud providers in error. Unfortunately, I've just had blanket replies to the form I submitted, with no clear indication, and asking me to post on here (which is difficult, given this isn't really suitable for Stack Overflow). LinkedIn don't seem to be making it easy for developers to work with them, as there is no mechanism to report things which you believe are a problem their side with the API, joining their partner program to access support seems to be the only option I can see.

这篇关于为什么LinkedIn API返回"999:请求失败"?信息?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！