# Tried to use --expand; all I got was an error message

**URL:** <https://community.letsencrypt.org/t/tried-to-use-expand-all-i-got-was-an-error-message/118754>\
**Category:** Help\
**Created:** [April 7, 2020, 7:35pm UTC](https://community.letsencrypt.org/t/tried-to-use-expand-all-i-got-was-an-error-message/118754 "2020-04-07T19:35:15Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![hbquikcomjamesl](https://avatars.discourse-cdn.com/v4/letter/h/a6a055/32.png) [@hbquikcomjamesl](https://community.letsencrypt.org/u/hbquikcomjamesl)\
**Post date:** [April 8, 2020, 12:23am UTC](https://community.letsencrypt.org/t/tried-to-use-expand-all-i-got-was-an-error-message/118754/6 "2020-04-08T00:23:28Z")

</div>

Oh, for heaven’s sake! 🤦‍♂️ I found the problem as I was in the process of building a reply to your last question.

I’d included both the non-SSL and SSL versions of the VirtualHost block in the new .conf file, but the SSL version was malformed (which makes me wonder why Apache tolerated it, but that’s neither here nor there): I left out the  
`Include /etc/letsencrypt/options-ssl-apache.conf`  
`SSLCertificateFile /<path>.pem`  
`SSLCertificateKeyFile /<path>.pem`  
and the `</IfModule>` at the end, after the `</VirtualHost>`!

I fixed that, and tried the command again, and this time it worked fine.

**THANKS!** 😀 😀 😀 👍 👍 👍

---

_[View the full topic](https://community.letsencrypt.org/t/tried-to-use-expand-all-i-got-was-an-error-message/118754)._