Errors when trying to run SSM with auto TLS

[Shaltz]

We have been using SSM for quite a while now, very happy with it, worked flawlessly.
Deployed a new instance, updated docker, pulled the latest version from git, update docker-compose,
and for the life of me, I can't get it to work anymore, with TLS and HTTP redirect...

here is the error I get :

batman@batcave:~/tools  $ docker logs supersecret

   ____    __
  / __/___/ /  ___
 / _// __/ _ \/ _ \
/___/\__/_//_/\___/ v3.3.10-dev
High performance, minimalist Go web framework
https://echo.labstack.com
____________________________________O/_______
                                    O\

   ____    __
  / __/___/ /  ___
 / _// __/ _ \/ _ \
/___/\__/_//_/\___/ v3.3.10-dev
High performance, minimalist Go web framework
https://echo.labstack.com
____________________________________O/_______
                                    O\
{"time":"2021-06-23T15:15:31.781414677Z","level":"FATAL","prefix":"echo","file":"main.go","line":"48","message":"listen tcp: address 443: missing port in address"}
2021/06/23 15:15:31 [INFO] HTTP Binding Address: 80
2021/06/23 15:15:31 [INFO] HTTPS Binding Address: 443
2021/06/23 15:15:31 [INFO] HTTPS Redirect enabled: true
2021/06/23 15:15:31 [INFO] TLS Auto Domain: secret.mydomain.io
2021/06/23 15:15:31 [INFO] TLS Cert Filepath: 
2021/06/23 15:15:31 [INFO] TLS Cert Key Filepath: 

and here is the docker-compose file:

version: '3.2'

services:
  vault:
    image: vault:latest
    container_name: vault
    environment:
      VAULT_DEV_ROOT_TOKEN_ID: supersecret
    cap_add:
      - IPC_LOCK
    expose:
      - 8200

  supersecret:
    build: ./
    image: algolia/supersecretmessage:latest
    container_name: supersecret
    environment:
      VAULT_ADDR: http://vault:8200
      VAULT_TOKEN: supersecret
      SUPERSECRETMESSAGE_HTTP_BINDING_ADDRESS: 80
      SUPERSECRETMESSAGE_HTTPS_BINDING_ADDRESS: 443
      SUPERSECRETMESSAGE_HTTPS_REDIRECT_ENABLED: "true"
      SUPERSECRETMESSAGE_TLS_AUTO_DOMAIN: "secret.mydomain.io"
    ports:
      - "8082:8082"
    depends_on:
      - vault

SuperSecret container is not running

any idea ?

thanks in advance :)

[Shaltz]

I found the issue... The errors were coming from the configuration examples in the README
I've created a pull request for it => #58

Now the containers are runnning...

[eranchetz]

There is a difference between the README examples which are in pure bash and your examples, they are in docker-compose.yml style