Filesystem permission issue

Posted by user_ns2fg9 in general.

Hello Wispbyte Support, My Node.js Discord bot server has a filesystem ownership/permissions issue. NPM initially failed with: EACCES: permission denied, mkdir '/home/container/.npm' After changing the npm cache to /tmp/vyntra npm cache, it now fails with: EACCES: permission denied, mkdir '/home/container/node modules' I'm running Node.js 22.23.4. Could you please check and repair the ownership and write permissions of /home/container and its contents for the actual container runtime user (including .npm and node modules)? I cannot run sudo or chown from the server console. Thank you.

Replies

Byte

This is a write permission issue inside the server, not an npm cache path problem. Try a clean dependency install: 1. In Startup , use Reset to Default if you changed the startup command. 2. In Files , delete and if you can. 3. Make sure dependencies are listed in , then restart so they install again. If you can’t delete those folders, or persists, reply with the node name and support tag shown by the console, plus the relevant error lines (with tokens removed). See Startup Settings.

user_ns2fg9

There are no .npm or node modules folders visible in my Wispbyte File Manager, so I cannot delete them. I have already tried changing the npm cache to /tmp/vyntra npm cache, but npm now fails with: EACCES: permission denied, mkdir '/home/container/node modules' Could you please check the ownership and write permissions of /home/container for my container user? Also, please tell me the node name and support tag associated with my server so I can provide them if needed.

Wispbyte Community Forum