nginx cannot write <path>

What it means

This nginx image expects root, and containers here run as a normal user.

The build passed, but the app did not start or did not answer the health check.

Typical causes

• The app does not listen on 0.0.0.0 and the port from the PORT variable
• An environment variable is missing, or the database or Redis is not connected
• The start command is wrong or the process exits right away

How to fix it on mevcore

Use nginxinc/nginx-unprivileged as the base image (it listens on 8080 and keeps its files in /tmp), or move pid and temp paths to /tmp in nginx.conf.

1. 1 Open the app in the mevcore panel: the Problems card on the overview shows this error and the log line it was found in.
2. It is fixed on the “Settings” tab of the app.
3. 2 After the fix, deploy again. If it fails again, the log ends with [mevcore] lines naming the new error code.
4. 3 The "Ask AI" button next to the error prepares a request for ChatGPT or Claude: the error code, the end of the log without secrets and the app settings.

For an AI assistant

The same in English: paste it together with the log into the AI chat.

mevcore error code: runtime.nginx_unprivileged
phase: start / health check
diagnosis: nginx cannot write <path>
platform hint: This nginx image expects root, and containers here run as a normal user. Use nginxinc/nginx-unprivileged as the base image (it listens on 8080 and keeps its files in /tmp), or move pid and temp paths to /tmp in nginx.conf.
platform docs: https://mevcore.com/llms-full.txt