# Issue setting up second Storj node on Ubuntu 24.04 — permission error in /app/config/bin **URL:** \ **Category:** troubleshooting\ **Tags:** multiple-nodes, file-permissions\ **Created:** [November 20, 2025, 6:59pm UTC](https://forum.storj.io/t/issue-setting-up-second-storj-node-on-ubuntu-24-04-permission-error-in-app-config-bin/31160 "2025-11-20T18:59:46Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![cronos](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/cronos/32/1125_2.png) [@cronos](https://forum.storj.io/u/cronos)\ **Post date:** [November 20, 2025, 6:59pm UTC](https://forum.storj.io/t/issue-setting-up-second-storj-node-on-ubuntu-24-04-permission-error-in-app-config-bin/31160/1 "2025-11-20T18:59:46Z")
Hello community, About two months ago I configured my first Storj node (storagenode2) on a mini PC NUC running Ubuntu 24.04.3 LTS, using a 4 TB disk. Everything is working fine. Now I want to add a second node (storagenode3) using a new 16 TB disk mounted at /media/giga/DATA2. I already created the new identity and tried to run the initial setup command: **sudo docker run --rm -e SETUP=“true” –user $(id -u):$(id -g) –mount type=bind,source=/home/giga/.local/share/storj/identity/storagenode3,destination=/app/identity –mount type=bind,source=/media/giga/DATA2,destination=/app/config –name storagenode3 storjlabs/storagenode:latest** But at the end I get this error: **mkdir: cannot create directory ‘/app/config/bin’: Permission denied** I am not sure how to continue from here. Do I need to change permissions on the disk or use a different path? Another question: my first node is configured with **port 28967**. Can I use the same port for the second node, or do I need to configure a different one (e.g. 28968)? Thanks in advance for your help. Greetings from Nashville, ---
**Author:** ![elek](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/elek/32/9189_2.png) [@elek](https://forum.storj.io/u/elek)\ **Post date:** [November 20, 2025, 9:08pm UTC](https://forum.storj.io/t/issue-setting-up-second-storj-node-on-ubuntu-24-04-permission-error-in-app-config-bin/31160/2 "2025-11-20T21:08:42Z")
Docker creates the mounted directories with root user (first time) if dirs don’t exist, but you try to use user `$(id -u)`, which may not have the permission for the mounted directories. 1. Either create the directories yourself with the same user (too late, I guess) 2. Or you need to fix ownership (`chown -R ...`) > [@cronos](#): > > Another question: my first node is configured with **port 28967**. Can I use the same port for the second node, or do I need to configure a different one (e.g. 28968)? Choose a different port. Only one service can use one port. (Note: you need to update multiple places in config. Listening address / external address…) ---
**Author:** ![Roberto](https://storj.bcdn.literatehosting.com/letter_avatar/roberto/32/5_5575768a8748004e209b776fc1b2916d.png) [@Roberto](https://forum.storj.io/u/Roberto)\ **Post date:** [November 20, 2025, 10:52pm UTC](https://forum.storj.io/t/issue-setting-up-second-storj-node-on-ubuntu-24-04-permission-error-in-app-config-bin/31160/3 "2025-11-20T22:52:41Z")
> [@My docker run commands for multinodes on Synology NAS](https://forum.storj.io/t/my-docker-run-commands-for-multinodes-on-synology-nas/22034): > > These are all the useful parameters that one storagenode can use, and the modifications that I use for the second node. Fill free to use them or not, is up to you. I put them here fore easy reference. These work for Synology NAS and I run them in sudo su mode. There is also the --user $(id -u):$(id -g) parameter, but I started without it. It seems that dosen’t work on Synology NAS. OLD CONFIG: See UPDATED section for the recent version; also read the entire thread to get the picture. NODE 1… ---
**Author:** ![lyoth](https://storj.bcdn.literatehosting.com/letter_avatar/lyoth/32/5_5575768a8748004e209b776fc1b2916d.png) [@lyoth](https://forum.storj.io/u/lyoth)\ **Post date:** [November 21, 2025, 1:09am UTC](https://forum.storj.io/t/issue-setting-up-second-storj-node-on-ubuntu-24-04-permission-error-in-app-config-bin/31160/4 "2025-11-21T01:09:15Z")
I notice that when you use uid and gid in the docker command, it has problem downloading the binary, because it tries to download the binary into /tmp inside the container, which I believe is owned by root. Once it is download in tmp, it then gets moved to bin, folder. The solution I came up was to mount /tmp where your bin folder is located, which is in config/bin ---
**Author:** ![cronos](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/cronos/32/1125_2.png) [@cronos](https://forum.storj.io/u/cronos)\ **Post date:** [November 22, 2025, 10:32pm UTC](https://forum.storj.io/t/issue-setting-up-second-storj-node-on-ubuntu-24-04-permission-error-in-app-config-bin/31160/5 "2025-11-22T22:32:57Z")
I would like to thank everyone who replied to my first post about my Storj node. Your advice helped me move forward with the setup. I have now opened a new thread where I explain another issue I am facing with my second node. Here is the link in case you want to check it out and share your thoughts: > [@Second node issue: Peer ID did not match requested ID](https://forum.storj.io/t/second-node-issue-peer-id-did-not-match-requested-id/31171): > > Hello community, I am trying to set up a new node (storagenode16T) on my server, but I keep getting the following error in the logs: rpc: tls peer certificate verification: tlsopts: peer ID did not match requested ID Here is the exact procedure I followed: I created the identity with: identity create storagenode This generated the 4 files: ca.cert, ca.key, identity.cert, and identity.key. Then I executed the setup command as root, pointing to the exact location of the credentials (same w…