This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-12-09
Channels
- # adventofcode (197)
- # announcements (25)
- # aws (1)
- # babashka (21)
- # beginners (138)
- # calva (21)
- # cider (5)
- # clara (1)
- # clj-kondo (35)
- # clojure (97)
- # clojure-australia (4)
- # clojure-dev (37)
- # clojure-europe (100)
- # clojure-nl (2)
- # clojure-spec (7)
- # clojure-uk (36)
- # clojurescript (11)
- # conjure (15)
- # cursive (20)
- # datomic (12)
- # emacs (10)
- # events (2)
- # fulcro (83)
- # graalvm (14)
- # jobs (1)
- # jobs-discuss (27)
- # kaocha (75)
- # lambdaisland (21)
- # off-topic (27)
- # pedestal (5)
- # reitit (2)
- # reveal (20)
- # rewrite-clj (24)
- # sql (9)
- # tools-deps (37)
- # xtdb (93)
I’m trying to figure out whether I screwed up my SSL/HTTPS config somehow or whether the IT department providing the server did. If I make an HTTPS request to a Pedestal web service and I get an 1) empty response and 2) the Pedestal log show no request having been made, then I guess it’s safe to assume that my IT department is blocking port 443, right?
@simongray double check ::http/host "0.0.0.0"
Thanks. That was actually the first surprising issue I had, but I solved it yesterday 🙂
I think I narrowed this issue down to having to do with a failing SSL handshake, probably because I imported some Let’s Encrypt certificates into a java keystore in a wrong way..? To be fair, for some inexplicable reason using a certificate in Pedestal/Java applications requires using a keystore file and importing the certificates into a keystore, apparently requires first converting them into a separate pkcs12 file… it’s all very convoluted and hard to understand :P