I am experiencing a persistent "502 Application failed to respond" error on my Laravel deployment (Project ID: c01a846c-c836-482f-b613-eec6a6655c2e) even though all diagnostics show the container is starting up perfectly. I have already performed extensive debugging and can confirm the following: 1. The Laravel application boots correctly in the CLI context (`php artisan` runs successfully). 2. The database connection is working (`php artisan migrate` runs successfully). 3. All environment variables (including Firebase credentials via Base64) are correctly loaded. 4. The Dockerfile has been configured to fix all common issues: - Apache's AllowOverride is set to All. - mod_rewrite is enabled. - All application files are owned by the www-data user. 5. A /health check endpoint has been configured in Railway's settings with a 30-second initial delay and 15-second timeout, but the issue persists. The most critical piece of evidence is my latest deployment log, which shows a perfect, error-free startup sequence right up to Apache running in the foreground. I am attaching it below for your review. Given that the container starts without any errors, this suggests a potential issue with the proxy or networking layer on Railway's side for this specific deployment. Could you please investigate this from your end? Thank you for your help.