DE

↑ ↓ select, Enter open, Esc close

Fix the Git error dubious ownership on servers

cautionGitalle

Caution: This command changes the system. Understand what it does before you run it.

Adjust the values, the command updates live
user@server
git config --global --add safe.directory /var/www/vhosts/example.com/httpdocs

Adds the directory to the global Git configuration of the current user as trusted. The error message detected dubious ownership appears since Git 2.35.2 when a repository belongs to another user, typically when working as root in Plesk vhosts. The entry only applies to the user who runs the command.

Note: A cleaner approach is to run Git as the owner of the repository, for example with sudo -u webuser git pull. Only use the value * for all directories if no untrusted users can create repositories.

Also searched as

  • fatal detected dubious ownership in repository
  • git as root in vhost directory not working
  • git unsafe repository error

Related one-liners

All in Git

Change the message of the last commit

$git commit --amend -m 'Fix: correct cache path in configuration'
cautionGit

Create an annotated tag and push it to the remote

$git tag -a v1.4.0 -m 'Release 1.4.0' && git push origin v1.4.0
cautionGit

Delete local branches that are already merged

$git branch --merged main | grep -vE '^[*+]|^\s*(main|main|master|develop)$' | xargs -r git branch -d
cautionGit

Discard local changes to a file

$git restore wp-config.php
destructiveGit

Find commits that added or removed specific text

$git log -S 'define('WP_DEBUG'' --oneline --all
harmlessGit

Find out who changed specific lines of a file

$git blame -L 10,40 wp-config.php
harmlessGit

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.