I'm having the error below since January 1st, 2018 when trying to login in my system with Linkedin OAuth2:
500 Server Error: Internal Server Error for url: https://api.linkedin.com/v1/people/~:(email-address,first-name,headline,id,last-name,picture-url,positions,public-profile-url)?format=json
For three days our system was having that error then on the 4th day I just removed Linkedin Login option on our website.
Today, January 11, I've tested again with the hope to enable Linkedin Login again, and the error is still there.
I've seen a similar question and the comments give the idea that it was solved but it wasn't yet.
I don't have reputation to comment on that question, that is why I'm asking here.
Some of you know how to contact Linkedin guys to solve this problem?
It's a problem in their servers.
Related
I have a VB.net application that has been working great with the gmail.api "gmail.send" scope for months. I have about 3 dozen different gmail accounts that have successfully integrated using OAUTH2. Starting yesterday one of the accounts began returning a 403 Forbidden error. Today another one started doing the same thing. Meanwhile, the others are all working just fine, sending plenty of messages successfully every day. My app hasn't been verified yet, but I would think if it were to be shut down then all of the accounts would not work. Likewise if there was some sort of throttling I would think it would apply to my app as a whole and not affect individual users. It seems very strange that some work and others don't. Any ideas?
I dove into the API instructions. I had been appending a ?key=[gmail application client id] parameter to the POST googleapis.com/upload/gmail/v1/users/userId/messages/send url. I'm not sure why I did that originally, but as of a few days ago it began causing a 403 forbidden error for some of the linked gmail accounts. Problem solved!
404 Error
Good afternoon,
i want to use the Billing API to get Information About my Costs...
I tried to run the sample from GitHub https://github.com/Azure-Samples/billing-dotnet-usage-api.
I did all steps which are described in the read me but i get a 404 Error when i call it.
I checked already if there is a typo in the Subscription ID but it is not.
Thank you David
URL: https://pilot-payflowpro.paypal.com
Until 12 April 2017 I had no problem but as of 13 April I failed to create a secure token.
There were no changes to the code nor to the account settings (no change in password, no "allowed IP addresses, ...").
The same code using paypal production accounts still works.
Apart from the TLS 1.2 and HTTP/1.1 upgrade I don't know about any changes on the PayPal server side.
Anyone having similar problems?
After some more digging I decided to contact PayPal technical support and I eventually (after 5 weeks) got this reply:
"There was a batch a few months ago that disabled Test accounts that hadn't been in use for a while.
They can be re-enabled only from our side...
Apologies for the inconveniences."
They kindly re-enabled our accounts and all was fine again.
I'm trying to sign up for DFP small business service with an enabled AdSense account.
After submitting with the apply form, I am still unable to log into DFP account and keep seeing this error:
Unauthorized Access
We apologize for the inconvenience, but you are not authorized to
visit this page. If you believe this is an error, please contact your
account manager.
I received nothing in my email (activation link or any message about it) and I cannot log in to check any information or settings about my account.
I also followed this answer to solve the issue but nothing really worked.
Is there anything I can do other than contact google and wait a long time to get useful response?
In order to use DFP, you need to sign an agreement with Google. DFP is not for free. You should contact Google.
I'm using Azure Active Directory (AD) to access ASP.NET MVC application. At the same time it works for some countries when doesn't work, for example, for US IP addresses, despite Region for AD has been set to United States. The error message below:
Sign in
Sorry, but we're having trouble signing you in.
Something went wrong.
Additional technical information:
Trace ID: a357d9ac-4253-485a-9d07-1f7f8e0d4ceb
Timestamp: 2014-03-26 08:34:39Z
ACS50000: There was an error issuing a token.
Did anyone has this issue or have any ideas? Thanks in advance!
After 5 days the problem was resolved automatically. Looks like it needs five days to sync AD to all countries. Before that it worked only for country, which application was created from in Azure Management Portal.