In short, everything looks like it should be working, but it is not. On top of that, all the other certificates on my host (using letsencrypt as well) are also not working.

I have tried several things I found online, including changing the permissions on /etc/letsencrypt/live and archive.

Perhaps the error message in FireFox is pertinent? "An error occurred during a connection to www.bancsdegolf.com. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG "

That looks strange to me. Can you re-run the command as root or with sudo - that will provide a lot more detail.

I wonder if you have orphaned Apache processes sitting around (that use a stale config). This can be checked by stopping Apache and making sure nothing is still listening on 443 while Apache is stopped.

I’m kinda stumped, it should be working from the basic things we have checked.

Rudy’s idea about NAT is really the only other thing that I’ve seen cause this kind of problem, but since you’re using EC2, I don’t think there’s any to easily screw your NAT up this way. To confirm that the problem isn’t NAT:

If you are willing to look at it I seriously would be willing to share the whole thing through a Google Drive link so I can remove it later, because I am really stuck. I assume that would be a tarball of /etc/apache2/sites-available/ ?

It’s all symlinks in the sites-enabled directory, and I can’t figure out how to tar them (I tried the -h flag). I added SSLEngine On in the bancsdegolf-com-le-ssl.conf to no avail. Also the two other lines you just sent me.