Resolving 'Application Not Found' and 404 Errors in YunoHost
Learn how to diagnose and fix 'Application Not Found' 404 errors in YunoHost by verifying Nginx reverse proxy mappings and domain associations.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to diagnose and fix 'Application Not Found' 404 errors in YunoHost by verifying Nginx reverse proxy mappings and domain associations.
YunoHost isolates apps with one Unix user and one subdomain each. This note maps where that boundary is real, where it is weak, and how to verify it with ordinary Linux tools.
Goal Determine whether the default MaxRequestWorkers setting is a bottleneck when Yunohost handles many simultaneous web requests. Constraints Yunohost installs Apache with MaxRequestWorkers=150 by default. The bundled PHP‑FPM pool is configured with 5 workers (pm.max_children). Increasing worker counts raises memory consumption, risking swap. No automatic t