Skip to content
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

Registry is down - npm.open-registry.dev let's encrypt certificate expired yesterday #45

Open
reimertz opened this issue Jul 30, 2020 · 3 comments

Comments

@reimertz
Copy link

No description provided.

@SamMousa
Copy link

SamMousa commented Aug 6, 2020

@victorb this is quite a big one so I'm being rude and just pinging you; hope you don't mind.

@victorb
Copy link
Member

victorb commented Aug 6, 2020

Thanks, been unavailable lately but just now starting getting this to work again. Thanks for the ping! :)

@victorb
Copy link
Member

victorb commented Aug 6, 2020

So, things are back to normal (issue ended up being that old certificates were being used to connect to Let's Encrypt from Caddy, so the certification renewal didn't work [and alerts were missing in case this happened, working on adding that], so we ended up with old, expired certificates).

However, seems the NPM Inc registry is having some issues themselves as well, as some tarballs are returning 404 intermittently, so if the package hasn't been cached in open-registry since before, you'll receive the same error. Trying to run the test suite now but the NPM Inc issues are not really helping.

Will keep this issue open until I see that everything is 100% working again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants