Jcloud

Don't have to, but if you want to just go up in the thread to my example of making a node, that address is the eth address I'm using for Storj. HAHA too late! Before I was on unraid I lost 14.5BTC from a currupted password file, from a failing HD. I've cried many tears over this.

Cool beans. I just got my head wrapped around multiple nodes and been playing around with the template. I think I can make a bash script to incorporate reloading nodes on an container update or reboot of container, but still have some kinks in it so I haven't posted anything yet. do you increment your nodes when you make them or do they all have the same port? I've incremented mine, but seeing your instructions I'm wondering if I need to.

*ME* Baby-steps figured out how to even do more nodes. ... "Baby-steps get on the bus" -- What about Bob? My not 100% sure it's possible with how the unRAID docker templates work, but I'll keep learning as I go. If I can, I will. That is weird about your config file, at least it hasn't happened since. I can definitely see more nodes needing more resources. Hmm, I wonder how it scales? Also have to be careful, not to accidentally flood one's router with open TCP connections. Other hand, could get nasty and start packet--shaping one's network. You mentioned maxed node size, I could see that, probably a demand-side sort of issue, also I bet bandwidth have to be some racing upload speeds. Which describes no American consumer grade ISP.

Well I figured out how to do this: In theory one could do this for N-number of nodes. What I have NOT yet figured out, can this be done through unRAID web interface? Can I start all the nodes at once or would I need a script? (presently I'm betting on a shell script) ┌─────────────────────────────────────────────┬─────────┬──────────┬──────────┬─────────┬───────────────┬─────────┬──────────┬───────────┬──────────────┐ │ Node │ Status │ Uptime │ Restarts │ Peers │ Allocs │ Delta │ Port │ Shared │ Bridges │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ 09ecfee3004001336fc2050531a55695ed326ee3 │ running │ 1h 21m … │ 0 │ 139 │ 18 │ ... │ 4000 │ 17.76GB │ connected │ │ → /storj/share │ │ │ │ │ 0 received │ │ (uPnP) │ (1%) │ │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ a403eadbdb8d7b6521e78aff82ef4213eb08e92b │ running │ 2m 32s │ 0 │ 133 │ 0 │ 235ms │ 4001 │ ... │ connected │ │ → /storj/Node_2 │ │ │ │ │ 0 received │ │ (TCP) │ (...%) │ │ └─────────────────────────────────────────────┴─────────┴──────────┴──────────┴─────────┴───────────────┴─────────┴──────────┴───────────┴──────────────┘ For those that would like to try and setup multiple nodes here are the steps: The official instructions are here (used sections 3.3 - 3.5) In your /mnt/user/storj/ share create sub folders, one for each node want to setup. root@HYDRA:/mnt/user/storj/# mkdir Node_1 Make addition port-forwards in your firewall, i.e 4001, 4002 for each node you're going to make. docker exec Storj storjshare-create --storj 0xe09a2b205d3a76196a88505f059c78df7d7c556f --storage /storj/Node_1 --size 500GB --outfile /storj/Node_1/config.json --rpcaddress 0.0.0.0 --rpcport 4001 --manualforwarding true --logdir /storj/Node_1 where 0xe09a2b205d3a76196a88505f059c78df7d7c556f is substituted for YOUR wallet address! Also want to take out 0.0.0.0 and replace it with what you use. For each node you'll want to increment the port, such that each node has a unique port. For each node you create, remember to change the /storj/Node_# path. Then you start the node manually docker exec Storj storjshare start --config /storj/Node_2/config.json That's all I have for now, I'll try and expand upon it later.

Out of curiosity where did you make and save this change to on your system? I saw ntp pool fields, and in /boot I saw /boot/config/ident.cfg which looks like a master config file for unRAID. I know you're relatively new to unRAID L0rdRaiden, so I'm checking to see if you may have edited /etc/ntp.conf? Wanted to double-check that you knew /etc/ gets rebuilt (afaik) every time your server is rebooted. UNRAID works as a live-boot-disc. And thinking back on your past thread was that what you meant before about your config file being randomly cleared?

Nope, unRAID auto-checks and I get notices, of when my installed containers need to be updated, but I manually push the update. An artifact of functionality, when I first installed unRAID, never bothered to change because it suites me fine. Saw it a while ago durring 6.4-rc in settings, but didn't flip the switch, I'll have to go looking again as it's probably worth doing and not being bothered by it.

I've notice something like this before, and clicking on the update container function a lot of times does seem to kick start going again. The repository is auto-built every eight, or was it twelve, hours according to the page. I hadn't figured out how to check/test a hypothesis (one part video-games, another part getting over flu and no energy/focus), which is after an update or two, docker client gets dropped by the network because it's not current. EDIT: Yes, I know it shows up as "up-to-date" in the unRAID webui, no clue why it behaves this way, another item on my mucking-to-do list. Although if anyone has a glimmer of insight, I'm "all ears." Glad to read things are moving towards working for you.

Oh yeah BIG BUCKS! No WAMIES! -- The preliminary Feb payout sheet is out, looked up my address, that $1.54 is all mine. Bwhahaha! 0xe09a2b205d3a76196a88505f059c78df7d7c556f FALSE 20137.06237 167784886 1.543409036 Feb, 2018 - Storj preliminary payout sheet.

Mine is the exact same. It looks like the size field doesn't have the comma, because it's the last uncommented item in the list; so if you were to add something below it, then yes it would need a comma -- you could always try adding one though, and restart the storj service, couldn't hurt (AFAIK).

Question, question, and more questions -- I may have gotten over my head. >.< I have this issue all the time, I have a good delta at the begining but it end up with the 3 dots after a while. I think delta is latency between your node and the bridge (not 100% certain on this fact), but if you're getting 3 dots after a while then your network is closing off your connection and it's timing out. I don't think you'll get any Allocs until this is resolved. In a past post you mentioned something about a pfsense VM what sort of router(s)/routing platforms are you currently using? Storj's instructions are here: https://docs.storj.io/docs/storj-share-daemon-cli looks like starts around section 3.4. The general idea I get from it is to make a series of subdirectories with modified copies of config.json file; once the storj daemon is running, you can load additional config-files/nodes. I dub thy @physikal expert in this, since judging by his question he's already made it this far. I haven't bothered this far yet, life and energy has gotten in the way. I didn't think the docker command would work, but it was the first thing I could think off off the top of my head. Presently, I don't have an answer for you sorry man. Not sure why, if you are going to "edit" in unRAID webui and then clicking on Apply this might be your source of the config file changing on you. Lastly, I want to apologize for my sub-par support, I'm a user too, and you guys are asking some good questions.

Is that using CA Backup/Restore appdata plugin? If so I'd just add Storj to the exclusionary list. AFAIK everything about the docker is kept in the /storj share. I don't know about you by my /mnt/user/appdata/storj directory is empty. You could also try adding: --exec="Storj storjshare load" In the "Post Arguments" field in the advanced view of the template, docker container runs with this, but I don't know if its actually running the exec, so give it a shot if you like. I'll keep digging for a better answer. I hope this helps.

As a concept, what about using a Mini-SAS to 4-sata port cable for the "unR" in unRaid; like cursive script lines but each line is part of the cable. Top-left of "u' would be the mini-sas port; line goes down bends to form the curve; the top right of the "u" is one of the Sata-ends. The bundle of 3 sata cables tails out of "u" and starts lower "n" goes up, cruves over and down to form the 'n' and terminates with another sata-port. Last two ends could form the "R." Too busy? Anyways just an idea I'll leave here for those with talent to send to trash or exploit and use.

Yeah, I found someone's Docker app of Cacti and setup made a template for it. It's in the Community Apps selection now if you want to grab it and try it. I'd say based on response to it, consider it alpha/beta in function.

Well it is an ICO, so on hand sketchy already, and Storj still has to prove the concept both technically (easy) and as a business (much harder) in reality. But, I don't disagree with your point, for me I'm sitting on empty space, so miserly rate is easily accepted on my end. I don't know if the container supports it, but if it does I may. First off that's for the Storj GUI client, in case you missed that, but everything covered there is more about networking between your Storj node to the internet. We're unRAID community, I doubt you have host sitting on the edge of the network on the public side, So it's going to use Tunnel or UPnP. I have ports forwarded on my router to host for Storj and status still reports "UPnP,." ┌─────────────────────────────────────────────┬─────────┬──────────┬──────────┬─────────┬───────────────┬─────────┬──────────┬───────────┬──────────────┐ │ Share │ Status │ Uptime │ Restarts │ Peers │ Allocs │ Delta │ Port │ Shared │ Bridges │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ 09ecfee3004001336fc2050531a55695ed326ee3 │ running │ 8h 44m … │ 0 │ 101 │ 21 │ 20ms │ 4000 │ 9.1GB │ connected │ │ → /storj/share │ │ │ │ │ 2 received │ │ (uPnP) │ (0%) │ │ └─────────────────────────────────────────────┴─────────┴──────────┴──────────┴─────────┴───────────────┴─────────┴──────────┴───────────┴──────────────┘ If you're expecting digits to just start flooding in, it's more like watching digital paint drying. If status = running AND Bridges=connected AND Peers > 0; Storj is working and on the Storj cloud. "Shared" is cumulative and, for me, moves at the rate of paint drying or grass growing. The important thing now, as far as I can tell, is being UP (uptime).

Yeah this is amusement and learning how to use Docker for me. So the earnings are extra to me -- I'm curious about the numbers I'll see, but any fiat money is gravy to me. I have empty space on my array, so, "why not?" for me. Simple Docker; almost as good as "hello world" learning how to use Docker.

Sorry, spelling has never been my strongest suite. To peek, peer, look at. Or in command line using something like: more, less, cat, or nano commands (or n-more) to view the file.

Looks right. If you don't want it throught uPnP see Nuhll note about editing confi.jason file. Might be worth double checking, peaking at the config.jason file to make sure everything looks right in there. It's all waiting now. For web interface, not with what Storj provided, and I'm not that good at programming to write my own at this time. I like to use console history to just re-exec the command, or could make it into a shell script simply enough.

Just fixed the typo thanks! I also noticed that the template settings act almost more as initial settings, I had increased the max size of my "share" on template, but noticed status was more with old size. I'm think I'm following out what you where pointing out before with the config.jason holding more importance over the template settings. 24th? that was the start of my flu, can I blame it on that? ... nah, that was my bad looking back.

You're right about the reason, and in networks there could be multiple kinks.I too also run a pfsense router (external box not as a docker), and I made my noted change and my Docker status went from Tunnel to uPnP; you do need to click on "apply" rather then "save" when you change the template. I also noticed that just clicking on, "save," and restarting the container, did nothing to change the port status.

The Docker reports tunneling due to a choice I made making template, If you want to remove that tunnel, in the template settings change "Network Type" from, "Bridge" to "Host" and then remove "Storj network ports" (which is a port forward from host to container, the source of your tunnel). I'm running it on the host port, I did notice the reported Delta went down; perhaps I made a bad setup choice. My logic at the time of setup, was that containers should be fully contained, also thought it would make potential port conflicts easier to change/explain on forums. Sorry nuhll I don't have those numbers yet, just been doing this for about the last few weeks myself -- for something to tinker with and learn how to setup Docker containers. Okay to be fair I have space, but not payout, I've allocated 3TB to Storj Daemon since the time of my OP I've shared 8.02GB. Willing to report back that number once payout occurs. I simply made a template, which launches the stock Storj container, but I'll see about maybe taking things to next level and making a custom repo with stats. May be a while, we shall see what life throws at me.

Sorry about confusion, you definitely don't have one there. Here's mine: https://i.imgur.com/EUpZqzl.jpg And, yeah 'apply' definitely re-builds it each time. I think the save button is activated, by going to ://YourBox/Apps/ca_settings Advanced "Enable Template Developer Mode?" --> Change to Yes and apply.

Looks fine to me, looks like you've been allocated two units, but you're correct, you haven't gotten any data yet. As far as I'm aware, this is nominal behavior, but just in case Storj community has an active chat channel, Storj Community jump page. You could post screenshot of the status, and ask the question, if there is something wrong they'll know for sure. If there is something that needs to be tweaked on the template, certainly can do that.

Good call. I had seen requests in forums, and was just trying to fulfill, I may have I opened a large can of worms. I've actually run into the issue you mention, GMAIL flags everything I've sent as SPAM. The bigger issue has been receiving email. Emailing from outside to Poste has resulted in no delivery/stuck in mailserver queue (not bounced). It's been over 15 years from the last time I've worked on a mail server, DNS, and delivery systems.

Application Name: Poste.io <==> "SMTP + IMAP + POP3 + Antispam + Antivirus + Web administration + Web email ... on your server in ~5 minutes." Application Site: https://poste.io/ Docker Hub: https://hub.docker.com/r/analogic/poste.io/ Template-Repository: https://github.com/Jcloud67/Docker-Templates INITIAL SETUP: 0. Requires registered FQDN to send/receive external email. 1. Following ports are used by container for mail: 25, 110, 143, 443, 465, 587, 993, 995 2. Following ports are used by container for webui: 443, 8280 (These may conflict, check your ports) 3. Make a user share for mail data, default is /mnt/user/poste 4. Some or all mail ports may need to be opened, forwarded, or dmz for mail send/receive to work. Optional arguments -e "HTTPS=OFF" To disable all redirects to encrypted HTTP, its useful when you are using some kind of reverse proxy (place this argument before image name!) NOTE: Marked as BETA, simply because author is not an expert in email exchange servers -- software itself looks pretty good.

Interesting, I'm also running on a user share myself (no cache drive) and it is working, allocated 3TB in Storj, two disks for unRAID user share. So far Storj has only given me 6GB of data. I wonder what the differences are? You're welcome to post the your unRAID diags from the tools menu. Perhaps that might shed some light on differences between yours and mine. I made the user share via unraid web interface first, then start the Docker, that way unRAID had what permissions it wants for the folder -- because it made it.