Skip to content
Register

Hostinger "managed" WordPress won't touch my 502 issue

Reviews by srelet 8 replies 510 views
srelet

Member OP

#1

Hostinger "managed" WordPress. Site throwing 502s. Their support: "we manage the server, not your application." Transparent about scope at least, but I misunderstood the line.

What I've ruled out:

  • MySQL connection limit (40% of max)
  • PHP-FPM pool exhaustion (pm.max_children not hit)
  • Disk full (68% usage)

502 comes from Hostinger's nginx upstream, not my origin. But they won't check their own gateway timeout against my backend. "Application issue."

I need community eyes. What am I missing? Error budget for this host is burning fast.

ME

Member

#2

Bro this is classic managed scam. They manage what is easy not what is broken.

I am pay 15 dollar for KnownHost managed and they dont even restart PHP when is crash. Very angry. For that price you can get 2 VPS at Leaseweb. No apostrophe in my anger!

reykjavik_doc

Member

container skeptic

#3

Docker? Just a process manager with extra steps and your host is running systemd anyway which is already a process manager so the whole "managed" thing is just someone else's systemd they wont touch because they dont understand it þ
Wordpress is stateful garbage that should be containerized but actually docker is just—no I dont use containers at home I use systemd units and you should too þ

quinnbizz

Member

#4

IMO the managed/unmanaged line varies by provider. YMMV, but Hostinger's terms likely exclude application-layer debugging. Take it with a grain of salt, but check if their nginx timeout is lower than your PHP max_execution_time. Common mismatch.

...
lee_mcr

Member

6 #5

Right then, full transparency: I'm with Hostinger. We're proper clear in the T&Cs—server stack only, not your dodgy plugins

That said, 502 from our edge usually means origin didn't respond in 30s. Your PHP might be fine but WordPress cron or a plugin could be hanging. Check wp-cron spawning. We won't, but the community just did. Cheers lads.

Honey badger don't care... about downtime
SO

Member

1 #6

Yo silvia check object cache redis or something sale my cousin had same with Hostinger jaja was plugin killing everything ok sale

Bruno22

Member

#7

Object cache is the real culprit nine times out of ten honestly

ping so high I wave back
wendy

Member

#8

Which PHP version is Hostinger running, 8.1 or 8.2?

Have you tried restarting it?
netop_mares

Member

#9

If the 502 is from their nginx, that's their infrastructure, Silvia. Full stop.

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft