Dejan Kovacevic

No, I gave up :(

when I run: `curl -ikv https://safe-reef-88300.herokuapp.com:443/bots/status` I am getting: ``` * Trying 54.225.154.132... * Connected to safe-reef-88300.herokuapp.com (54.225.154.132) port 443 (#0) * TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 * Server certificate:...

Thanks. What is the output when you start the service? You should see something like this: ``` INFO [2017-05-13 20:59:02,277] org.eclipse.jetty.util.log: Logging initialized @4073ms INFO [2017-05-13 20:59:02,400] io.dropwizard.server.DefaultServerFactory: Registering jersey...

In your logs: ``` Starting process with command java $JAVA_OPTS -Ddw.server.applicationConnectors[1].port=9677 -jar target/echo.jar server conf/echo.yaml ``` This means you are overriding your https port 443 specified in yaml with 9677...

I see. OK so it's clear that Heroku is not routing traffic from 443 to 9677 correctly. I will try to investigate bot deployments to Heroku more on Monday. Meanwhile...

One more thing. Can you verify that you provided Dev Bot with the correct string from pubkey.pem? You can always update your pubkey by running: `update bot ` and then...

I think this is fine: If you try adding _https_ like: `curl -ikv https://localhost:4434/bots/status` You should see something like: ``` * Trying 127.0.0.1... * Connected to localhost (127.0.0.1) port 4434...

What is your base_url for your bot? What is your bot name?

Thanks. I think Wire Backend does not default to 443 for https. Can you change your base url to: `https://safe-reef-88300.herokuapp.com:443` This should fix the glitch with the BE

Yes. If I try to add your bot to a conversation (Chrome console): `wire.app.repository.bot.add_bot("testbridge")` I get: ``` code: 502 label: "bad-gateway "message: "The upstream service returned an invalid response." ```...