Hi all, for 3-4 years I had a domain SSL-secured on my server running Ubuntu 14.04. Recently I wiped it and started with a fresh install of Ubuntu 16.04. If I use 000-default.conf and simply have it do HTTP on port 80 there are no problems; but when I try configuring default-ssl.conf with the SSL certificates I got from GoDaddy and my private key file, no joy whatsoever. I’ve talked to several IT experts about my problem, but no one seems to be able to help me out. Anyone ever have a similar problem in 16.04. Nothing very exciting in terms of error logs. At least not that I can see. Again, we are talking about a system that worked fine in 14.04 with SSL; only when I moved in a fresh install to 16.04 did it stop working. Yes, I chose a2ensite, did a2enmod SSL, restarted apache2, am sure port 443 is opened in UFW, etc. But no go. Anyone been here and done this?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
hi. no, it never worked. and i did exactly what i’d done in version 14.04 of Ubuntu, which had only 1 IP address, by the way. But it used to work just fine, before trying the same trick with Ubuntu 16.04. So I had to give up in the end. Are you trying to do the same thing? Have you succeeded in doing the same thing with Ubuntu 16.04?
I did generate the .csr and related .key file, inserted it in my rekey request from my certificate provider, got back a zip with two .crt files in it, that I put into a …/ssl/certs directory and put my privatekey.key file in the …/ssl/private directory. Used default-ssl.conf and enabled module with a2enmod ssl, restarted apache2, I even tried fiddling with 000-default.conf in sites-available, since I have no problem with that, thinking I could also include the VirtualHost *:443 directive along with the VirtualHost *:80 that does work fine. Really a puzzle. Thanks for your help with this. If you or anyone else happens to have an idea what is going wrong, please contact me. Again, I had SSL working just fine on same OS (but version 14.04) and same server for several years. But when I wiped it and reinstalled a fresh install of 16.04, only HTTP works. Not SSL on same domain.
If you’ve already reissued the certificate, then we’d need to take a look at your configuration files for the domain in question. If you’re not having issues with accessing your domain on port 80, then we’ll skip that file and take a look at the VirtualHost block that handles port 443.
If you can copy and paste that in to a code block as a reply, I’ll be more than happy to take a look. If needed, you can change the domain name if you prefer not to post that – just use domain.com or any other filler.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.