L0rdRaiden

Members
  • Content Count

    388
  • Joined

  • Last visited

Everything posted by L0rdRaiden

  1. Fixed, it was a "Icon URL" link that was broken in one of the dockers. I have been breaking my head the last weeks with this problem, I tried everything and at the end... Maybe you could add something in fix common problems to detect this.
  2. No, thats error was from when I was tryting to fix it and I was playing around with the settings. Now if I run "fix common problems" I don't get that error anymore. Could it be because there is an icon from a docker container or something or a link that is called tha is down and it takes to long to resolve?
  3. Thanks in advance for helping me. file attached unraid-diagnostics-20191130-1204.zip
  4. In the dashboard tab I dont see dockers or VM after a while of openning the page. VM tab loads quickly and without any issue
  5. When I open the docker or apps tab it take like a minute or two to show the contents Anyone can help my to troubleshot this? I have tried everything related with DNS settings already.
  6. 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
  7. Maybe is related with the database corruption problems that Unraid 6.7 has. Is someone tuning storj in a old Unraid build?
  8. Let us know if you start a new node and my solution works for you, I might try to start a new node again
  9. 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
  10. 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.
  11. But that is basically the same than stopping the container from command line. I only want to do this with 1 container. Not all.
  12. @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
  13. 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?
  14. 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
  15. @binhex Can you add a simple file editor to the docker?
  16. 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
  17. @spants Can you include unbound in this docker to do this? https://docs.pi-hole.net/guides/unbound/
  18. 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?
  19. I took it from docker hub and configure it manually, if you copy my settings it will work I don't know how to do the template to have it in unraid apps
  20. Have you seen this? https://github.com/AdguardTeam/AdGuardHome https://github.com/AdguardTeam/AdGuardHome/wiki/Docker
  21. I have started a new dorcker from scratch, same config than always and It doesn't work, I can't reach the web interface Have been considered the latest changes? https://hub.docker.com/r/pihole/pihole/