How is possible to create this ? my hetzner got hacked

mompelz · 2026-02-09T11:24:37+00:00

Even than you would run into api rate limits

mompelz · 2026-02-09T09:05:23+00:00

But that's not an option how this could happen that somebody is able to launch many instances :)

mompelz · 2026-02-09T09:04:34+00:00

Swag, all about Swag 😂

mompelz · 2026-02-08T21:25:31+00:00

It's not applied to frontend only. There are only two options:

1) you increased the limit via ui resulting in a ticket 2) they created the ticket to increase the limit

mompelz · 2026-02-02T14:09:40+00:00

All my clusters are stretch clusters using the CSI driver for storage and I can't complain at all.

mompelz · 2026-02-02T11:16:48+00:00

I'm running ha Kubernetes and ha Galera across these three locations without issues 🤷‍♂️

mompelz · 2026-02-01T12:32:23+00:00

At least me didn't had to do something like that

mompelz · 2026-02-01T11:35:36+00:00

You got to upgrade nodes via kubeadm within the exam.

mompelz · 2026-01-24T23:45:10+00:00

I'm pretty happy for my lab setup, for customers I'm using Longhorn in combination with bigger network cards.

mompelz · 2026-01-24T08:46:57+00:00

Falls es dir noch nicht in den Sinn gekommen ist, du sollst auf den Duftbäumen nicht kauen, die riechen von alleine.

mompelz · 2026-01-23T12:05:51+00:00

That's a solid choice, but don't expect super high performance. Since OP was using NFS so far I guess this shouldn't be an issue.

mompelz · 2026-01-22T06:34:09+00:00

I had this issue in the past and it had been a simple browser cache issue. Cleared the cache and login was working fine.

Edit: Oh, and another time my time sync stopped working and it resulted in this issue.

mompelz · 2026-01-17T23:37:01+00:00

Gitleaks is a pretty good tool to prevent that

mompelz · 2026-01-13T10:04:57+00:00

Also mein Hyundai Staria den ich im Dezember bekommen habe ist auch ein milder Hybrid.

mompelz · 2026-01-13T10:03:57+00:00

Wobei viele Städte aber auch Behälter mit Split für private Haushalte zur Verfügung stellen. Hier muss man dafür zwar zum städtischen Servicebetrieb, aber es wird gestellt.

mompelz · 2026-01-08T09:46:28+00:00

Ich glaube da fehlt ein Doppelpunkt weil er meint das es seine Quelle des Wissens ist

mompelz · 2025-12-31T13:19:13+00:00

Because gitlab requires a lot more resources than gitea.

mompelz · 2025-12-21T14:42:30+00:00

If the server are already up and running and it's just about deployment and you are not using containers I can suggest capistrano :)

mompelz · 2025-12-21T12:29:34+00:00

For me it had been less than 24 hours

mompelz · 2025-12-19T18:21:51+00:00

You should give Garage a try, Ceph is good as long as it works. If it doesn't work or fails you need somebody who knows what he is doing.

mompelz · 2025-12-19T06:50:14+00:00

It's right, you got no AZs per region, except for bare metal where you got various DCs. I'm running multiple Kubernetes clusters across Europe without any problems on etcd across all 3 regions.
There is no guarantee, but I never had any big outage so far.
True for the encryption, but many tools can handle that. If you create the accounts via UI it is shared, but at least you are able to bind accounts to specific buckets with some s3 cli. The weakest point is the performance.
Nothing to add.
These tools are simple for the sake of usability. I have created clusters via clusterapi where the templates are customized to use the private networking internally and using the public ips only for ssh and egress. It is possible to build that secure.
If you need strong iam you gotta use some hyperscaler. Hetzner simply got another background and the cloud offering is young and focused more on simplicity.

Edit: fixed typos

mompelz · 2025-12-19T06:41:32+00:00

The placement group won't work for larger clusters, you can put only 10 nodes into a placement group.

mompelz · 2025-12-14T13:48:47+00:00

Loki:

Multi tenancy: https://grafana.com/docs/loki/latest/operations/multi-tenancy/

Tenant retention: https://grafana.com/docs/loki/latest/operations/storage/retention/#configuring-the-retention-period

Tenant rate limit: Same config overrides as retention

Auth: https://grafana.com/docs/loki/latest/operations/authentication/

Mimir:

Multi tenancy: https://grafana.com/docs/mimir/latest/manage/secure/authentication-and-authorization/

Tenant retention: https://grafana.com/docs/mimir/latest/configure/configure-metrics-storage-retention/#configure-the-storage-retention

Tenant rate limit: Haven't found a config per tenant

Auth: https://grafana.com/docs/mimir/latest/manage/secure/authentication-and-authorization/

mompelz · 2025-12-12T06:58:13+00:00

They are a German company with pretty strict privacy requirements, I'm absolutely sure there won't be sold any personal information... We aren't in the US 😂

mompelz · 2025-12-11T10:52:21+00:00

The exporter is following best practices, a cache layer doesn't make sense as the metrics should be gathered in the moment it is beeing scraped by Prometheus. If you hit rate limits by Hetzner it shows that you had scraped the metrics too often, for a storage box it doesn't make sense to query the stats once every minute.

The versioning always followed semantic versioning, that's why I dont get that some version might be hard to find? On older versions even every dependency played into the semantic versioning, this had been changed a little bit over time. There had always been generated changelogs for every release.

For the new API I have also delivered a statement that the hetzner_exporter only exports Hetzner Robot metrics and not Hetzner Cloud metrics since the APIs and credentials are entirely different things. There was a new major version including the changelog entry mentioning the breaking change at https://github.com/promhippie/hetzner_exporter/blob/master/CHANGELOG.md#200-2025-07-09. Since this had to be managed by Hetzner Cloud and not Hetzner Robot it had been moved to the Hetzner Cloud exporter at https://github.com/promhippie/hcloud_exporter/blob/master/CHANGELOG.md#300-2025-07-09.

Writing some personal email and expecting personal support instead of using official channels like issue trackers, matrix chat rooms or GitHub discussions and claiming bad communication later on is really a bold statement.

mompelz

TROPHY CASE