
A 502 bad gateway WordPress error is a proxy reporting that the process behind it died, vanished or sent a broken answer. Find out who sent it, then read the log line: a PHP fatal error is a 500, and a slow request is a 504.
FFmpeg server requirements come from one number: finished encode-minutes per day. Measure a single job, multiply by your rendition ladder, then read off the tier that clears it. The plan name is the last decision, not the first.

AHosting logged 65,044 AI crawler fetches in 28 days against 298 Google clicks. Most of that load costs nothing, because a cached page consumes no entry process — and most of it cannot be blocked with robots.txt either, because 72% of it is user-triggered.

Useful FFmpeg threads are capped by the video, not by your core count. At 1080p that cap is about four, so spare vCPU buys a second job rather than a bigger thread number.
