This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-09-22
Channels
- # admin-announcements (5)
- # aws (32)
- # beginners (2)
- # boot (51)
- # cider (33)
- # cljs-dev (4)
- # clojure (83)
- # clojure-berlin (11)
- # clojure-czech (23)
- # clojure-poland (3)
- # clojure-russia (51)
- # clojure-seattle (4)
- # clojure-sg (1)
- # clojure-uk (4)
- # clojurescript (48)
- # clojurex (1)
- # datomic (26)
- # devcards (10)
- # devops (12)
- # editors (9)
- # emacs (12)
- # events (1)
- # funcool (14)
- # hoplon (117)
- # immutant (1)
- # jobs (2)
- # ldnclj (32)
- # ldnproclodo (12)
- # om (51)
- # onyx (17)
- # reagent (11)
- # yada (4)
bhagany: localhost should works anyway
Today I have weird issue, my app was running but health-check was unhealthy
@tom: localhost may not work if your app is only listening on a single network interface, e.g. eth0 or if your app is running in a container. investigate which processes are listening on which ports with "sudo lsof -i"
@lowl4tency: you're right, of course
Funny thing is how redirects (say, from http to https) are considered an unhealthy app by the ELB health check.
First, I checked port is listened, second try to connect via telnet. third take a look on log-file
jaen: it's not funny, it's hurt
I've got ELB and S3 bucket with maintenance page, when ELB is not available I've got ssl error instead the page 😞