L0rdRaiden

if I click on dashbaord or type https://192.168.1.200/Dashboard This sends me to the login page. -> https://192.168.1.200/login Also I get this on the error log, probably not related Oct 19 19:13:13 Unraid root: error: /plugins/dynamix.docker.manager/include/UpdateConfig.php: wrong csrf_token Oct 19 19:13:15 Unraid root: error: /webGui/include/Notify.php: wrong csrf_token Oct 19 19:13:15 Unraid root: error: /plugins/dynamix.docker.manager/include/UpdateConfig.php: wrong csrf_token Oct 19 19:13:16 Unraid root: error: /plugins/dynamix.system.temp/include/SystemTemp.php: wrong csrf_token Oct 19 19:13:16 Unraid root: error: /webGui/include/Notify.php: wrong csrf_token Oct 19 19:13:23 Unraid kernel: veth1870321: renamed from eth0 Oct 19 19:13:24 Unraid kernel: eth0: renamed from veth1fa4c7e Oct 19 19:13:37 Unraid root: error: /plugins/dynamix.docker.manager/include/UpdateConfig.php: wrong csrf_token Oct 19 19:13:41 Unraid root: error: /webGui/include/Notify.php: wrong csrf_token Oct 19 19:13:41 Unraid root: error: /plugins/dynamix.docker.manager/include/UpdateConfig.php: wrong csrf_token Oct 19 19:13:41 Unraid root: error: /plugins/dynamix.system.temp/include/SystemTemp.php: wrong csrf_token Oct 19 19:13:41 Unraid root: error: /webGui/include/Notify.php: wrong csrf_token Oct 19 19:13:43 Unraid root: error: /plugins/dynamix.docker.manager/include/DockerUpdate.php: wrong csrf_token Oct 19 19:13:44 Unraid root: error: /plugins/dynamix.docker.manager/include/UpdateConfig.php: wrong csrf_token Oct 19 19:13:47 Unraid root: error: /plugins/dynamix.docker.manager/include/DockerUpdate.php: wrong csrf_token Oct 19 19:13:47 Unraid root: error: /plugins/dynamix.docker.manager/include/UpdateConfig.php: wrong csrf_token Oct 19 19:13:48 Unraid root: error: /plugins/dynamix.docker.manager/include/DockerUpdate.php: wrong csrf_token Oct 19 19:13:48 Unraid root: error: /plugins/dynamix.docker.manager/include/UpdateConfig.php: wrong csrf_token Oct 19 19:13:51 Unraid root: error: /plugins/dynamix.system.temp/include/SystemTemp.php: wrong csrf_token Oct 19 19:13:55 Unraid root: error: /plugins/dynamix.docker.manager/include/UpdateConfig.php: wrong csrf_token Oct 19 19:14:01 Unraid root: error: /plugins/dynamix.docker.manager/include/UpdateConfig.php: wrong csrf_token Oct 19 19:14:02 Unraid root: error: /webGui/include/Notify.php: wrong csrf_token Oct 19 19:14:02 Unraid root: error: /plugins/dynamix.docker.manager/include/UpdateConfig.php: wrong csrf_token Oct 19 19:14:02 Unraid root: error: /webGui/include/Notify.php: wrong csrf_token Oct 19 19:14:02 Unraid root: error: /plugins/dynamix.system.temp/include/SystemTemp.php: wrong csrf_token

Maybe is related with the database corruption problems that Unraid 6.7 has. Is someone tuning storj in a old Unraid build?

Let us know if you start a new node and my solution works for you, I might try to start a new node again

I have the same problem 3 times database became corrupted. The problem might be because storj database needs more time to close correctly everytime the docker is shutdown or restarted. Storj recommends 300 seconds Unraid by default is much lower, I don't remember the value This might not be a problem when you don't have a lot of data but when you have many Gb the database probably needs more time and then the docker is killed by Unraid while the database is still doing things. One solution should be to configure this docker to with more time https://docs.docker.com/engine/reference/commandline/stop/ But I don't know how to do it

Does it really matter?

I know I can do this docker stop -t 300 DOCKERNAME but what I want is to implement this somewhere so is the default behaviour when I click on the docker and then click stop is this.

But that is basically the same than stopping the container from command line. I only want to do this with 1 container. Not all.

@limetech I would need to do the same, the database of the Storj Docker keeps get corrupting becuase the timeout is too short. I could shut it down manually but it would be great to be able to customize the timeout for this docker in particular, or for all of them, whatever is easier. Is there a way to do this without you requiring you to modify unraid? Stopping the container from the interface with a bigger timeout Thanks

No one else is having this problem? the docker apparently works but it stops to update the IP after a week or so. Is there an automatic way to restart the docker every day?

I have updated the docker, and somehow it failed in the middle of the process because docker isn't able to kill the container. The icon was there before I can't stop the container manually I can't delete the container This is the log e":"can not get logs from container which is dead or marked for removal"} If I stop the docker service it doesn't work because docker service can kill this container so the service can stop. What can I do? unraid-diagnostics-20190628-0757.zip

@binhex Can you add a simple file editor to the docker?

There are many plugings made by the community covering basic options that should be available out of the box in Unraid. Have you consider integrate\absorb them in a future? How do you plan to finance Unraid in the future? How is working so far with the lifetime licenses? Can you give a tentative roadmap of the product? Or at least a few hints of what you are working on

@spants Can you include unbound in this docker to do this? https://docs.pi-hole.net/guides/unbound/

Lately I'm having the same problem, DuckDNS looks like it works but is not updating the IP when it changes. Did you find a solution?

Any help here?