DE

↑ ↓ select, Enter open, Esc close

Check permissions along a path

harmlessPermissions and ownershipalle
Adjust the values, the command updates live
user@server
namei -l /var/www/vhosts/example.com/httpdocs/index.php

Splits the path and shows permissions, owner and group for every level starting at /. Accessing a file requires the x permission on every parent directory. If it is missing somewhere, this shows immediately where.

Note: namei is part of util-linux and always available on Debian and Ubuntu.

Also searched as

  • permission denied although file permissions are correct
  • 403 forbidden caused by permissions
  • which folder blocks access
  • show permissions of all parent directories

Related one-liners

All in Permissions and ownership

Analyze server errors (5xx) in the access log

#awk '$9 ~ /^5[0-9][0-9]$/ {print $9, $7}' /var/www/vhosts/system/example.com/logs/access_ssl_log | sort | uniq -c | sort -rn | head -20
harmlessLogs

Capture network traffic on a port with tcpdump

#tcpdump -i any -nn -c 100 port 25
harmlessNetwork

Check all MySQL tables for errors

#mysqlcheck --all-databases --check --silent
harmlessMySQL and MariaDB

Check all PHP files in a directory for syntax errors

$find /var/www/vhosts/example.com/httpdocs/wp-content/themes -name '*.php' -exec php -l {} \; 2>&1 | grep -v '^No syntax errors'
harmlessPHP

Deactivate a single plugin despite a PHP fatal error

$wp plugin deactivate woocommerce --skip-plugins --skip-themes --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Deactivate all plugins and save the active list

$wp plugin list --status=active --field=name --path=/var/www/vhosts/example.com/httpdocs > /var/www/vhosts/example.com/active-plugins.txt && wp plugin deactivate --all --path=/var/www/vhosts/example.com/httpdocs
cautionWP-CLI

Read first, then run.

The commands on myline.de act directly on servers, files and databases. A wrong path or placeholder can delete data irreversibly or make a server unreachable.

  • All commands are provided without warranty and are not tested on every system.
  • Understand what a command does before running it, and check every placeholder.
  • Make a backup first and, if possible, try it on a test system.
  • You run commands at your own risk. Liability for damages is excluded to the extent permitted by law.