2nd Node Port Issue

[dankmonty]

Hi all. I read somewhere that I have to run “-p 28968:28967” command instead of “28967:28967” when trying to set up my 2nd node. I’ve done this but am still not able to get my node online. Should "-e"port be 28968 or 28967? Any other insight appreciated.

Thanks

[Alexey]

Please, take a look

Setting up second machine with storj on same network

Ok, those two responses seem to contradict each other, yet they are both correct. When the outside world is trying to reach a specific node, it basically has to go through a few steps. I’m going to include docker in case you want to use it on the other system or in case someone else with a docker setup has the same question. Single node setup outside world => 28967 => router => 28967 => node machine [ => 28967 => docker container] Since all the ports are the same, you can just…

[dankmonty]

So I have the router set up to fwd 28968 -->28968, then have the docker command as below. The two nodes seem to be fighting over the 28967 port still. Been playing with it and can’t figure it out… If you see anything I’ve missed please let me know

docker run -d --restart unless-stopped -p 28968:28967 -e WALLET=“XXXXXXXXXXXXXXX” -e EMAIL="XXXXXXXX@gmail.com" -e ADDRESS=“XXXXXX.ddns.net:28968” -e BANDWIDTH=“100TB” -e STORAGE=“500GB” --mount type=bind,source=C:\Users\User\AppData\Roaming\Storj\Identity*storagenode2*,destination=/app/identity --mount type=bind,source=D:\Storj,destination=/app/config --name storagenode2 storjlabs/storagenode:beta

[Alexey]

Please, check the second identity: https://documentation.storj.io/dependencies/identity#confirm-the-identity

Make sure that you added the 28968 port to the inbound firewall rule to allow traffic to it

[dankmonty]

Ended up just using 28968 for everything for the 2nd node instead of 28968:28967 and it seems to be working… Not sure why it was instructing me to have 28968 changed to 28967 which is already occupied by the first node… documentation is kind of confusing

[Alexey]

It’s depends on version and setup:

Setting up second machine with storj on same network

Ok, those two responses seem to contradict each other, yet they are both correct. When the outside world is trying to reach a specific node, it basically has to go through a few steps. I’m going to include docker in case you want to use it on the other system or in case someone else with a docker setup has the same question. Single node setup outside world => 28967 => router => 28967 => node machine [ => 28967 => docker container] Since all the ports are the same, you can just…

So, if -p 28968:28968 is working for you, then you changed for some reason the server.address: :28967 to server.address: :28968 too.
It’s not needed in case of docker, then the port mapping -p 28968:28967 will work.