| 9 Feb 2026 |
 K900 | https://www.githubstatus.com/incidents/ffz2k716tlhx | 10:03:32 |
| K900 | Github is on fire | 10:03:34 |
| K900 | AGAIN. | 10:03:36 |
 sinan | monitoring the situation 🍿 | 11:54:02 |
| 10 Feb 2026 |
 dgrig | At some point in the past, a budget for https://tracker.security.nixos.org/ was approved by the foundation and the security tracker was deployed on a Hetzner Cloud project. We're still way below the budget limit, but we want to increase the size of the hosts (staging and prod) soon which will increase the cost and make it comparable to getting a dedicated host in Hetzner (for way more performance/€).
Is there a reason we should stay in Hetzner Cloud instead of getting a dedi? I vaguely remember someone (no idea who) saying back in late 2024 that Hetzner Cloud was easier to provision in terms of billing/permissions for the foundation and the infra team. Is this still true and a concern?
| 10:57:18 |
 Vladimír Čunát | We do have dedicated Hetzner machines already (and added titan machine recently), so I wouldn't expect issues really. | 11:11:22 |
 Bot_wxt1221 | 
Download 图像.png | 11:29:19 |
| Bot_wxt1221 | nixos wiki has something strange happened. | 11:29:28 |
| Bot_wxt1221 | Or where should I submit this stupid error. | 11:30:55 |
| Bot_wxt1221 | * | 11:30:59 |
| Bot_wxt1221 | Another thing is that it only happens when I refer to some website. | 11:38:13 |
 Weijia | See https://github.com/NixOS/nixos-wiki-infra/issues/121. | 14:29:10 |
| Bot_wxt1221 | oh really stupid | 15:03:45 |
 hexa | #NixOS Wiki fwiw | 15:06:37 |
| 11 Feb 2026 |
| hexa | we can allocate a dedicated machine for the security tracker, but you won't be able to manage it | 00:20:06 |
| hexa | access to robot cannot be delegated | 00:20:17 |
| hexa | if you want a reset or remote kvm access you need to go through the infra-build team | 00:20:49 |
 Tom | you can setup per machine admin robot credentials for dedicated machines. That at least gets you the following tabs: | 00:51:32 |
| Tom | 
Download image.png | 00:51:49 |
| Tom | but yeah, no kvm console ordering or contatct to support | 00:51:56 |
| hexa | yeah, fairly pointless | 00:52:34 |
| hexa | not worth the hassle to setup more credentials | 00:53:12 |
| Tom | reset and rescue can be helpful. You can reset a machine and then take a look via rescue, but yeah, it's not much | 00:54:33 |
| Tom | via rescue mode and then kexec you can even get a nixos running :D | 00:59:46 |
 lennart | you may add additional mail addresses to send the KVM login details to, when opening the ticket.
at work we get all KVM mails (even without additional notes in the ticket) to multiple addresses, would have to take a look where that setting was.
but yea not a perfect solution … | 06:06:53 |
|  zowoq joined the room. | 07:44:55 |
| Tom | You can AFAIK add multiple Main adress (EN) / Kontakt-E-Mail (DE) to the account. That hoewer means ALL E-Mails (exept for Invoices, that's a seperat setting) are sent to those adresses. Not something which would be helpful or desired here IMHO. | 08:22:52 |
 yorik.sar | With NixOS you can easily boot into older generation via rescue or even rebuild the whole system from scratch. I wouldn’t say that’s not much. I found this more than enough for managing internal shared machines. | 09:34:03 |
| hexa | yes, but you'd need a remote kvm to control the bootloader | 09:34:44 |
| hexa | which you can't order with a limited account | 09:35:17 |
