| 4 Oct 2022 |
 hexa | thanks! 😄 | 21:27:05 |
 m1cr0man | Alright done :) | 21:53:56 |
| 9 Oct 2022 |
|  @shapr:cofree.coffee joined the room. | 17:09:20 |
| @shapr:cofree.coffee | Hello, I'm having problems with acme. Here's my entire configuration.nix .
The error I get is:
Oct 08 23:32:51 surtr nginx[88563]: 2022/10/08 23:32:51 [error] 88563#88563: *3038 open() "/var/lib/acme/acme-challenge/.well-known/acme-challenge/QRZ9CmjhedoazA3YKZaevRybxjy415mk-1OPiYmP9IY" failed (2: No such file or directory), client: 23.178.112.208, server: scannedinavian.com, request: "GET /.well-known/acme-challenge/QRZ9CmjhedoazA3YKZaevRybxjy415mk-1OPiYmP9IY HTTP/1.1", host: "scannedinavian.com"
Any idea why it's trying to serve from /var/lib/acme when I've set the webroot to /var/www | 17:11:55 |
| @shapr:cofree.coffee | I found the problem! This line was setting the location incorrectly! | 20:44:55 |
| 15 Oct 2022 |
|  @tinybronca:sibnsk.net changed their display name from underpantsgnome to underpantsgnome!. | 00:30:21 |
| 17 Oct 2022 |
 Winter (she/her) | Is it normal for (a) the renewal timers to fire on each reboot, and (b) for it to not be daily, as specified in the timer file? | 03:02:39 |
| Winter (she/her) | Here's what I mean:
```
Until: Sun 2022-10-16 22:57:57 EDT; 26s ago
Trigger: Mon 2022-10-17 05:09:17 EDT; 6h left
``` | 03:02:54 |
| Winter (she/her) | (Sorry for the screwed up formatting, I'm trying to edit it but my client keeps crashing.) | 03:04:04 |
| Winter (she/her) | It just seems weird -- that certainly isn't daily, and I don't think the random skew thing has any impact on this? | 03:04:31 |
| Winter (she/her) | Unless it'll then fire at 05:09:17 every day | 03:04:44 |
| Winter (she/her) | (well, until the next reboot, I guess) | 03:04:50 |
| Winter (she/her) | Definitely weird how it fires every reboot no matter what, though. | 03:05:10 |
| Winter (she/her) | (Also wow that Until: ... is confusing wording, maybe I can ask what upstream thinks about changing it.) | 03:05:46 |
| Winter (she/her) | Upon another reboot: Until: Sun 2022-10-16 23:30:55 EDT; 1min 8s ago
Trigger: Mon 2022-10-17 05:09:17 EDT; 5h 37min left
| 03:32:36 |
| Winter (she/her) | I noticed the stamp file seems to be holding an mtime from a few hours ago, and isn't being updated by these runs. | 03:34:11 |
| Winter (she/her) | Weird! | 03:34:12 |
| Winter (she/her) | Wonder what happens if I delete it and reboot. | 03:34:31 |
| Winter (she/her) | It gets recreated as expected, gonna reboot again. I assume it won't be updated. | 03:37:26 |
| Winter (she/her) | Yup, isn't updated, timer still fires at reboot. | 03:38:49 |
| hexa | In reply to @winterqt:nixos.dev
Definitely weird how it fires every reboot no matter what, though. that is likely Persist=yes, it will run on reboot if it should have run in the meantime | 08:03:22 |
| hexa | though every reboot sounds wrong | 08:03:56 |
| hexa | are you maybe not persisting some statedir? | 08:04:04 |
| Winter (she/her) | In reply to @hexa:lossy.network
are you maybe not persisting some statedir? look at the other messages where i talk about the stamp file, that's what i'm talking about.
even if the stamp file says the service ran minutes before, a reboot will make it run again, which is obviously wrong. :/ | 11:10:58 |
| Winter (she/her) | it's so weird | 11:11:08 |
| hexa | do you have a setup with non-persistent mountpoints? | 11:11:49 |
| Winter (she/her) | though that's definitely an issue i considered, and maybe there's some race condition or something | 11:11:53 |
| Winter (she/her) | In reply to @hexa:lossy.network
do you have a setup with non-persistent mountpoints? what do you mean by that? (probably not, but want to clarify what you mean) | 11:12:09 |
| hexa | yeah, the wording is weird | 11:12:17 |
| hexa | uhm, erase your darlings blogpost | 11:12:22 |
