# Getting around apache configs with 443 redirects

**URL:** <https://community.letsencrypt.org/t/getting-around-apache-configs-with-443-redirects/26846>\
**Category:** Help\
**Created:** [February 1, 2017, 1:58am UTC](https://community.letsencrypt.org/t/getting-around-apache-configs-with-443-redirects/26846 "2017-02-01T01:58:45Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![aaplmike](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/aaplmike/32/7600_2.png) [@aaplmike](https://community.letsencrypt.org/u/aaplmike)\
**Post date:** [February 1, 2017, 1:58am UTC](https://community.letsencrypt.org/t/getting-around-apache-configs-with-443-redirects/26846/1 "2017-02-01T01:58:45Z")

</div>

Hello.

All the domains we have are set up with redirects from :80 to :443. This is causing issue with renew:

```
<VirtualHost *:80>
    ServerName myhost.mydomain.com
    Redirect / https://myhost.mydomain.com
</VirtualHost>

<VirtualHost *:443>
  ...
</VirtualHost>

```

What I’d prefer to do is have maybe a different, shared directory outside of our main web data directory where LE would save it’s challenge. Does anyone have a workaround for this? I was thinking maybe as Alias directive?

---

<div class="post-metadata">

**Author:** ![jmorahan](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jmorahan/32/1873_2.png) [@jmorahan](https://community.letsencrypt.org/u/jmorahan)\
**Post date:** [February 1, 2017, 5:09am UTC](https://community.letsencrypt.org/t/getting-around-apache-configs-with-443-redirects/26846/2 "2017-02-01T05:09:33Z")

</div>

Redirects should normally work fine. You do need the slash at the end though, if you’re using the webroot method:

```
     Redirect / https://myhost.mydomain.com/
```

---

<div class="post-metadata">

**Author:** ![serverco](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/serverco/32/4251_2.png) [@serverco](https://community.letsencrypt.org/u/serverco)\
**Post date:** [February 1, 2017, 7:23am UTC](https://community.letsencrypt.org/t/getting-around-apache-configs-with-443-redirects/26846/3 "2017-02-01T07:23:30Z")

</div>

You can use an Alias for redirecting all challenges to a single location, yes. Something like …

```auto
Alias /.well-known/acme-challenge /your/challenge/directory
<Directory /your/challenge/directory>
	Require all granted
</Directory>

```

---

<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:** [March 3, 2017, 7:25am UTC](https://community.letsencrypt.org/t/getting-around-apache-configs-with-443-redirects/26846/4 "2017-03-03T07:25:57Z")

</div>

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