Kamal Proxy logs: "level":"INFO","msg":"http: TLS handshake error from <myip>:: no server name provided"

[orbanbotond]

Hi Guys,

I have this deploy.yml file:

# Deploy to these servers.
servers:
  - <ip of the cloud server>

proxy: 
  ssl: true
  host: <ip of the cloud server, same as above>
  app_port: 3000

Then as I turned the ssl to true, the web app no longer responds, I checked the kamal proxy log:
"level":"INFO","msg":"http: TLS handshake error from :47524: no server name provided"

Any solutions?
thx in advance

[orbanbotond]

As I am examining further TLS is higly tight to a domain. This could be it:
"A domain validated certificate (DV) is an [X.509]of the applicant is validated by proving some control over a [DNS domain]"

[elitebyte]

Did you find a solution to this? Stuck using an AWS Load balancer and EC2 instances

[ps-ruby]

I am also facing this issue. I am using Kamal to deploy multiple instances for different subdomains, and it is working for one, another is throwing errors.

http: TLS handshake error from MYIP: no server name provided
http: TLS handshake error from MYIP tls: client offered only unsupported versions: [301]
http: TLS handshake error from MYIP tls: unsupported SSLv2 handshake received

@orbanbotond Were you able to fix this issue?

[egor-khanko]

@orbanbotond Hey! How were you able to resolve this? Do you know the root cause?

[egor-khanko]

Was resolved in #170