| 16 Dec 2023 |
 raitobezarius | It can go both way, anyway, found a bug | 15:34:30 |
| raitobezarius | the parser of /etc/hosts is also more generically broken | 16:03:02 |
| * raitobezarius found another one character bug | 16:08:08 |
| 18 Dec 2023 |
 m1cr0man | I would take acme common code maint being meh, it hasn't been touched in ages | 06:55:50 |
| m1cr0man | needs a whole rewrite, too unreliable | 06:56:05 |
| 23 Dec 2023 |
| raitobezarius changed their display name from raitobezarius to raitobezarius (DECT 2128). | 22:22:39 |
| 26 Dec 2023 |
|  tokudan changed their display name from sugi to sugi 📞8658. | 00:55:57 |
| 30 Dec 2023 |
| raitobezarius changed their display name from raitobezarius (DECT 2128) to raitobezarius. | 19:53:18 |
| tokudan changed their display name from sugi 📞8658 to tokudan. | 23:00:21 |
| 5 Jan 2024 |
|  obsqrprjkt joined the room. | 14:07:59 |
| 27 Jan 2024 |
|  @lehmanator:gnulinux.club removed their profile picture. | 16:53:53 |
| @lehmanator:gnulinux.club set a profile picture. | 16:59:37 |
| @lehmanator:gnulinux.club removed their display name Sam Lehman. | 16:59:42 |
| @lehmanator:gnulinux.club left the room. | 17:03:22 |
| 29 Jan 2024 |
|  Sam Lehman joined the room. | 11:03:10 |
| Sam Lehman set a profile picture. | 11:06:04 |
| 31 Jan 2024 |
 Train | Whenever I try to get a certificate, it always tries to use my local DNS:
lego --email email --dns domain --domains domain run
2024/01/31 13:09:58 [INFO] [domain] acme: Obtaining bundled SAN certificate
2024/01/31 13:09:58 [INFO] [domain] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz-v3/XXXXXXXXXX
2024/01/31 13:09:58 [INFO] [domain] acme: Could not find solver for: tls-alpn-01
2024/01/31 13:09:58 [INFO] [domain] acme: Could not find solver for: http-01
2024/01/31 13:09:58 [INFO] [domain] acme: use dns-01 solver
2024/01/31 13:09:58 [INFO] [domain] acme: Preparing to solve DNS-01
2024/01/31 13:09:59 [INFO] [domain] acme: Trying to solve DNS-01
2024/01/31 13:09:59 [INFO] [domain] acme: Checking DNS record propagation using [127.0.0.53:53]
2024/01/31 13:10:01 [INFO] Wait for propagation [timeout: 2m0s, interval: 2s]
2024/01/31 13:10:01 [INFO] [domain] acme: Waiting for DNS record propagation.
2024/01/31 13:10:03 [INFO] [domain] acme: Waiting for DNS record propagation.
2024/01/31 13:10:05 [INFO] [domain] acme: Waiting for DNS record propagation.
2024/01/31 13:10:07 [INFO] [domain] acme: Waiting for DNS record propagation.
2024/01/31 13:10:09 [INFO] [domain] acme: Waiting for DNS record propagation.
2024/01/31 13:10:11 [INFO] [domain] acme: Waiting for DNS record propagation.
| 19:13:23 |
| Train | Is it normal to use a loopback address such as this one: 127.0.0.53:53 | 19:13:48 |
| Train | * Is it normal to use a loopback address such as this one: 127.0.0.53:53? | 19:17:30 |
 ajs124 | if you're using systemd resolved, yes | 22:02:01 |
| 1 Feb 2024 |
| m1cr0man | In reply to @atra1n:matrix.org
Is it normal to use a loopback address such as this one: 127.0.0.53:53? Yes and you can also set it through the ACME options :) | 00:36:31 |
| 7 Feb 2024 |
|  netpleb joined the room. | 21:27:59 |
| netpleb | i am getting : 2024/02/07 21:34:52 Could not create client: get directory at 'https://acme-v02.api.letsencrypt.org/directory': Get "https://acme-v02.api.letsencrypt.org/directory": dial tcp: lookup acme-v02.api.letsencrypt.org: Temporary failure in name resolution with self-hosted bind (followed the manual) dns-01 validation | 21:38:12 |
 K900 | Sounds like DNS | 21:39:09 |
| netpleb | In reply to @k900:0upti.me
Sounds like DNS right, so I just thought of one thing which might fix it (i feel like i have tried everything already)...but this server actually gets its public ip via a wireguard interface, and I used wg-quick in that interface and did set the dns = [ <some server> ] option. I am going to remove that and cross my fingers! :-) | 21:40:35 |
| netpleb | hmm, sadly that did not seem to solve it | 21:44:40 |
| netpleb | what logs should i post which would help diagnose? | 21:44:54 |
| netpleb | Redacted or Malformed Event | 21:46:52 |
| K900 | Do you actually have working DNS? | 21:49:31 |
| K900 | Like, can you ping that domain name? | 21:49:39 |
