Investigate setting up a reverse proxy or correctly configuring SSL certificates in fly.io

[MgenGlder]

Summary

• After playing around with dig and cURL in the shell, I came across this error when attempting to hit the https qualified url dearborncodingclub.com.

  curl: (35) LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to dearborncodingclub.com:443 

• This seems to indicate to me that something is going wrong with the TLS/SSL handshake when making a request. The hosted website is always configured to point to https (https://website-base-backend.fly.dev), so I assume it is an issue with routing requests between our hosting server and the custom domain provider.
• Fly.io has some promising documentation here around configuring DNS records and configuring SSL such that an external domain provider can successfully complete the handshake. I think we may need to set up some of this custom configuration to get things up and running.
• Notably, I think the issue might be around missing headers and the need of a proxy to do some request enrichment. I'll try to look at this as time permits this week, and when we meet this weekend.

cc/ @dXu23 @ctcarrier

[MgenGlder]

More information on creating and using a certificate in fly.io can be found here.

[MgenGlder]

I went ahead and followed one of the first steps: Adding a dearborncodingclub.com certificate to the fly.io system using the command fly certs dearborncodingclub.com.

The response 👇🏾

[MgenGlder]

That seems to have resolved it. I ran fly cert show dearborncodingclub.com and received the following successful response:

[MgenGlder]

Visiting https://dearborncodingclub.com seems to work now as well 🎉

[MgenGlder]

I wrote up an issue here around documenting our findings as I feel other people might eventually run into the same problems.

[MgenGlder]

We no longer need a reverse proxy and the website is now correctly hooked up to the host. Closing as completed now.