This page covers the Nginx-specific delivery and logging path for fyuhls.

• faster local-file delivery
• lower PHP overhead on downloads
• better threshold-based completion tracking when the completion log is configured

• fyuhls authorizes the download
• Nginx performs the actual file handoff
• completion logs can feed back into payout or verification-sensitive flows

• Nginx handoff headers are configured correctly
• the completion log path matches the path configured in fyuhls
• the log file is writable by Nginx and readable by the app

• the Nginx completion log path is validated much more strictly
• the example Nginx config includes a /storage/ deny reminder
• download diagnostics in System Status now make it easier to see whether traffic is app-controlled, signed-origin, or CDN-eligible

If downloads work but completion-sensitive behavior does not:

• check the completion log path
• check cron
• check the Nginx completion log ingestion task

If downloads fail outright:

• verify handoff config first
• then test a normal PHP delivery path to isolate whether the break is in Nginx or the app