Question: NCBI Eutils error forwarding request
5
sklimek23 • 50 wrote:
I am having an issue connecting to the NCBI entrez eutils service. All my requests give the error message:
"error":"error forwarding request","api-key":"xxxxxxxxxx","type":"api-key", "status":"ok"
I am using the GET method to get the content of the url request. The thing is that my url requests where working fine the day before and I did not change anything in my code.
Would this be an issue with the NCBI website or something on my end? I do not know how or where to check the status of their serivces.
Edit by GenoMax: Redacted NCBI api-key posted in the question.
I guess it is the issue with the website as I am getting the same message when I tried 5 mins ago.
This is definitely a problem on NCBI's end. While it is likely to get corrected please put a ticket in using the support center.
Hi, do you know how to solve this problem? My website doesn't work now.
NCBI needs to fix whatever the problem is on their end. So please put a support ticket in at NCBI Help desk at link I posted above.
Not working again: https://eutils.ncbi.nlm.nih.gov/entrez/eutils/efetch.fcgi?db=nucleotide&id=KJ567057&rettype=gb&retmode=text
FYI, I am using Pubmed API for years now and today I got the same error. Found this post by googling the error, so maybe it's a problem on Pubmed's end?
ditto, had this issue with NIH Federal Reporter before, had to write several emails and it took a week to fix.
It might be the entire eutils serveice which are down, I'm developping some entrez-direct code into a pipeline, so first I suspected me being blocked for making a mistake (an esearch run with ~10 queries).
In terminal i receive a long
500 Internal Server Error, while in browser i receive aI get exactly the same error just from using a single query, so I think you may be right about eutils
I'm having this problem too. Definitely wasn't happening yesterday evening. I'm guessing the problem is with Pubmed.
In addition, I checked their ftp, there doesn't seem to be any new releases this month, so wouldn't expect it to be version-related.
the same situation happened to my website！！！！！！！！！！！！！！！！！！！