MrChunky

Stroj is working as expected with multiple nodes and reporting to StorjStat for me now:) So good job all around @Jcloud. I am looking into SIA now and I got the docker installed, ports forwarded. When I open terminal within unraid gui for that docker (new feature in unraid), I tried a few commands and I just cannot find how to interact with it. Tried host commands and siad comands, nothing found. how do you do it? The GUI shows syncing activity but the daemon says unreachable from terminal... I am still syncing so that might be the issue? Figured it out: Have to use ./siac to access terminal commands from within UnRaid docker terminal. e.g.: ./siac -h ./siac folder add /sia-data/xxx 8TB Or from SIA UI terminal: ./siac --addr xxx.xxx.xxx.xxx:9980 ./siac --addr xxx.xxx.xxx.xxx:9980 host folder add /sia-data/xxx 8TB Also don't forget to port forward both TCP and UDP... Took me a while to figure that out. There is a small mistake in your instructions: False and True should be the other way around

What do you mean by restore the GUI? Is that a specific action? Thanks for the quick reply

Got myself a new weird problem. Apps tab is missing. When I try to directly access IP:Port/Apps I just get a blank page. In Plugins section the community applications plugin is looking strange: I am running Unraid v 6.5.1-rc6. Nothing of note in Syslog... some PHP warnings... Any help would be much appreciated.

I am running both repos, and its the same situation. I presume the network was being tested, and now its not. This is why the alocs are basically 0, not because of the repo. If you read the subreddit, everyone is in the same boat.

Sorry for the spam. I was thinking that it would make sense (to me) to not start the main node that resides in the root folder and only start additional nodes. It would make the folder structure make more sense, as all nodes will be in respective sub folders. Also potentially avoid complications with debugging several conditions (main/ additional nodes).

Yep, sorted it out. Unassigned devices runs under nobody on the /storj folder. Changed perms to root and its all good now.

In my case, when I set it to False, I get UPnP connection. When it is set to true I get TCP. All my nodes are set to do not traverse and working fine. I have a floating rule for the ports on PfSence since I wanna circumvent pfblockerng geo blocking.

It is container with a single node that existed previously on ht old template. But I am getting the same error on the completely new nodes I also just restarted an old mode in host mode, to check that it is not the problem and I have the same error. The only other thing I changed in the config is: Do Not Traverse NAT to True. * starting node with config at /storj/config.json {"level":"info","message":"got status query","timestamp":"2018-04-21T07:21:34.665Z"} [07:21:34] 94fc2d886f6c664a20f55f8c357c189775f79a46 | Submit to Storjstat [07:21:34] ERROR {"error":"Invalid farmer data (spaceUsedBytes)"}

Played around with a new docker. Thanks a bunch for getting this done. 1. Firstly, I think that bridge still works better. If I try to run multiples of the new docker (e.g. I want to share unassigned devices and main storage) the second docker tries to launch with the same IDs as the first in Host mode. Not a problem in Bridge mode. 2. Secondly the storagemonitor is not working for me. I get: * starting daemon in foreground {"level":"info","message":"attempting to start node with config at path /storj/config.json","timestamp":"2018-04-20T07:05:12.296Z"} * starting node with config at /storj/config.json {"level":"info","message":"got status query","timestamp":"2018-04-20T07:05:12.498Z"} [07:05:12] 94fc2d886f6c664a20f55f8c357c189775f79a46 | Submit to Storjstat [07:05:12] ERROR {"error":"Invalid farmer data (spaceUsedBytes)"} {"level":"info","message":"got status query","timestamp":"2018-04-20T07:16:41.768Z"} {"level":"info","message":"got status query","timestamp":"2018-04-20T07:16:56.028Z"} {"level":"info","message":"got status query","timestamp":"2018-04-20T07:20:12.528Z"} [07:20:12] 94fc2d886f6c664a20f55f8c357c189775f79a46 | Submit to Storjstat [07:20:12] 94fc2d886f6c664a20f55f8c357c189775f79a46 | Error {"level":"info","message":"got status query","timestamp":"2018-04-20T07:20:41.421Z"} {"level":"info","message":"got status query","timestamp":"2018-04-20T07:35:12.628Z"} [07:35:12] 94fc2d886f6c664a20f55f8c357c189775f79a46 | Submit to Storjstat [07:35:12] 94fc2d886f6c664a20f55f8c357c189775f79a46 | Error ... This node does however have stored data: ┌─────────────────────────────────────────────┬─────────┬──────────┬──────────┬─────────┬───────────────┬─────────┬──────────┬───────────┬──────────────┐ │ Node │ Status │ Uptime │ Restarts │ Peers │ Allocs │ Delta │ Port │ Shared │ Bridges │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ 94fc2d886f6c664a20f55f8c357c189775f79a46 │ running │ 3h 40m … │ 0 │ 162 │ 42 │ 2ms │ 4000 │ 13.5GB │ connected │ │ → /storj/share │ │ │ │ │ 4 received │ │ (TCP) │ (0%) │ │ └─────────────────────────────────────────────┴─────────┴──────────┴──────────┴─────────┴───────────────┴─────────┴──────────┴───────────┴──────────────┘ All the numbers are blue in my storjstat website. Not sure what other details I can provide to diagnose this... 3. Another thing is that I tried to migrate multiple nodes to the new docker. The first node (that is in the root folder) gets the stored data identified properly in the terminal with "storjshare status" command. The extra nodes do not get existing data shown properly, although they connect fine. This could be peculiarity of my setup as I ran the nodes of unassigned devices in R/W Salve mode...

Looking good, I got the nodes up and running from the latest docker! How do you check that the storjmonitor is reporting properly? Everything is up, but I don't see any changes on StorjStat.com... Probably need to wait for someone to actually put things on the share

I would really appreciate that too. If you are in too deep, you could possibly ask someone on the forums like aptalca, who has a lot of experience with dockers to look over it.

Wouldn't this docker implementation completely circumvent the limits storj imposed on the number of nodes being limited by the number of cores on one machine?

I have been looking at my firewall and it looks like the tunnel ports are indeed unused. Keeping the whole range open for now.

What you define in the json file only affects the docker internally. What you are showing in the image above are the ports you have forwarded to the docker when you created it. To me it looks like you need to change the ports in the template configuration to what you want e.g. 4000-4003, 4004-4007 etc. (step 4 in what I posted above). If this is not fixing your problem, I would guess that there is some issue on your side unrelated to Storj...

@L0rdRaiden That's because your containers are in host/br0 modes. They need to be in bridge modes. the container port field is only relevant in bridge mode.

@L0rdRaiden You need to first enable the advanced view and switch the container networking from host to bridge. You should then be able to see all the options you need. The screen shot of my view is in the post above.

Figured out fool proof way to add additional nodes using multiple containers. I was not able to find the Storj container using community apps plugin, so here is how I did it: 1. Add repository (address field with red arrow) and click "Add Container" 2. You will then see the container/docker configuration screen. Here you need to delete the line with address (red arrow) and switch to advanced view in the top right corner. 3. Then switch from Host to Bridge 4. Add storage location again (you have to use separate folders for each storj container/ docker) and the network ports you plan to use (I used a field of 4 ports for each container: 4000-4003 for container 1, 4004-4007 for container 2 etc.) 5. Launch the docker, then shut it down immediately and edit the config file located in the folder you pointed to earlier. Edit the following fields: "rpcAddress": "yourdomain.ddns.com", "rpcPort": 4000, "doNotTraverseNat": true, "tunnelGatewayRange": { "min": 4001, "max": 4003 }, 6. Now you can relaunch the container. Everything should run fine... I have 3 running now... I think some steps are possibly unnecessary like deleting the storage field before reentering it as well as using 4 ports for each docker and specifying the tunneling ports. This config worked for me though, so here you go. Don't forget to forward your ports though the NAT and the firewall.

@nuhll How long did you run for in total to get to 5000? Do you guys think auto update should be off, since the server will shut down for the update and hence will not be up 24/7? How would that affect updates in general?

Now you have the same error as me:) Welcome to the club.

Strange that we are all getting different errors. I have "Connection refused". you have something else. A third guy is get "unauthorized". I was getting your error until I changed the HTTPVAL value, now I get connection refused.

Apply the fix that Jasgud/ aptalca suggested above

I have what seems like the same problem, so I applied the suggested fix. FYI the required variable is set to false by default in the docker config already. There is no need to add a new variable, just change the existing one. But, I am getting connection refused on port 80. Should I change something in the nginx config as well? Domain: www.xxx.com Type: connection Detail: Fetching http://www.xxx.com/.well-known/acme-challenge/xxx: Connection refused Here is my current nginx config... port 80 listening seems to be enabled as per instructions. server { listen 80; server_name www.xxx.com; return 301 https://$host$request_uri; } server { listen 443 ssl default_server; root /config/www; index index.html index.htm index.php; server_name www.xxx.com; Edit: I have figured out that the problem started after the last update of letsencrypt docker. Still don't know how to fix it.

Just took some screenshots of the openfiles plugin. 12000 files open Gonna shut that down until its fixed.

OMBI is keeping thousands of files open, which is leading to the system becoming unstable (running out of allowed open files limit). Is this expected behaviour, or can this be fixed somehow in the future? I can provide logs if it is necessary.

I have increased the inotify value yet again. I haven't had the locking up behavior since. Not sure if it solved the problem, but I haven't seen it for a while. Thanks for the suggestions.