# Can I change the /.well-known/acme-challenge path?

**URL:** <https://community.letsencrypt.org/t/can-i-change-the-well-known-acme-challenge-path/13590>\
**Category:** Uncategorized\
**Created:** [April 1, 2016, 5:50pm UTC](https://community.letsencrypt.org/t/can-i-change-the-well-known-acme-challenge-path/13590 "2016-04-01T17:50:22Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![volkan\_unsal](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/volkan_unsal/32/6417_2.png) [@volkan\_unsal](https://community.letsencrypt.org/u/volkan_unsal)\
**Post date:** [April 1, 2016, 5:50pm UTC](https://community.letsencrypt.org/t/can-i-change-the-well-known-acme-challenge-path/13590/1 "2016-04-01T17:50:22Z")

</div>

The Rails app I’m using doesn’t support dots at the base of the root. I’d like to change the location of this path. Is it possible?

---

<div class="post-metadata">

**Author:** ![nicoo](https://avatars.discourse-cdn.com/v4/letter/n/0ea827/32.png) [@nicoo](https://community.letsencrypt.org/u/nicoo)\
**Post date:** [April 1, 2016, 5:52pm UTC](https://community.letsencrypt.org/t/can-i-change-the-well-known-acme-challenge-path/13590/2 "2016-04-01T17:52:36Z")

</div>

No, you cannot.

However, you can serve the challenges from whatever web frontend/reverse proxy you are using (likely something like Nginx or Apache).

Otherwise, you can use an alternative auth method, like `dns-01`.

---

<div class="post-metadata">

**Author:** ![jsha](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jsha/32/12_2.png) [@jsha](https://community.letsencrypt.org/u/jsha)\
**Post date:** [April 1, 2016, 6:16pm UTC](https://community.letsencrypt.org/t/can-i-change-the-well-known-acme-challenge-path/13590/3 "2016-04-01T18:16:03Z")

</div>

@nicoo is correct. The .well-known name was chosen in part because it’s a little “special,” so it’s less likely for web apps to accidentally be configured with arbitrary uploads from untrusted parties there. See [https://tools.ietf.org/html/rfc5785](https://tools.ietf.org/html/rfc5785).

---

<div class="post-metadata">

**Author:** ![volkan\_unsal](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/volkan_unsal/32/6417_2.png) [@volkan\_unsal](https://community.letsencrypt.org/u/volkan_unsal)\
**Post date:** [April 1, 2016, 6:26pm UTC](https://community.letsencrypt.org/t/can-i-change-the-well-known-acme-challenge-path/13590/4 "2016-04-01T18:26:27Z")

</div>

Can you link me to an example of how to use `dns-01` as part of the manual setup? Very much appreciate it.

---

<div class="post-metadata">

**Author:** ![nicoo](https://avatars.discourse-cdn.com/v4/letter/n/0ea827/32.png) [@nicoo](https://community.letsencrypt.org/u/nicoo)\
**Post date:** [April 1, 2016, 7:00pm UTC](https://community.letsencrypt.org/t/can-i-change-the-well-known-acme-challenge-path/13590/5 "2016-04-01T19:00:47Z")

</div>

Which ACME client are you using?  
The official Let’s Encrypt client doesn’t support `dns-01` … [yet](https://github.com/letsencrypt/letsencrypt/pull/2061).

---

<div class="post-metadata">

**Author:** ![Iodok](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/iodok/32/1273_2.png) [@Iodok](https://community.letsencrypt.org/u/Iodok)\
**Post date:** [April 2, 2016, 8:47am UTC](https://community.letsencrypt.org/t/can-i-change-the-well-known-acme-challenge-path/13590/6 "2016-04-02T08:47:11Z")

</div>

Can’t you just link the path to [s.th](http://s.th). valuable for the Rails-app?

just my 2 cents

Iodok

---

<div class="post-metadata">

**Author:** ![rmalenko](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rmalenko/32/7898_2.png) [@rmalenko](https://community.letsencrypt.org/u/rmalenko)\
**Post date:** [June 30, 2016, 2:11pm UTC](https://community.letsencrypt.org/t/can-i-change-the-well-known-acme-challenge-path/13590/7 "2016-06-30T14:11:32Z")

</div>

Nginx’s server, usually protect to show all files and folder started from dot i.e. /.well-known/ will not work in this case.  
By this reason I think it is a good idea change to /well-known/
