TierHive - 768mb ram | 7 GB NVMe | $0.64 /mo | UK, DE, USA, CA, SG, FR | Free to try| Build a plan!

AnthonySmith · April 22

@WSS said:

@AnthonySmith said:

@WSS said:
It was doing fine with a local netcat. (shrug) It seems to be kind of sporadic. I've got a pre-cached nginx and grav with a handful of php-fpm in the pool. Even if php-fpm went down for several hours, it should still serve from my nginx cache.

Only thing that it might trip would be the too-many-consecutive hits pool, and that's only set for the contact page.

I will have a look in a bit, if it's our side being over the top I will relax it

I've been watching your curl hits every so often and they're fine. They do hit my default page, though, and not the one I've got configured. You're doing an HTTP/1.1 request, but I don't see my hostname there. My default failthrough IP based auth/unknown doesn't (didn't) have an index page so it was throwing a 404 at you.
%sudo tail /var/log/nginx/access.log
10.0.0.15 - - [22/Apr/2026:11:58:02 -0500] "GET / HTTP/1.1" 200 615 "-" "curl/8.14.1"
10.0.0.15 - - [22/Apr/2026:12:00:01 -0500] "GET / HTTP/1.1" 200 615 "-" "curl/8.14.1"
10.0.0.15 - - [22/Apr/2026:12:02:01 -0500] "GET / HTTP/1.1" 200 615 "-" "curl/8.14.1"
10.0.0.15 - - [22/Apr/2026:12:04:02 -0500] "GET / HTTP/1.1" 200 615 "-" "curl/8.14.1"
10.0.0.15 - - [22/Apr/2026:12:06:02 -0500] "GET / HTTP/1.1" 200 615 "-" "curl/8.14.1"
10.0.0.15 - - [22/Apr/2026:12:08:01 -0500] "GET / HTTP/1.1" 200 615 "-" "curl/8.14.1"
10.0.0.15 - - [22/Apr/2026:12:10:01 -0500] "GET / HTTP/1.1" 200 615 "-" "curl/8.14.1"
10.0.0.15 - - [22/Apr/2026:12:12:01 -0500] "GET / HTTP/1.1" 200 615 "-" "curl/8.14.1"
10.0.0.15 - - [22/Apr/2026:12:14:01 -0500] "GET / HTTP/1.1" 200 615 "-" "curl/8.14.1"
10.0.0.15 - - [22/Apr/2026:12:16:02 -0500] "GET / HTTP/1.1" 200 615 "-" "curl/8.14.1"

Compared to other traffic-

%wc -l /var/log/nginx/site.com.access.log
254 /var/log/nginx/site.com.access.log
%

Right, that's a pretty obvious problem,can't believe no one else has reported it.

I will have some changes made.

WSS · April 22

@AnthonySmith said:
Right, that's a pretty obvious problem,can't believe no one else has reported it.

Probably because you're throwing a 503, which looks like misconfiguration or a capacity problem. That's what confused the hell out of me, until I saw "Wait, this heartbeat isn't following spec."

WSS · April 23

Is there anyway to resize down from 10GB? It won't let me, and I'm using maybe 4. Unless it's a qcow image, that's just waste.

AnthonySmith · April 23

@WSS said:
Is there anyway to resize down from 10GB? It won't let me, and I'm using maybe 4. Unless it's a qcow image, that's just waste.

It's qcow and it's based on the distro official image minimums, or maybe you selected 10gb on create.

Downgrading disk is not supported (yet) but I might be able to do it manually for you if you want

AnthonySmith · April 24

@WSS said:

@AnthonySmith said:
Right, that's a pretty obvious problem,can't believe no one else has reported it.

Probably because you're throwing a 503, which looks like misconfiguration or a capacity problem. That's what confused the hell out of me, until I saw "Wait, this heartbeat isn't following spec."

You now get about 20 minutes of local downtime before haproxy boots your record out instead of 4 minutes.

We are also going to talk about a generic enough but informative enough 503 so you know where its being stopped should it be hit by haproxy.

@WSS said:
Is there anyway to resize down from 10GB? It won't let me, and I'm using maybe 4. Unless it's a qcow image, that's just waste.

Token adjustment for that vps applied so you are only paying for what you are using.

TierHive - 768mb ram | 7 GB NVMe | $0.64 /mo | UK, DE, USA, CA, SG, FR | Free to try| Build a plan!

Comments