# SSL not working correctly on AWS EC2

**URL:** https://community.letsencrypt.org/t/ssl-not-working-correctly-on-aws-ec2/70143
**Category:** Help
**Created:** [August 22, 2018, 8:36am UTC](https://community.letsencrypt.org/t/ssl-not-working-correctly-on-aws-ec2/70143 "2018-08-22T08:36:51Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![nikitantra](https://avatars.discourse-cdn.com/v4/letter/n/d6d6ee/32.png) [@nikitantra](https://community.letsencrypt.org/u/nikitantra)
#### Post date: [August 22, 2018, 8:36am UTC](https://community.letsencrypt.org/t/ssl-not-working-correctly-on-aws-ec2/70143/1 "2018-08-22T08:36:52Z")

</div>

Hello,  
I can really use some help! First of all, thank you for creating this amazing product! The internet needs people like you! I just got the SSL installed and it looks like its almost working:) For one the SSL does not appear as secure when using chrome. [https://i.imgur.com/MC6otT6.png](https://i.imgur.com/MC6otT6.png) and for some reason, it looks like all the CSS and Js is not loading. When I browse using regular [http://caralbert.com](http://caralbert.com) it works fine. My ssl.config has:  
SSLCertificateFile /etc/letsencrypt/live/caralbert.com/fullchain.pem  
SSLCertificateKeyFile /etc/letsencrypt/live/caralbert.com/privkey.pem  
SSLCertificateChainFile /etc/letsencrypt/live/caralbert.com/chain.pem

Not sure what am I missing ☹

My domain is:  
[https://caralbert.com](https://caralbert.com)  
I ran this command:  
sudo ./certbot-auto --debug -v --server [https://acme-v01.api.letsencrypt.org/directory](https://acme-v01.api.letsencrypt.org/directory) certonly -d [caralbert.com](http://caralbert.com)

It produced this output:  
Congratulations! Your certificate and chain have been saved at:  
/etc/letsencrypt/live/caralbert.com/fullchain.pem

My web server is (include version):  
Apache/2.4.33 (Amazon)

The operating system my web server runs on is (include version):  
Linux 14.62-65.117.amzn1.x86\_64

My hosting provider, if applicable, is:  
AWS

I can login to a root shell on my machine (yes or no, or I don’t know):  
YES

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):  
NO

---

<div class="post-metadata">

### Author: ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)
#### Post date: [August 22, 2018, 8:40am UTC](https://community.letsencrypt.org/t/ssl-not-working-correctly-on-aws-ec2/70143/2 "2018-08-22T08:40:55Z")

</div>

> [@nikitantra](#):
>
> certonly

Certonly will not install the cert.  
It will only get the cert.  
Look at:  
`sudo ./certbot-auto certificates`  
and you should see the cert.

---

<div class="post-metadata">

### Author: ![nikitantra](https://avatars.discourse-cdn.com/v4/letter/n/d6d6ee/32.png) [@nikitantra](https://community.letsencrypt.org/u/nikitantra)
#### Post date: [August 22, 2018, 8:50am UTC](https://community.letsencrypt.org/t/ssl-not-working-correctly-on-aws-ec2/70143/3 "2018-08-22T08:50:08Z")

</div>

Thank you for replying so quickly. Here’s the output I am getting:

Found the following certs:  
Certificate Name: [caralbert.com](http://caralbert.com)  
Domains: [caralbert.com](http://caralbert.com)  
Expiry Date: 2018-11-20 05:53:52+00:00 (VALID: 89 days)  
Certificate Path: /etc/letsencrypt/live/caralbert.com/fullchain.pem  
Private Key Path: /etc/letsencrypt/live/caralbert.com/privkey.pem

---

<div class="post-metadata">

### Author: ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)
#### Post date: [August 22, 2018, 9:41am UTC](https://community.letsencrypt.org/t/ssl-not-working-correctly-on-aws-ec2/70143/4 "2018-08-22T09:41:22Z")

</div>

Hi @nikitantra

> [@nikitantra](#):
>
> Certificate Name: [caralbert.com](http://caralbert.com)

your certificate is good and is already installed. So this part is done.

But there [https://caralbert.com/](https://caralbert.com/) are mixed content warnings. So the page loads content via http, not https.

Use FireFox or Chrome, Ctrl + Shift + I, then open the console. There you see a lot of mixed content warnings:

http :// caralbert . com / media/main-slider/1.jpg

Change them to https.

---

<div class="post-metadata">

### Author: ![nikitantra](https://avatars.discourse-cdn.com/v4/letter/n/d6d6ee/32.png) [@nikitantra](https://community.letsencrypt.org/u/nikitantra)
#### Post date: [August 22, 2018, 5:34pm UTC](https://community.letsencrypt.org/t/ssl-not-working-correctly-on-aws-ec2/70143/5 "2018-08-22T17:34:01Z")

</div>

Yep, looks like its all working now! thank you very much!

---

<div class="post-metadata">

### Author: ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)
#### Post date: [September 21, 2018, 5:34pm UTC](https://community.letsencrypt.org/t/ssl-not-working-correctly-on-aws-ec2/70143/6 "2018-09-21T17:34:02Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
