[Support] QDirStat, Jcloud - cryptoCoin templates


Recommended Posts

Application Name: QDirStat   --   Graphical view of directories, find files taking up the most space. Real MovieOS stuff!

Application Site: https://github.com/shundhammer/qdirstat

Docker Hub: https://hub.docker.com/r/mjdumont1/qdirstat

Template-Repository: https://github.com/Jcloud67/Docker-Templates

 

UI is through RDPclient, youTowerName:33389

Template defaults /mnt/user/ on host, as the container location /files/.  

 

 

 


Application Name: Storj.io daemon

    What is Storj?  https://www.storj.io/

Application Site: https://github.com/Storj/storjshare-daemon/ 

    The command line version, of this.

Docker Hub: https://hub.docker.com/r/oreandawe/storjshare-cli

Template-Repository: https://github.com/Jcloud67/Docker-Templates

 

   Storj is a Crypto-asset and P2P cloud storage service. This Docker runs the back-end client for Storj allowing internet users to rent their disk space and earn STORJ an Ethereum asset.  @Jcloud makes no guarantee that STORJ or ETH will retain, or increase in fiat value.** This is only the Storj Daemon and CLI tool. 

 

SETUP REQUIREMENTS:
-------------------------------------
    1.   TCP ports 4000 open on host and setup on container (should be set below)

          Ports 4001-4003 are used to tunnel a connection if 4000 is closed, but this typically results in no data being shared.  Port(s) 4001++ are used when running multiple nodes.
    2.   Path on host for Storj data to sit.  IE: make a user share,  /mnt/user/storj  or similar.
    3.   Your Ethereum-based wallet address.
    4.   The max allowed space STORJ can take up on the host; remember to make it less than space available on host.  (500MB, 1000GB, 1TB, 8TB   Note 8TB is maximum size per node)  

  

 

STORJ DAEMON STATUS:  (In your command line)
 

docker exec Storj storjshare status

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

Application: Storj daemon + CLI tools; storjstat.com monitor script   (a fork of the official repo, which is above).   . . . OR Rate My Storj 

Application Site: https://github.com/Jcloud67/docker-storjshare-cli

Docker Hub: https://hub.docker.com/r/zugz/r8mystorj/

Template-Repository: https://github.com/Jcloud67/Docker-Templates

 

   This repository, or Docker container, is in response to forum feature requests. Requests, which couldn't done easily without the source. 

features:

  • Base container you all know: Storj DAEMON + CLI tools.  
  • Installed, storjstat.com monitoring script AND a place for users to put  API-key in the template on webui!  (DOES NOT YET AUTO-LAUNCH)
  • Now supporting building and launching of multiple farming nodes, AND a place for users to put it in the template on webui! 
  • Improved webui template, from lessons learned in past two months.
  • Changed default network type from Bridge to Host (seemed to work out better for most and/or preferred) *feature? A change.*
  • Auto launch of storjstat.com monitor script, and staying on.

 

Currently working on, or trying to improve:

  • Saving storjshare state after loading multiple nodes.  entrypoint seems to do this for me.
  • auto-building updates on some periodic function.

 

Setup requirements are the same as Storj. Running the storjMonitor and/or multiple farming nodes are optional. 

 

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Sia-Coin

Sia-coin website:                                     https://sia.tech/
Sia-coin client utilities:                           https://sia.tech/get-started
Docker hub site:                                       https://hub.docker.com/r/mtlynch/sia/
Original Docker install instructions:     https://blog.spaceduck.io/sia-docker/
Repository site:                                        https://github.com/mtlynch/docker-sia
Template site:                                           https://github.com/Jcloud67/Docker-Templates

   Sia-coin, from their website, “Sia is a decentralized storage platform secured by blockchain technology. The Sia Storage Platform leverages underutilized hard drive capacity around the world to create a data storage marketplace that is more reliable and lower cost than traditional cloud storage providers.” 
   
   *** DISCLAIMER *** I have no affiliation with Sia-coin or Mr. Lynch. I was asked if Sia was possible? I found someone already invented the wheel, I just made the hub-cap.  I do not guarantee, nor will hold any responsibility, for loss or corrupted data; or that Sia-coin (Sia), Bitcoin (BTC), or any other “crypto-currency” will gain or maintain their current fiat value.

 ***  Please, with any and all, “ICO’s,” “exchanges,” “tokens,” and cryptos’ do exhaustive research before any transaction. ***

SETUP:
 1.   User share for Docker data, I just called it, “Sia”:

Example
Screenshot_2018-05-03_22-17-19.thumb.jpg.239afbc7816b7be56c1e7ffe936dc180.jpg

 

2.  Punch hole in firewall for outside to your docker's ip address, TCP ports 9981 and 9982. 

   DANGER! : Sia also uses TCP port 9980 for command & control, do NOT expose 9980 outside of your network! Failure to follow this rule can result in wallet and Sia host hijack.

 

3.  Download the Sia client from download URL, if you want a GUI experience.

4.  Setup Sia template and docker container on unRAID using CA store.

Sia4.thumb.jpg.62e09286d05302b66481a39f8f380ec0.jpg

Sia5.thumb.JPG.be812ea6747bb507de9c2a5b887588ae.JPG

5.  For GUI clients, running on a VM or on the LAN:

Start the Client and Click on "About"Sia0.thumb.JPG.c7239b44a43057a45eb29743a672c259.JPG

 

Sia1.thumb.jpg.76344e4b22f6b5c85b674136fec8e9c0.jpg

 

After closing Sia client, and the file manager opened to Sia's configuration files, edit the config.json file

Change "detachted": false, to    "detached": true,

In the "address" line change "127.0.0.1" to your IP address of your Sia container.

Save config.json file.

 

Sia2.thumb.jpg.2671ce905bc886046f3c1048b9d3b1d7.jpg

 

When you Restart Sia, it should connect to your docker:

Sia3.thumb.JPG.49f9ddcb50f73bb3caa90815ca886913.JPG

Edited by Jcloud
New template docoumented
  • Like 1
Link to comment

when i setup your storj container with unRaid 6.4.1 i get this error in the container log:
 

created directory: '/storj/share'
created directory: '/storj/log'

* starting daemon in foreground


* configuration written to /storj/config.json

failed to start node, reason: invalid storage size

my config looks like this and for me at least it looks ok:
 

{
  // Set the STORJ/ERC20 wallet address for receiving contract payments
  "paymentAddress": "private",
  // Subscribes to the given contract topics
  // See https://storj.github.io/core/tutorial-contract-topics.html
  "opcodeSubscriptions": [
    "0f01020202",
    "0f02020202",
    "0f03020202"
  ],
  // An array of bridges to connect and accept contracts,
  // send exchange reports and discover network seeds.
  "bridges":[
    {
      "url": "https://api.storj.io",
      "extendedKey": "private"
    }
  ],
  // Known preferred seeds in form of a storj URI
  // Example: "storj://[ip.or.hostname]:[port]/[nodeid]"
  "seedList": [],
  // Interface to bind RPC server, use 0.0.0.0 for all interfaces or if you
  // have a public address, use that, else leave 127.0.0.1 and Storj Share
  // will try to determine your address
  "rpcAddress": "0.0.0.0",
  // Port to bind for RPC server, make sure this is forwarded if behind a
  // NAT or firewall - otherwise Storj Share will try to punch out
  "rpcPort": 4000,
  // doNotTraverseNat: true requires you to have an external ip address.
  // You can use a proxy to gain an external IP address.
  // doNotTraverseNat: false Enables NAT traversal strategies
  // first UPnP, then reverse HTTP tunnel
  // if that fails. Disable if you are public or using dynamic DNS
  "doNotTraverseNat": false,
  // Maximum number of tunnels to provide to the network
  // Tunnels help nodes with restrictive network configurations participate
  "maxTunnels": 3,
  // Maximum number of concurrent connections to allow
  "maxConnections": 150,
  // If providing tunnels, the starting and ending port range to open for
  // them
  "tunnelGatewayRange": {
    "min": 4001,
    "max": 4003
  },
  // Number of times to retry joining the network and the wait time between
  "joinRetry": {
    "times": 3,
    "interval": 5000
  },
  // Temporarily stop sending OFFER messages if more than this number of shard
  // transfers are active
  "offerBackoffLimit": 4,
  // ECDSA private key for your network identity, your Node ID is derived from
  // this and it is used to sign and verify messages
  "networkPrivateKey": "private",
  // Determines how much detail is shown in the log:
  // 4 - DEBUG | 3 - INFO | 2 - WARN | 1 - ERROR | 0 - SILENT
  "loggerVerbosity": 3,
  // Path to write the log file to disk, leave empty to default to:
  // $HOME/.config/storjshare/logs/[nodeid]_date.log
  "loggerOutputFile": "/storj/log",
  // Directory path to store contracts and shards
  "storagePath": "/storj/share",
  // Amount of space to lease to the network, as human readable string
  // Valid units are B, KB, MB, GB, TB
  "storageAllocation": "12TB"
  // Max size of shards that will be accepted and stored
  // Use this and make this lower if you don't have a strong internet connection
  // "maxShardSize": "100MB"
}

Can you see what i'm missing here? 

Thanks in advance for your help and your containers!

Link to comment
6 hours ago, DaLeberkasPepi said:

when i setup your storj container with unRaid 6.4.1 i get this error in the container log:
 


created directory: '/storj/share'
created directory: '/storj/log'

* starting daemon in foreground


* configuration written to /storj/config.json

failed to start node, reason: invalid storage size

my config looks like this and for me at least it looks ok:
 


{
  // Set the STORJ/ERC20 wallet address for receiving contract payments
  "paymentAddress": "private",
  // Subscribes to the given contract topics
  // See https://storj.github.io/core/tutorial-contract-topics.html
  "opcodeSubscriptions": [
    "0f01020202",
    "0f02020202",
    "0f03020202"
  ],
  // An array of bridges to connect and accept contracts,
  // send exchange reports and discover network seeds.
  "bridges":[
    {
      "url": "https://api.storj.io",
      "extendedKey": "private"
    }
  ],
  // Known preferred seeds in form of a storj URI
  // Example: "storj://[ip.or.hostname]:[port]/[nodeid]"
  "seedList": [],
  // Interface to bind RPC server, use 0.0.0.0 for all interfaces or if you
  // have a public address, use that, else leave 127.0.0.1 and Storj Share
  // will try to determine your address
  "rpcAddress": "0.0.0.0",
  // Port to bind for RPC server, make sure this is forwarded if behind a
  // NAT or firewall - otherwise Storj Share will try to punch out
  "rpcPort": 4000,
  // doNotTraverseNat: true requires you to have an external ip address.
  // You can use a proxy to gain an external IP address.
  // doNotTraverseNat: false Enables NAT traversal strategies
  // first UPnP, then reverse HTTP tunnel
  // if that fails. Disable if you are public or using dynamic DNS
  "doNotTraverseNat": false,
  // Maximum number of tunnels to provide to the network
  // Tunnels help nodes with restrictive network configurations participate
  "maxTunnels": 3,
  // Maximum number of concurrent connections to allow
  "maxConnections": 150,
  // If providing tunnels, the starting and ending port range to open for
  // them
  "tunnelGatewayRange": {
    "min": 4001,
    "max": 4003
  },
  // Number of times to retry joining the network and the wait time between
  "joinRetry": {
    "times": 3,
    "interval": 5000
  },
  // Temporarily stop sending OFFER messages if more than this number of shard
  // transfers are active
  "offerBackoffLimit": 4,
  // ECDSA private key for your network identity, your Node ID is derived from
  // this and it is used to sign and verify messages
  "networkPrivateKey": "private",
  // Determines how much detail is shown in the log:
  // 4 - DEBUG | 3 - INFO | 2 - WARN | 1 - ERROR | 0 - SILENT
  "loggerVerbosity": 3,
  // Path to write the log file to disk, leave empty to default to:
  // $HOME/.config/storjshare/logs/[nodeid]_date.log
  "loggerOutputFile": "/storj/log",
  // Directory path to store contracts and shards
  "storagePath": "/storj/share",
  // Amount of space to lease to the network, as human readable string
  // Valid units are B, KB, MB, GB, TB
  "storageAllocation": "12TB"
  // Max size of shards that will be accepted and stored
  // Use this and make this lower if you don't have a strong internet connection
  // "maxShardSize": "100MB"
}

Can you see what i'm missing here? 

Thanks in advance for your help and your containers!

It looks like you are allocating 12TB correct? 

Have you tried with less? 

Link to comment
5 hours ago, Micaiah12 said:

It looks like you are allocating 12TB correct? 

Have you tried with less? 

 

I think Micaiah12 beat me to the answer. How big is your storj unRAID user share does it have 12TB of free space?  If you do have 12TB of free space, but it's chopped up between all your disks try the largest value of a given disk chunk. 

 

Perhaps it's an error trying to allocate over the disks (possible but I doubt it).  I've been running the program for myself, only for the last week or so.

Link to comment
4 hours ago, DaLeberkasPepi said:

i got it working by selecting /mnt/diskX/ as location instead of the user share and setting the size to the free space of that hdd. But that would mean i have to make one docker container per disk i want to use for storj...

Have you tried to select less storage space then 12TB in the user storage? I am going with 1TB right now, it's recognizing the storage through the user share for me. 

Link to comment
9 minutes ago, DaLeberkasPepi said:

yeah i tried everything down to 1gb but only worked when i switched to /mnt/disk13/storj instead of /mnt/user/storj

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.

4 minutes ago, DaLeberkasPepi said:

did you let the docker create the storj folder under /mnt/user ?

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. 

Edited by Jcloud
Link to comment

I installed this docker when released & followed the guide to get operational...but it doesnt seem to be doing anything?

 

I have 500gb shared on my UD drive w/ the access mode set to R/W slave, ports 4000-4003 on pfsense opened and mapped to internal IP

 

Daemon says it is connected but I dont see any data being stored.  Any tips?

Capture.PNG

Capt1ure.PNG

Link to comment
On 2/18/2018 at 5:51 PM, DaLeberkasPepi said:

ok i found the problem now!
i had to create the storj on every drive i wanted to use so for me to be able to use the 12TB i had to create the folder on at least 3 of my 4TB drives. Then it could properly recognise the available space available to storj

 

 

I think you may be running into a limitation of the storj CLI

See attached doc from storj FAQ/guides

Capture.PNG

Link to comment
6 hours ago, therapist said:

Daemon says it is connected but I dont see any data being stored.  Any tips?

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. 

Link to comment
6 hours ago, therapist said:

I installed this docker when released & followed the guide to get operational...but it doesnt seem to be doing anything?

 

I have 500gb shared on my UD drive w/ the access mode set to R/W slave, ports 4000-4003 on pfsense opened and mapped to internal IP

 

Daemon says it is connected but I dont see any data being stored.  Any tips?

Capture.PNG

Capt1ure.PNG

Have you updated the config of storj in the storj share? If you open the config there is good documentation where your public/DDNS should be entered. 

Link to comment
On 21.2.2018 at 1:50 PM, therapist said:

 

 

I think you may be running into a limitation of the storj CLI

See attached doc from storj FAQ/guides

Capture.PNG

yeah i noticed that also, thanks for posting it here for the rest. I still dont know why also my storj docker uses tunnel despite the fact that i also forwarded the ports in pfsense to the docker....

Link to comment

WoW crazy, sounds cool.

 

Can someone share some earnings? +how much space +bandwidth? (dont want to make money with it, but if its only 1 cent a month, i dont need to do it... ) 

 

To the creator of the docker, could you add the statistic addon for it also? :D

 

edit:

 

good, i test it with 1TB from EU.

 

For statstic i found https://storjstat.com which works without any extra addon, perfect.

 

So far nothing happend, but it seems they have technical issues atm. 

Edited by nuhll
Link to comment

 

12 hours ago, DaLeberkasPepi said:

yeah i noticed that also, thanks for posting it here for the rest. I still dont know why also my storj docker uses tunnel despite the fact that i also forwarded the ports in pfsense to the docker....

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.

 

2 hours ago, nuhll said:

Can someone share some earnings? +how much space +bandwidth? (dont want to make money with it, but if its only 1 cent a month, i dont need to do it... ) 

 

To the creator of the docker, could you add the statistic addon for it also? :D

 

edit:

 

good, i test it with 1TB from EU.

  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.

Edited by Jcloud
  • Upvote 1
Link to comment
15 minutes ago, Jcloud said:

 

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).

 

 

Im not sure, but i think thats wrong!

 

Tunnel means it cant reach the port. Thats for sure. But it has nothing to do with network type bridge or host.

 

Its because your standard config is "wrong".

 

I changed it this way: 

 

Quote

 


"rpcAddress": "EnterYourStaticIPorDNS.de",
  // Port to bind for RPC server, make sure this is forwarded if behind a  // NAT or firewall - otherwise Storj Share will try to punch out
  "rpcPort": 4000,  // doNotTraverseNat: true requires you to have an external ip address.
  // You can use a proxy to gain an external IP address.  // doNotTraverseNat: false Enables NAT traversal strategies
  // first UPnP, then reverse HTTP tunnel  // if that fails. Disable if you are public or using dynamic DNS
  "doNotTraverseNat": true,
 

 

 

After i just c hanged this. And port forwarded port 4000 - 4003 to the unraid machine, all is working without tunnel. No need to change network type, but i guess, you could change it if you want it.

 

Just btw u also have a typo in the descriton from the docker template, there u say port forward port 400- 4003 ;)

 

Edited by nuhll
  • Upvote 1
Link to comment
2 minutes ago, nuhll said:

Im not sure, but i think thats wrong!

 

Tunnel means it cant reach the port. Thats for sure. But it has nothing to do with network type bridge or host.

 

Its because your standard config is "wrong".

 

I changed it this way: 

 

 

Quote

 

 


"rpcAddress": "enteryourstaticipordns.de",
  // Port to bind for RPC server, make sure this is forwarded if behind a  // NAT or firewall - otherwise Storj Share will try to punch out
  "rpcPort": 4000,  // doNotTraverseNat: true requires you to have an external ip address.
  // You can use a proxy to gain an external IP address.  // doNotTraverseNat: false Enables NAT traversal strategies
  // first UPnP, then reverse HTTP tunnel  // if that fails. Disable if you are public or using dynamic DNS
  "doNotTraverseNat": true,
 

 

 

 

 

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.

Link to comment

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. :)

Edited by Jcloud
typos
Link to comment
10 minutes ago, L0rdRaiden said:

I have set it up and it looks like it's working, right?


Do I have to do something else? or now is just a matter of waiting? xD

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.

 

Link to comment
  • Jcloud changed the title to [Support] QDirStat, Jcloud - cryptoCoin templates

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.