This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-07-06
Channels
- # aleph (1)
- # announcements (3)
- # asami (32)
- # aws (12)
- # babashka (6)
- # beginners (43)
- # calva (36)
- # cider (3)
- # clj-kondo (3)
- # cljs-dev (2)
- # clojars (6)
- # clojure (66)
- # clojure-europe (14)
- # clojure-uk (2)
- # clojurescript (12)
- # conjure (1)
- # core-async (27)
- # cursive (17)
- # data-science (9)
- # datahike (1)
- # datomic (28)
- # emacs (34)
- # events (1)
- # girouette (3)
- # jobs (1)
- # klipse (4)
- # lsp (26)
- # malli (5)
- # off-topic (38)
- # portal (1)
- # releases (1)
- # shadow-cljs (72)
- # sql (7)
- # tools-deps (5)
- # vim (9)
- # xtdb (18)
Hi everyone! Did the clojars cert recently expire? We were having some really funky errors when pulling deps, and noticed the site's cert is now giving us a nastygram
This is for http://status.clojars.org, which is a cname for http://clojars.statuspage.io, and the cert names don't match. Because of this, we recently changed the status link in the footer to link directly to the http://statuspage.io site. This won't impact dependency resolution at all.
For additional context, I started seeing these errors when spinning up our clojure project late last week, which i think are related (they had been working fine previously)
The first image isn't related to clojars; something in your setup is trying to load dependencies from http://repository.springsource.com over http instead of https, which lein will warn about. The second image looks like you have an incorrect dependency name or versions maybe? Certificate errors should present differently.
Ok cool, thanks @U06SGCEHJ appreciate the insight!