Kamal 2 - Deploy, ERR_SSL_PROTOCOL_ERROR

rubyonrails-talk
1

I’ve built a really basic project in Rails8 (Few basic CRUD style controllers). I’m then using Kamal 2 to deploy it to an EC2 Instance (Ubuntu).

Deployment seems to be working but when accessing the URL, I get

Error code: SSL_ERROR_INTERNAL_ERROR_ALERT

In the browser (Same in Firefox and Chrome).

I can get to the /up page (As doesnt enforce ssl). So the project seems to be deployed correctly.

Anyone had this issue, or suggest any further debugging techniques?

2

I’ve resolved this now. It was a DNS Problem, it took a while to figure out based on the result but I remembered you need DNS in place for all domains for LetsEncrypt to succeed!

3 Likes
6

Good to know that you found solution. I am leaving a guide for future readers as this is one of the most common errors faaced by site owners.

The SSL_ERROR_INTERNAL_ERROR_ALERT in Firefox usually indicates that something went wrong during the SSL/TLS handshake between your browser and the server—essentially, the server ran into an unexpected issue and terminated the connection.

Few tips to help you troubleshoot it:

  1. Check the SSL Certificate: Make sure your site’s certificate is valid, not expired, and correctly installed. You can use tools like SSL Labs to test it.
  2. Server Configuration: If you’re using a custom server setup (like Caddy, Apache, or Nginx), check that the SSL/TLS settings are correct and compatible with modern browsers.
  3. Browser Extensions or Firewall: Sometimes extensions or antivirus software can interfere with SSL handshakes—try disabling them temporarily.
  4. Force HTTPS: Ensure your site is properly redirecting HTTP to HTTPS without causing a redirect loop.

For people with no technical knowledge - certera(dot)com/blog/how-to-fix-err-ssl-protocol-error-in-chrome/