physikal

Anyone else have any issues with the cameras disconnecting daily? I don't have backups running or anything like that, that would shut down the docker. Seems like 2 o'clock on the dot is when it happens.

@Jcloud Just realized you wrote up a node guide. I noticed you used mkdir as root on the host. Let me know if you have any problems with that. When I did that, every node directory I made had host perms that the docker didn't have permissions to, so when trying to run the storjshare load command via docker container it didn't have permissions to load the other nodes outside of the initial load the docker container made. So check out my step 1. Just an FYI for when you pimp this thing out

Same, and I don't like wasting ports so I keep it slim. Thanks again!

lol, I don't think of it like that. If I sent you ETH now, I HOPE it goes up for you. Sorry for your loss. Use l0rd's ports, he seems to know more about the ports than I do though my current setup is working fine.

Sorry, missed this other question. Yes, node folder and port increment. I typically give each node a 2 port jump. So node 1 is 4000, 2 is 4002, 3 is 4004, etc. Just in case.

Nice! What's your ETH address so I can donate? I appreciate all you're doing. Makes my life 10x easier.

Hey there nuhll. Storj Documentation is here: https://docs.storj.io/docs/storj-share-daemon-cli The steps I used to create additional nodes (bare w/ me, off the top of my head): Docker config: Container Name: Storj Host Directory: /mnt/user/storj Docker Directory: /storj | config is /storj/config.json Additional nodes: /storj/node2 /storj/node3 /storj/node4 The reason I have so many nodes is max storage for a node is I believe 8TB, so I have each node sharing 7TB. Step 1: Create node directories with docker exec so it has the docker perms on the folder (this matters later when you load the snapshot) command: docker exec containername mkdir /storj/nodeX Step 2: Create the next node command: docker exec containername storjshare create --storj yourERC20addresshere --storage /storj/node2 --size 7TB --outfile /storj/node2/config.json --rpcaddress xxx.xxx.xxx.xxx(IP or hostname here) --rpcport 4004 --manualforwarding true --logdir /storj/node2 Run docker exec containername storjshare status to check if the node is running. If the node is not running run this command: docker exec containername storjshare start --config /storj/nodeX/config.json Step 3: Saving snapshot Once you have all the nodes running that you want, make sure you save the state by typing: docker exec containername storjshare save What this allows you to do is start all the nodes with one command after you reboot your unRAID server, or the container. command: docker exec containername storjshare load That load command loads the previously saved state of all nodes running. Hope this helps!

All good man! I appreciate the support and you building a sweet docker for us. I'll do my best to answer the question on multiple nodes to help you support this thang

Thanks Jcloud - I tried both of these and neither worked for some reason :\

How would I get this container to run storjshare load automatically after the container restarts? I have it running 4 nodes and when my appdata backup schedule hits, it stops the container and restarts it but it only loads the first node and not the other 3 unless I load the snapshot with "storjshare load". Full command is docker exec Storj storjshare load. Thanks!