search

OpenSourceOrg / api

Light API based on the licenses spec
https://api.opensource.org/licenses/
GNU Affero General Public License v3.0
94 stars 18 forks source link

I/O error when accessing the API #20

Open goneall opened 1 year ago

goneall commented 1 year ago

Recently, we started getting I/O errors when accessing the API.

The specific error returned is java.security.cert.CertificateException: No subject alternative DNS name matching api.opensource.org found.

This will impact the SPDX license list's ability to mark the OSI URL's as active.

See the LicenseListPublisher PR 155 comments for more context.

debbryant commented 1 year ago

Unclear if anyone responded to your email, notifying stakeholders by CC if this has been missed; we recently did a major web site migration and will check to see if something was broken. Apologies for the extra traffic if this has already been resolved.

Deb Bryant

On Feb 16, 2023, at 1:50 PM, goneall @.***> wrote:

Recently, we started getting I/O errors when accessing the API.

The specific error returned is java.security.cert.CertificateException: No subject alternative DNS name matching api.opensource.org found.

This will impact the SPDX license list's ability to mark the OSI URL's as active.

See the LicenseListPublisher PR 155 https://github.com/spdx/LicenseListPublisher/pull/155 comments for more context.

— Reply to this email directly, view it on GitHub https://github.com/OpenSourceOrg/api/issues/20, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABVN44T4TOJLZH6LBO2HEELWXZZG5ANCNFSM6AAAAAAU6RHQOQ. You are receiving this because you are subscribed to this thread.

smaffulli commented 1 year ago

@goneall this issue was due to the DNS switch when we moved the website to a new host. It should be resolved now, API has its own, proper DNS record now. Can you please confirm?

goneall commented 1 year ago

@smaffulli It has improved but not completely fixed. I can now successfully access the API from my local machine, but when I run it in a GitHub action, I'm still getting a failure. I recall we had this issue before - I think there was a firewall blocking the GitHub based access to the API.