NewDisplayName

OKay, i have news, 3 days ago i startet the docker again and let it run. Till now it seems to work. Storage Node Dashboard ( Node Version: v0.20.1 ) ====================== ID 1XXXX Last Contact 2s ago Uptime 1h47m12s Available Used Egress Ingress Bandwidth 20.0 TB 0 B 0 B 0 B (since Sep 1) Disk 2.0 TB 0 B Bootstrap bootstrap.storj.io:8888 Internal 127.0.0.1:7778 External XXX:28967 Neighborhood Size 178 Seems to work again? Even with version ..... but no data till now.

cool, sadly no balance feature

hahaha, ive run 11 nodes (v2) for around a year and only made under 3usd worth of shit So its not about the money, but they could atleast fix their shit when we run their buisness

BTW! I found out why this program "sometimes" from one day to other day stopped working. Your licence is only up to a special version. So lets say u buy version 1.0 then you get till version 1.1 free, when the container updates to 1.2, your setup stops working... So, be sure to dont use auto update on this container, or this command in "extra parameters" (without quotes ofc) "--restart=unless-stopped -e VERSION='18.11.21'" (the version should be the highest you payd for) Since i changed this, this docker works flawlessly. @coppit I think you should add that to the first page

I have the problems with storj, but not with plex...^^ (i think most reported it with plex database?) but yeah, might be docker + unraid error.... And shouldnt it be fixed already!? (or not?) Ill never understand why companys dont start from bottom to top. Why add new features and new clients and new everything when the ground is not propperly working / feature less. There is no real statistic, no controll for UL / DL, no planned downtime. The whole process for this node is so useless complicated... and it should be suited for home users, not tech ppl (thats what they advert with)

this whole crap annoys the shit out of me. the old node worked for years without problems and now this. Same shit like you cant put dl/ul limits on it. like wtf, its 2019. If they dont fix their node they dont deserve us. removing it for the time beeing. if anyone has news, ill might try again. I dont think its unraid related, but who knows. @limetech sadly didnt responded. Thanks for all your help.

Lets say i host a 1gb file, and stteam e.g. via ftp or plex or httpd... and another download (file access) would start... would it be clever and use cached data or start a new download from google? Like are 100 1gb downloads 100 individual streams, or can cache be used?

U can set the kill time in ca auto update/backup. I dont see how storj is the only app on this planet which "Perhaps it's related to how this platform is mounting the disks. Looks like the container started earlier than the filesystem is ready and the" wtf? @limetech Isnt docker standardized, were not using a special unraid docker, am i right!??!

just to give some feedback, it works for some time (maybe a day?) and then the node is offline. I hate this whole crap. Why something cant just work? Or just not work? But how both? Storage Node Dashboard ( Node Version: v0.0.0 ) ====================== ID Last Contact OFFLINE Uptime 17h57m7s Available Used Egress Ingress Bandwidth 20.0 TB 0 B 0 B 0 B (since Aug 1) Disk 2.0 TB 0 B Bootstrap Internal 127.0.0.1:7778 External :28967 Neighborhood Size 174

If u have the mountcheck file crypted on your google drive, all is working. Atleast the transfer. What happens if u use the upload script? All dirs correct? Did you try to restart server and let the scripts automatic run on startup?

Ok, glad you found out.

and it didnt worked? u have to plan again?

Or... u just use "install the fix comon problems plugin, then run the docker safe new permissions command"

Please follow the tutorial in the first post, if you do it like descriped it works. ALl your questions are answered there too.

Dont upload it to google drive direct, let the script upload it.

Again: They download from your Server, your server download from cloud. For plex its just a normal folder. When something accesses it, it gets streamed from cloud.

I dont understand your questions, why should plex pass be needed? Do you need plex pass for your current plex server? Oo "n order to preserve my files I could just copy them to the upload folder correct? Then point Plex to the cloud drive. This would then take the load off of my server and place it on the clients. Correct on this?" I dont know what you mean. Files in upload folder get uploaded and then local removed. Again: if you follow this tutorial, the files in the cloud appear like a normal directory on your server/software, you can / cant do the same things. This setup is not meant as backup, if you ask that. Its replacing local files with cloud files. For clients only bottleneck is your upload speed. The deal here is, that you get unlimited storage for a buck...

1. cloud -> server -> family 2. see 1 but u can "link" unlimited plex server sto the same drive (which would be pretty dumb if u ask me) 3. transcode or not depends on the client, like a normal plex installation. just remmeber the whole thing appears to be a normal directory for your server/software, thats the whole deal.

Im not sure if it was that, how far i understand docker storjlabs/storagenode should always mean storjlabs/storagenode:latest anyway... (also it didnt download anything new...) Seems to work now flawlessly. Thanks. Do you also have version 0 in docker exec -it storagenode /app/dashboard.sh ?

Thats 100% nothing mover would do, as far as i know. It will only do that if you write new files to unraids system, which unbalance does bypass... (then maybe a mode without bypassing unraids "file balancing" system?) You just need to be sure to write to a share where the specified source disk is not part of. But if im right, that would also not work, because (im not sure) you are not allowed to write from mnt disk to mnt user ?!? (or lets say you shouldnt) Edit: ill guess you could go around that problem by doin so cp "file" from mnt disk to mnt user "file.something" and if that is successfull, remove old file and rename file then. But easier would be a balance mode

What about my idea?

Lol just tested it again. Old (jclouds) version works just fine (online and it shows node dashboard 0.0.0.17 or something), the official version shows 0.0.0.0.0.0 and offline... edit: okay after i startet the old node and then the new mode it works now. (same dirs) but still shows 0.0.0... I also changed storjlabs/storagenode to storjlabs/storagenode:latest, one of the things did it. Lets see how it works out.

Sorry, my idea has nothing to do with a shedule function, its a new mode for unbalance. (like gather)

Hmm, now im getting: rpc error: code = PermissionDenied desc = info requested from untrusted peer and the status shows offline? "No bootsrap address specified {"STORAGE": " is normal, right?

What about my suggestion?