I signed a new certificate which listed the FQDN.  However, I still had the same error. After reading this, https://github.com/spesmilo/electrum/issues/1782, I realized that my laptop and phone thin wallets had connected to my server when I had my original SSL certificate in which I had filled out all the fields.  I had deleted this one when I got too much spam from bots scraping my e-mail off the certificate.  Since the original certificate was in my thin clients ~/.electrum/certs as trusted, my server was either flagged as MITM'd or my thin client tried to use the incorrect certificate, so my server refused the connection.  After deleting the trusted certificates, I have connected via SSL on both thin clients now.

On another topic, with regards to bootstrapping speed, my online instructor stated that VFS is much faster than ext4.  So, I am considering reformatting my 4TB bitcoind HDD and 0.5TB  electrumX SSD, and lowering bitcoind's dbcache from the current setting of 3GB.  Bitcoind uses 10% of my 20GB of RAM after bootstrapping.  I welcome any resource allocation suggestions.