WebServer New Added 9 October 2026

Apache: AH01071: Got error 'Primary script unknown'

The message is PHP-FPM's, relayed by Apache: the script path Apache sent over FastCGI does not exist, or cannot be read, from PHP-FPM's point of view. Usually the handler builds the path from the wrong document root, or PHP-FPM runs in a container where the code lives somewhere else. The browser only sees "File not found.", so it looks like a missing page rather than two processes disagreeing about a path.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix

# How is Apache handing .php files to PHP-FPM?
grep -rn 'proxy:unix\|proxy:fcgi\|ProxyPassMatch' /etc/apache2/ /etc/httpd/ 2>/dev/null

# Can the FPM pool user read the file at that exact path?
grep -E '^(user|chroot)' /etc/php/8.3/fpm/pool.d/www.conf
sudo -u www-data ls -l /var/www/example/public/index.php

# Preferred form: Apache maps the path from its own DocumentRoot
<FilesMatch "\.php$">
    SetHandler "proxy:unix:/run/php/php8.3-fpm.sock|fcgi://localhost"
</FilesMatch>

# PHP-FPM in a container: mount the code at the same path in both,
# or rewrite the path Apache sends
# ProxyFCGISetEnvIf "true" SCRIPT_FILENAME "/app/public%{reqenv:SCRIPT_NAME}"

sudo apachectl configtest && sudo systemctl reload apache2

How to diagnose WebServer errors

Web server errors are usually about permissions, binding, or configuration that was never loaded. A common trap: the server runs as an unprivileged user (www-data, nginx), so it needs execute permission on every directory in the path to a file, not just read permission on the file itself. Another: editing a config file changes nothing until the server is reloaded and the file is actually included.

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

Validate configuration before reloading: nginx -t, apachectl configtest, caddy validate. This catches syntax errors without dropping traffic.
Dump the fully resolved configuration with nginx -T to see what is actually in effect, including every include.
Read the error log, not the access log, for 5xx causes. nginx names the failing upstream and the exact filesystem path it could not open.
For permission errors, test as the server user: sudo -u www-data cat /path/to/file. Check execute bits on every parent directory.
For binding failures, find the current listener with ss -tulpn | grep :80. Ports below 1024 need privileges or a capability such as CAP_NET_BIND_SERVICE.

Tools worth reaching for

nginx -t / nginx -T
apachectl configtest
ss -tulpn
tail -f error.log
sudo -u www-data

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

httpd.apache.org

Related WebServer errors

See all 20 WebServer errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.