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
The goal is to revert database schema changes applied during a module upgrade on Yunohost v2.0.0. The core relies on Symfony/Doctrine migrations, yet no generic rollback command is exposed to undo all module‑specific changes in one step. Current constraints include a manual backup dump that must be restored to recover from a failed migration, which is non‑at
Apache Web Server and Yunohost Core – Cache Invalidation Interoperability Question When an application on Yunohost is updated or its configuration changes, the Apache mod_cache module may continue to serve stale static or dynamic content until the TTL expires. Yunohost’s global "clear cache" button purges all cache entries, but it offers no per‑application g