-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting consistent 503 Server Error: Service Unavailable #51
Comments
Hi, I am receiving the same error. Looks like the NVD API is having an issue at the moment. Lets keep this issue open until we can confirm its been resolved. I recommend emailing the NVD team and letting them know the issue is occurring. |
Thanks for confirming the error!
I have emailed ***@***.*** about the issue.
PGP Fingerprint: 741AE17E58790B4404D74D9C943C07713F7743CD
…________________________________
From: vehemont ***@***.***>
Sent: Saturday, November 23, 2024 9:53 AM
To: vehemont/nvdlib ***@***.***>
Cc: johnlabuyfoy1024 ***@***.***>; Author ***@***.***>
Subject: Re: [vehemont/nvdlib] Getting consistent 503 Server Error: Service Unavailable (Issue #51)
Hi,
I am receiving the same error. Looks like the NVD API is having an issue at the moment. Lets keep this issue open until we can confirm its been resolved. I recommend emailing the NVD team and letting them know the issue is occurring.
—
Reply to this email directly, view it on GitHub<#51 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACCWEOM5UMMSFM4DKPJPEDT2CCJE3AVCNFSM6AAAAABSLEVMROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJVGUYDIMRXG4>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
same error |
Been having this same issue lately. I did realize, could be a coincidence but I had just taken the time to upgrade my Mac from MacOS 14 to 15, and around that point is when I started getting issues. I noticed a lot of my errors were tied into SSL libraries, and so have test pulling down CVE's without encryption. It's not perfect, it's probably getting 90% of the pages, and 10% are failures. But it's a heck of a lot better that anything else I'd tried over the last week. I'll obviously have to redownload once I can do so with TLS.SSL But just wanted to share my observation. I also sent an email the NVD team at NIST |
FYI. Since November 21, 2024 - I've been receiving the following error message:
https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2014-2120
Has anyone else been receiving this error message?
The text was updated successfully, but these errors were encountered: