I feel odd replying to my own question... but before any kind people spend time helping:
I have resolved the issue. Somewhere along the way my apache2.conf file had the "IncludeOptional sites-enabled/*.conf" attribute commented out. A good lesson in checking the basics before requesting help... Thanks, James On Wed, May 17, 2017 at 2:53 PM, James Kerwin <jkerwin2...@gmail.com> wrote: > Hello all, > > Firstly, I'm a bit of a beginner so please be as patient as you can. > > I set up a practice website that sent data collected from a form to a > database. It worked. > > I then tried to install an SSL certificate for better security. > Unfortunately it didn't work (when typing URL my browser couldn't open the > page). I then discovered certbot and used this to attempt to install an SSL > certificate. It doesn't work now. As I didn't make the changes myself I > can't go back and undo them. To be specific, when I type my domain into the > browser it shows me this (in Chrome): > > "This site can't provide a secure connection" and "ERR_SSL_PROTOCOL_ERROR". > > Would somebody be willing to help? > > So far I have this from openssl (sorry if it formats terribly, like I > said; beginner): > > james@localhost:~$ openssl s_client -connect www.mydomain.com:443 > CONNECTED(00000003) > 140444419827352:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown > protocol:s23_clnt.c:794: > --- > no peer certificate available > --- > No client certificate CA names sent > --- > SSL handshake has read 7 bytes and written 305 bytes > --- > New, (NONE), Cipher is (NONE) > Secure Renegotiation IS NOT supported > Compression: NONE > Expansion: NONE > No ALPN negotiated > SSL-Session: > Protocol : TLSv1.2 > Cipher : 0000 > Session-ID: > Session-ID-ctx: > Master-Key: > Key-Arg : None > PSK identity: None > PSK identity hint: None > SRP username: None > Start Time: 1495028612 > Timeout : 300 (sec) > Verify return code: 0 (ok) > > I'm running Ubuntu 16.04 and Apache 2.4.18 (Ubuntu). > > If anybody could help me I would really appreciate it. I only did the SSL > stuff this morning and I have heard it could take up to 24 hours to work, > but still... > > Thanks, > James > > PS: If there is a more suitable list I can contact, please let me know. > >
