| 19 Sep 2025 |
 ghpzin | Yes, that was for previous issue when there was js error and nothing loaded.
Not sure if current issue is related to security fix that was the reason for that.
It is weird, because on other prefixes there is only 1 request and it is fine, on those there is first one and then the always spamming one.
Both return 200 with what seems to be correct things: <ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Name>...
I guess pagination does not work, first request on spamming ones returns:
<MaxKeys>1000</MaxKeys><Delimiter>/</Delimiter><IsTruncated>true</IsTruncated>
Working ones return <IsTruncated>false</IsTruncated> | 19:10:23 |
| ghpzin | Yes, that was for previous issue when there was js error and nothing loaded.
Not sure if current issue is related to security fix that was the reason for that.
It is weird, because on other prefixes there is only 1 request and it is fine, on those there is first one and then the always spamming one.
Both return 200 with what seems to be correct things: <ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Name>...
I guess pagination does not work, first request on spamming ones returns:
<MaxKeys>1000</MaxKeys><Delimiter>/</Delimiter><IsTruncated>true</IsTruncated>
Working ones return <MaxKeys>1000</MaxKeys><Delimiter>/</Delimiter><IsTruncated>false</IsTruncated> | 19:10:51 |
| ghpzin | Yes, that was for previous issue when there was js error and nothing loaded.
Not sure if current issue is related to security fix that was the reason for that.
It is weird, because on other prefixes there is only 1 request and it is fine, on those there is first one and then the always spamming one.
Both return 200 with what seems to be correct things: <ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Name>...
I guess pagination does not work, first request on spamming ones returns:
<IsTruncated>true</IsTruncated>
Working ones return <IsTruncated>false</IsTruncated> | 19:11:19 |
 Vladimír Čunát | I think those pages did work at some point, but I haven't tried very recently to be sure that they did break right now around those security fixes. | 19:14:24 |
| Vladimír Čunát | * I believe those pages did work at some point, but I haven't tried very recently to be sure that they did break right now around those security fixes. | 19:14:32 |
 K900 | Can someone update anubis on Hydra | 19:14:40 |
| K900 | I still can't load it on my phonen | 19:14:46 |
| K900 | * | 19:14:50 |
| K900 | Because of the 9 cores thing | 19:14:55 |
| Vladimír Čunát | We deploy whatever is in stable-small. | 19:16:28 |
| Vladimír Čunát | I think even in this case (anubis), at a quick glance at the repo. | 19:16:51 |
| Vladimír Čunát | Last update was just a couple days ago. | 19:17:04 |
| K900 | Hm I wonder if they haven't tagged a release yet | 19:18:27 |
 Mic92 | What is the 9 cores thing? | 20:19:28 |
 dgrig | https://anubis.techaro.lol/blog/2025/cpu-core-odd/ | 20:25:13 |
| ghpzin | Commit with fix seems to be only in v1.22.0:
https://github.com/TecharoHQ/anubis/commit/c661bc37d133976a005fb0b1060e3e0a34f69003 | 20:28:20 |
| 21 Sep 2025 |
 hexa | getting closer to replacing haumea | 21:25:36 |
| hexa | but the requirements changed slightly | 21:25:47 |
| hexa | given the recent increase of low disk alerts we should go for 2x2TB instead of 2x1TB | 21:26:03 |
| hexa | upgrading an AX52 will land us at 124,63 EUR/mo | 21:27:05 |
| hexa | an AX102 starts at 125,84 EUR/mo and comes with twice the memory and a beefier CPU | 21:27:43 |
| hexa | the intel alternative would be an EX101 but I'm not fond of the prevalence of E-cores on the i9-13900 | 21:28:18 |
| hexa | https://www.hetzner.com/dedicated-rootserver/matrix-ax/
https://www.hetzner.com/dedicated-rootserver/matrix-ex/ | 21:28:34 |
| hexa | though the intel machine does come with ECC memory and 2x2TB disk 😬 | 21:29:49 |
| hexa | anyway, these are my thoughts. enjoy | 21:30:58 |
| dgrig | ECC would be good to have, but I wonder if those intel 13900s are affected by this or did Hetzner RMA'd them/patched them all fast enough | 21:35:57 |
| hexa | supposedly fixed by firmware updates a while ago | 21:37:17 |
|  Nico joined the room. | 21:42:45 |
 Tom | I think you'll end up paying and receiving (if you don't tell them to remove those) the default two 1tb drives anyway. So if you add 2x 1tb you're getting 1 TB, 1 TB, 2 TB and 2 TB. Just mentioning it in case that wasn't considered and somehow affects the plans. | 21:45:14 |
| hexa | yeah, I'm aware. | 21:45:53 |
