!RROtHmAaQIkiJzJZZE:nixos.org

NixOS Infrastructure

387 Members
Next Infra call: 2024-07-11, 18:00 CEST (UTC+2) | Infra operational issues backlog: https://github.com/orgs/NixOS/projects/52 | See #infra-alerts:nixos.org for real time alerts from Prometheus.120 Servers

Load older messages


SenderMessageTime
2 Jun 2025
@jfly:matrix.orgJeremy Fleischman (jfly)if you're available! https://meet.jit.si/freescoutingggggggg16:36:37
@infinisil:matrix.orginfinisilRedacted or Malformed Event19:42:45
@infinisil:matrix.orginfinisil Jeremy Fleischman (jfly): We might need to do some more: https://public.infinisil.com/2025-06-02_21-43.png 19:44:52
@infinisil:matrix.orginfinisil(the bottommost error is probably just because there are no background jobs, though the error message sucks if so)19:47:01
@jfly:matrix.orgJeremy Fleischman (jfly)ok, good to know! Nina predicted the modules permissions error in https://cyberchaos.dev/e1mo/freescout-nix-flake/-/issues/1. That's a good reminder that we should try out a module.19:58:29
@jfly:matrix.orgJeremy Fleischman (jfly)* ok, good to know! Nina predicted the modules permissions error(s) in https://cyberchaos.dev/e1mo/freescout-nix-flake/-/issues/1. That's a good reminder that we should try out a module.19:59:03
@jfly:matrix.orgJeremy Fleischman (jfly)files https://cyberchaos.dev/e1mo/freescout-nix-flake/-/issues/2 for the public/storage issue20:03:59
@jfly:matrix.orgJeremy Fleischman (jfly) and https://cyberchaos.dev/e1mo/freescout-nix-flake/-/issues/3 for the .env perms issue 20:05:59
@arianvp:matrix.orgArian

Some interesting things I noticed looking at Fastly dashboard:

We have 0 requests using TLS 1.3. They’re all using TLS 1.2. Is this some limitation in the nix codebase in how we setup openssl?
half of the requests are HTTP1.1 and the other half HTTP2. I would expect way more (maybe even all) to be HTTP2. Where is all that HTTP1.1 traffic coming from?

20:39:52
@hexa:lossy.networkhexaour config does not support tls1.320:48:04
@hexa:lossy.networkhexait supports 1.1 and 1.2 and all clients use 1.220:48:11
@hexa:lossy.networkhexaat least the last time I checked, which was early januar20:48:29
@hexa:lossy.networkhexa* at least the last time I checked, which was early january20:48:30
@hexa:lossy.networkhexainteresting profiles would support h2/h3 with 0rtt, but the offered ones lack ipv620:49:02
@hexa:lossy.networkhexasee https://manage.fastly.com/network/subscriptions20:50:51
@arianvp:matrix.orgArianhaving to choose between TLS1.3 and Ipv6 is wild20:51:18
@hexa:lossy.networkhexahm, no … that's not it20:51:20
@hexa:lossy.networkhexahttps://manage.fastly.com/network/tls-configurations20:51:31
@arianvp:matrix.orgArianOkay that’s one mystery down. But why is half our traffic HTTP 1.1?20:51:39
@hexa:lossy.networkhexathat is surprising to me20:52:08
@arianvp:matrix.orgArianhttps://manage.fastly.com/observability/dashboard/system/overview/details/Tb10gX/7mNUQGZO6YxAd2jpokgWxS?mode=historic&view=data20:53:15
@hexa:lossy.networkhexaoh, I confused h1/h2 with tls11/1220:54:39
@hexa:lossy.networkhexaand while we offer tls11/12 all clients use tls1220:54:50
@hexa:lossy.networkhexa* oh, I misremembered the numbers for tls11/12 as h1/h220:55:11
@hexa:lossy.networkhexaso one thing we could add is a https record with alpn information20:55:34
@hexa:lossy.networkhexaand see if that makes a dent, though I would be surprised if it did20:55:54
@emilazy:matrix.orgemilydoes Nix itself speak h2?20:58:23
@hexa:lossy.networkhexaI would hope so, since it relies on curl20:58:43
@arianvp:matrix.orgArian

Yes. it has been speaking H2 for ages

https://github.com/NixOS/nix/blob/e72f19eb28189c9aaaa051423d3c35c93a591fad/src/libstore/filetransfer.cc#L353-L357

unless you disable it explicitly in the config

20:58:56
@arianvp:matrix.orgArianbut this would mean half our users opted out of using it? that seems odd to me20:59:18

Show newer messages


Back to Room ListRoom Version: 6