Error AtlasError Documentation and Resolution
Back to searchMore Node.js errors

Node.js

Node.js permission denied while accessing a file or resource

EACCES: permission denied

Node.js could not access a file, folder, port, or other resource because the current process does not have the required permissions.

EACCESruntime

Observed message

EACCES: permission denied

Why it happens

  • The Node.js process does not have permission to read, write, or execute the target path.
  • The process is trying to bind to a restricted port or system-owned resource.
  • The file or directory ownership does not match the user running the app.

How to fix it

  1. Check the ownership and permissions of the affected file, folder, or socket.
  2. Run the process as a user that has the required access instead of elevating more broadly than necessary.
  3. Avoid privileged ports or protected locations unless the deployment environment is configured for them deliberately.

Official reference

Node.js Errors

Related errors

EMFILENode.js opened too many files at onceECONNREFUSEDNode.js connection was refused by the target serviceECONNRESETNode.js connection was reset by the peerEADDRINUSENode.js could not bind because the address is already in use

Explore more

Node.jsBrowse more Node.js errorsruntimeBrowse more runtime errors
Node.js EACCES permission denied: causes and fixes | Error Atlas