TLS handshake error, LetsEncrypt host not configured

Dear,

Today I was testing the Docker-Compose based SCIM integration.

When running the container, I'm receiving TLS handshake errors:
# scim_1 | redicrypt: getting cert for key redicrypt/my.domain.com
# scim_1 | 2018/11/21 15:59:35 http: TLS handshake error from 1.2.3.4:42748: acme/autocert: host not configured

DNS = OK worldwide.
Incoming ports HTTP and HTTPS are open and are properly mapped to the container.
Outgoing no port is blocked. (yet)

How can we further troubleshoot and debug this issue please?

Thanks,
B.


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Ubuntu 18.04 LTS
Sync Type: Not Provided

Comments

  • Dear,

    Today I was testing the Docker-Compose based SCIM integration.

    When running the container, I'm receiving TLS handshake errors:
    # scim_1 | redicrypt: getting cert for key redicrypt/my.domain.com
    # scim_1 | 2018/11/21 15:59:35 http: TLS handshake error from 1.2.3.4:42748: acme/autocert: host not configured

    DNS = OK worldwide.
    Incoming ports HTTP and HTTPS are open and are properly mapped to the container.
    Outgoing no port is blocked. (yet)

    How can we further troubleshoot and debug this issue?

    Thanks,
    B.

  • cohixcohix

    Team Member

    @burn,

    It looks to me like the request coming into the SCIM bridge is not being made to the DNS address, but rather the IP address. All requests to the SCIM bridge should be to https://my.domain.com, and not 1.2.3.4.

    If you're using a load balancer or reverse proxy, ensure that TLS is not being terminated at that level before being redirected to the container.

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file