How to fix Error: EACCES: permission denied, open '/root/file.txt' in Node.js

Node.jsBEGINNERMEDIUM

This error occurs when a Node.js process attempts to access a file, directory, or port without the necessary permissions. It commonly happens during file operations, npm installations, or when trying to bind to privileged ports below 1024.

What this error means

The EACCES error (Error Access) is a system-level permission error that occurs when Node.js attempts an operation that requires permissions the current user or process does not have. This is a POSIX error code that originates from the operating system's file access control system. In Node.js, this error most commonly appears during file system operations (fs.readFile, fs.writeFile, fs.access), but can also occur when installing npm packages globally, binding to network ports, or executing files. The error indicates that while the target file or resource exists, the current user lacks the read, write, or execute permissions needed for the operation. Understanding file permissions is crucial for resolving this error. On Unix-like systems (Linux, macOS), every file has owner, group, and other permissions. On Windows, NTFS permissions and User Account Control (UAC) can trigger similar access denied errors. The solution depends on whether you need to modify permissions, change ownership, or restructure how your application accesses resources.

How to fix "Error: EACCES: permission denied, open '/root/file.txt'"

1Identify the file or directory causing the permission error

Check the exact path mentioned in the error message and inspect its permissions:

bash

# View file permissions
ls -la /path/to/file.txt

# View directory permissions
ls -ld /path/to/directory

# Check ownership
stat /path/to/file.txt

Look for the permission string (e.g., -rw-r--r--) and owner/group. If the file shows restrictive permissions like -rw------- (600) and is owned by a different user, you've found the issue.

2Fix file permissions with chmod (if you own the file)

If you own the file but it has restrictive permissions, modify them:

bash

# Make file readable and writable by owner, readable by others
chmod 644 /path/to/file.txt

# Make file readable, writable, and executable by owner
chmod 700 /path/to/script.sh

# Make directory accessible with read and execute permissions
chmod 755 /path/to/directory

For Node.js applications, ensure your process user has at least read permission (4) for files it needs to read, write permission (2) for files it modifies, and execute permission (1) for directories it traverses.

3Change file ownership with chown (if appropriate)

If the file is owned by root or another user, change ownership to your user:

bash

# Change ownership to current user
sudo chown $(whoami) /path/to/file.txt

# Change ownership recursively for directories
sudo chown -R $(whoami):$(whoami) /path/to/directory

# For npm directories specifically
sudo chown -R $(whoami) ~/.npm
sudo chown -R $(whoami) /usr/local/lib/node_modules

Be cautious when changing ownership of system files. Only change ownership of files within your home directory or application directories you manage.

4Reconfigure npm to avoid global permission issues

Instead of using sudo for npm installations, configure npm to use a directory in your home folder:

bash

# Create directory for global npm packages
mkdir ~/.npm-global

# Configure npm to use this directory
npm config set prefix '~/.npm-global'

# Add to PATH in your shell profile (~/.bashrc, ~/.zshrc)
export PATH=~/.npm-global/bin:$PATH

# Reload shell configuration
source ~/.bashrc  # or source ~/.zshrc

After this configuration, global npm packages will install to your home directory without requiring sudo, eliminating permission conflicts.

5Use ports above 1024 or configure capabilities for privileged ports

If your error occurs when binding to ports, either use non-privileged ports or grant capabilities:

javascript

// Use port above 1024 (recommended)
const server = app.listen(3000, () => {
  console.log('Server running on port 3000');
});

// Or use environment variable for flexibility
const PORT = process.env.PORT || 3000;
server.listen(PORT);

For production deployment on port 80/443, use a reverse proxy (nginx, Apache) or grant capabilities:

bash

# Grant capability to bind to privileged ports (Linux only)
sudo setcap 'cap_net_bind_service=+ep' $(which node)

Note: setcap must be reapplied after Node.js updates.

6Verify and update file paths in your Node.js code

Ensure your application writes to appropriate directories with proper permissions:

javascript

import { writeFile } from 'fs/promises';
import { join } from 'path';
import os from 'os';

// Write to user's home directory instead of system directories
const homeDir = os.homedir();
const filePath = join(homeDir, '.myapp', 'data.json');

try {
  await writeFile(filePath, JSON.stringify(data), { mode: 0o644 });
  console.log('File written successfully');
} catch (err) {
  if (err.code === 'EACCES') {
    console.error('Permission denied. Check file permissions.');
  } else {
    console.error('Write failed:', err);
  }
}

Never hardcode paths to system directories like /root, /usr, or /etc unless running as root (which is not recommended).

Advanced notes

Using Node Version Managers to Avoid Permission Issues

Installing Node.js via nvm (Node Version Manager) or fnm eliminates most permission problems:

bash

# Install nvm
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash

# Install Node.js through nvm
nvm install --lts
nvm use --lts

# Global npm packages now install to ~/.nvm/versions/node/vX.X.X/lib/node_modules
npm install -g typescript  # No sudo needed

This approach completely avoids system-level permission conflicts because all Node.js files live in your home directory.

Understanding File Permission Numbers

Permission numbers are octal values combining read (4), write (2), and execute (1):

- 644 = rw-r--r-- (owner read/write, group/others read)
- 755 = rwxr-xr-x (owner read/write/execute, group/others read/execute)
- 600 = rw------- (owner read/write only, no access for others)
- 700 = rwx------ (owner full access, no access for others)

For application data files, 644 is typically appropriate. For executables and directories, use 755. For sensitive files like private keys, use 600.

SELinux and AppArmor Considerations

On systems with SELinux (Red Hat, CentOS, Fedora) or AppArmor (Ubuntu, Debian), permission errors may persist even with correct file permissions:

bash

# Check SELinux status
getenforce

# View SELinux context
ls -Z /path/to/file.txt

# Temporarily disable SELinux for testing (not recommended for production)
sudo setenforce 0

# Properly set SELinux context for your application
sudo chcon -t httpd_sys_content_t /path/to/file.txt

Instead of disabling security modules, create proper policies or adjust contexts for your application's needs.

Docker Container Permissions

In Docker containers, EACCES errors often occur due to volume mount permission mismatches:

dockerfile

# Run as non-root user in Dockerfile
RUN useradd -m -u 1000 appuser
USER appuser

# Ensure mounted volumes match user ID

bash

# Mount with appropriate ownership
docker run -v $(pwd)/data:/app/data --user $(id -u):$(id -g) myapp

Security Best Practices

- Never run Node.js applications as root in production
- Use principle of least privilege - grant only necessary permissions
- Avoid chmod 777 (world-writable) - it's a security risk
- For production deployments, use systemd or pm2 with proper user contexts
- Regularly audit file permissions with tools like find:

bash

# Find world-writable files (potential security issue)
find /path/to/app -type f -perm -002

# Find files owned by root in application directory
find /path/to/app -user root

Windows-Specific Considerations

On Windows, EACCES errors relate to NTFS permissions and UAC:

- Run Command Prompt or PowerShell as Administrator for system directory access
- Check file properties → Security tab for permission settings
- Use icacls command to modify permissions:

cmd

icacls "C:\path\to\file.txt" /grant YourUsername:F

However, restructuring your application to use user directories (AppData, Documents) is preferred over modifying system permissions.

How to fix Error: EACCES: permission denied, open '/root/file.txt' in Node.js

What this error means

Typical symptoms

Common causes

How to fix "Error: EACCES: permission denied, open '/root/file.txt'"

Advanced notes

Related errors

Official resources & further reading