# Challenge file not created during update **URL:** \ **Category:** Help\ **Created:** [February 29, 2020, 8:16pm UTC](https://community.letsencrypt.org/t/challenge-file-not-created-during-update/114636 "2020-02-29T20:16:12Z")\ **Posts on this page:** 3\ **Page:** 3
**Author:** ![9peppe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/9peppe/32/31596_2.png) [@9peppe](https://community.letsencrypt.org/u/9peppe)\ **Post date:** [March 1, 2020, 9:55pm UTC](https://community.letsencrypt.org/t/challenge-file-not-created-during-update/114636/41 "2020-03-01T21:55:24Z")
Yeah, of course, but it needs to be an explicit choice of the website operator, not a default I’m comfortable telling people to just activate 🙂 ---
**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\ **Post date:** [March 2, 2020, 3:42am UTC](https://community.letsencrypt.org/t/challenge-file-not-created-during-update/114636/42 "2020-03-02T03:42:31Z")
> [@Osiris](#): > > Hm, that’s strange. It seems `--debug-challenges` doesn’t work when using `renew` … Not sure if that’s intented or a bug. I believe it's the same behavior as how `--manual` can't work with `renew`, because `renew` is strictly noninteractive. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [April 1, 2020, 3:42am UTC](https://community.letsencrypt.org/t/challenge-file-not-created-during-update/114636/43 "2020-04-01T03:42:33Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed. [Previous page](https://community.letsencrypt.org/t/challenge-file-not-created-during-update/114636.md?page=2)