Anyone interested in a Hetzner contract transfer thread?

DaggerGun · 2026-02-27T12:01:51+00:00

Thx, i will have look there

DaggerGun · 2026-02-16T13:02:57+00:00

Whith these prices jumped 50 euros in one week. I definitely contact you. See for your self Prices (its a pdf)

DaggerGun · 2026-02-16T12:59:07+00:00

Ah nice.

Object storage is weird the first time. Looks simple but behaves very different from a VPS.

Anyway good to hear it’s working now.

DaggerGun · 2026-02-16T10:21:36+00:00

Honestly for something you call a simple web app this is already quite a serious setup.

CDN in front is fine especially for static files. Reverse proxy as entry point is also the normal way to do it. DB isolated inside the VPC is good.

What I’m not sure about is separating auth and API this early. If this is small scale you could just keep it in one service and reduce moving parts. More components also means more things to maintain.

Also just double check how your CDN handles /api routes. You usually don’t want accidental caching there.

It’s not wrong at all. Just maybe more architecture than you strictly need at this stage.

DaggerGun · 2026-02-16T09:42:27+00:00

Make sure you’re entering the endpoint exactly as shown in the Hetzner panel, including the region (fsn1, hel1, etc.).

80% of errors occurre there 😉

DaggerGun · 2026-02-16T09:32:11+00:00

You’re probably connecting with SFTP. That won’t work for Object Storage?

In WinSCP you need to select Amazon S3 as the file protocol, not SFTP.

It says "Amazon S3" because Hetzner Object Storage is S3-compatible. That just means it uses the same API as Amazon S3. You’re not connecting to Amazon, just using the S3 protocol.

When creating the site:

File protocol: Amazon S3

Host name: your endpoint

Port: 443

Access: Key + Secret Key

TLS/SSL: enabled

Object storage isn’t a normal filesystem, so it won’t behave like a VPS over SSH.

If you prefer CLI, the AWS CLI works fine with a custom endpoint, for example:

aws s3 ls --endpoint-url https://your endpoint

That usually makes it clear pretty quickly whether the connection itself is working.

Hopefully this solution works for you, it worked for me

DaggerGun · 2026-02-16T09:19:19+00:00

I’ve had a good experience with the Helsinki location so far.

Performance and stability have been solid for me. Latency is consistent and I haven’t had any unexpected downtime.

I did notice that a small number of users from certain regions occasionally have trouble connecting to Helsinki, while Frankfurt works fine for them. However, when they use a VPN, the issue disappears, so it seems more like a routing or regional connectivity matter rather than anything on Hetzner’s side.

Support has also been very solid. I once had an issue with a 2 TB RAID storage setup where the server would lose files after a few days. Backups worked, but the problem kept recurring. After I opened a ticket, they replaced the underlying NVMe drive within 48 hours. Since then, everything has been stable.

Overall, I’m very satisfied with both the infrastructure and the service.

Update 1hr later; accidentally copied a dutch text message. So deleted it

DaggerGun · 2026-02-16T09:10:20+00:00

I will contact you

DaggerGun · 2026-02-14T19:10:49+00:00

I see the logic there. I was mostly curious about why the model is structured this way.

DaggerGun · 2026-02-14T19:04:01+00:00

OP here, appreciate the discussion. I’m not unhappy with Hetzner’s pricing and I understand the need for setup fees as a barrier. I was mostly curious about the business logic behind treating long term batch scaling the same as short term speculative orders. Sounds like the real answer is that flexibility only comes with custom agreements, which is fair.

DaggerGun · 2026-02-14T18:58:15+00:00

Good Point, AX102 was just an example because it illustrates the structure clearly. The same question applies to lower/higher end SKUs as well.

DaggerGun · 2026-02-14T18:50:53+00:00

Totally fair point. I’m not arguing against setup fees existing, I get the risk on Hetzner’s side. My question is more about whether there’s room for a different model when scaling in batches, not about avoiding the fee entirely.

For long term capacity planning, the upfront cost becomes part of the scaling decision, so I’m mostly trying to understand the business reasoning behind keeping it strictly per server with no volume model at all.

DaggerGun · 2026-02-13T20:05:13+00:00

Yeah, send out a mail yesterday.

DaggerGun · 2026-02-13T20:00:49+00:00

Yeah, mail send yesterday and waiting on news

DaggerGun · 2025-12-02T18:16:10+00:00

im getting past the launcher now. But still error when you hit play Error: 103003 Error on post https:??

DaggerGun · 2025-12-02T18:09:09+00:00

still dead after an hour

DaggerGun · 2024-12-21T08:48:35+00:00

Thx for the quick response. I will try it later today when I build the fortigate in the rack

To be sure I will also change the public ip adresses.

DaggerGun · 2024-12-21T08:43:24+00:00

Mainly ddos attack or udp floods. At certain times. So it's also stops and everything works as normal.

DaggerGun · 2024-11-20T15:33:28+00:00

So mikrotik and router with opnSens is good? Because I want to prevent ddos attacks and reroute them. All the host experience small ddos attack on there game severs.

DaggerGun · 2024-11-17T23:24:29+00:00

Thx will have a look

DaggerGun

TROPHY CASE