Timeline for How can I set let's encrypt certificates with Ansible?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 15, 2022 at 7:01 | history | edited | Bruce Becker | CC BY-SA 4.0 | jsonformat the error message from ansible |
| Jul 14, 2022 at 22:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jun 14, 2022 at 21:12 | comment | added | Tanuki | @Zeitounator yes, I was missing the /.well-known/acme-challenge/ and there were a couple of mistakes in my task. | |
| Jun 14, 2022 at 21:09 | answer | added | Tanuki | timeline score: 1 | |
| S Jun 4, 2022 at 9:25 | history | suggested | Zeitounator | CC BY-SA 4.0 | Syntax highlighting, long error layout and make title an actual question. |
| Jun 4, 2022 at 7:41 | review | Suggested edits | |||
| S Jun 4, 2022 at 9:25 | |||||
| Jun 4, 2022 at 7:36 | comment | added | Zeitounator | You are redirecting every singlle call on http to its https counterpart. A bit of a shortcut here but in a common default setup this basically can't work as let's encrypts needs access over unencrypted http to get the challenge files. Moreover, I don't see any configuration in nginx to allow acessing /.well-known/acme-challenge/* files (unless you already tested this works from you app folder....). In a typical let's encrypt setup, you allow accessing the /.well-known path (and all its subdirs) over http and redirect the rest to https. | |
| S Apr 30, 2022 at 19:06 | review | First questions | |||
| Apr 30, 2022 at 20:03 | |||||
| S Apr 30, 2022 at 19:06 | history | asked | Tanuki | CC BY-SA 4.0 |