SECURITY WARNING: Never run commands you don't understand. Always review code before execution. Use at your own risk.
FixMyError.net
WebServer New Added 26 September 2026

Apache: Invalid command 'Order', perhaps misspelled or defined by a module

Order, Allow and Deny moved into mod_access_compat in 2.4, so configuration written for 2.2 no longer parses unless that module is loaded. The same wording appears for any directive whose module is absent, which is why enabling the compatibility module is a stopgap and rewriting the block is the fix.

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
# Which directive, in which file and line
sudo apache2ctl configtest

# Translate rather than restore:
#   Order allow,deny        ->  Require all denied
#   Order deny,allow        ->  Require all granted
#   Allow from 10.0.0.0/8   ->  Require ip 10.0.0.0/8
#   Satisfy any             ->  <RequireAny>

# Stopgap when you cannot edit every vhost today
sudo a2enmod access_compat
sudo systemctl restart apache2

# The same message for other directives means a different missing module
apache2ctl -M | sort
sudo a2enmod rewrite headers      # for RewriteRule, Header

# RHEL and CentOS load modules from files rather than with a2enmod
grep -R LoadModule /etc/httpd/conf.modules.d/

# Mixing 2.2 and 2.4 authorisation in one directory gives unpredictable results

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.

  1. Validate configuration before reloading: nginx -t, apachectl configtest, caddy validate. This catches syntax errors without dropping traffic.
  2. Dump the fully resolved configuration with nginx -T to see what is actually in effect, including every include.
  3. 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.
  4. For permission errors, test as the server user: sudo -u www-data cat /path/to/file. Check execute bits on every parent directory.
  5. 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 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.