clowrym

Members
  • Posts

    550
  • Joined

  • Last visited

Everything posted by clowrym

  1. CLick force resart and a window should pope up, your looking for this: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='MineOS-node' --net='bridge' -e TZ="America/Denver" -e HOST_OS="Unraid" -e 'USER_PASSWORD'='password' -p '25565-25575:25565-25575/tcp' -p '8443:8443/tcp' -p '8120-8126:8120-8126/tcp' -p '25565:25565/udp' -v '/mnt/cache/appdata/minecraft/':'/var/games/minecraft':'rw' -v '/mnt/cache/minecraft':'/mnt/data':'rw' 'hexparrot/mineos' 479fd653a593c9ed8f3c2b7e150b6c26e540c50b6cb593d4964337fad4dace05 Also, can you check the user:group on the folders / subfolders, they all should be 1000:1000 per below
  2. While I do run a couple server's, ive never run into any of these issues, Typically when I have had issue with starting servers, it was either user:group issues of the files within the mount points, or share mapping. Can you post your docker run command? Beyond any glaring issues there, you could also post an issue HERE
  3. Did you change the admin password? Should be mc & password if i remember correctly.
  4. looks like everything is up to date, but I did have a notification this monring about updating auto update, i guess i'll wait for the next jackett update and see what happens!! thanks for the response!!
  5. Having a problem the last few days with Jacket & updates, For some reason after an update, it wont automatically restart. Tried toggling the automatic start button, but doesnt seem to make a difference.
  6. I wonder if your issue is related to this? https://github.com/haugene/docker-transmission-openvpn/issues/764
  7. I can Help you with setting up the Docker etc, but I've only created the templates, if your having issues that dont relate to docker template settings, you can post HERE. One thing to note, if you arent Using PIA for your provider, you need to change the entries in the "OPENVPN_CONFIG:" variable to suit your providers config file names, they can be found HERE in your providers folder.
  8. Is your PUID & PGID set to 0 for a reason? I dont know if it will make a difference, but usually I keep my dockers at PUID=99 AND PGID=100.... thats the only thing that looks a little off to me
  9. can you post a screenshot of your docker template settings?
  10. I've been getting a weird error everytime I update Docker container's, Specifically I've noticed it with the Plex container, Always starts the same with Duplicate device, followed by intelpowerclamp... No Idea how to trouble shoot this one!! Mar 13 10:23:15 Tower kernel: BTRFS warning (device md4): duplicate device fsid:devid for 16d6aaf7-f0d9-419d-ac06-d0351d960bdb:1 old:/dev/md4 new:/dev/sdt1 Mar 13 10:23:16 Tower kernel: BTRFS warning (device md1): duplicate device fsid:devid for 1b8fa8ee-850f-48f2-8614-af47d6577726:1 old:/dev/md1 new:/dev/sdi1 Mar 13 10:23:35 Tower kernel: BTRFS warning (device md8): duplicate device fsid:devid for fe834164-5e8e-4dad-8ad1-3186ed9ca15d:1 old:/dev/md8 new:/dev/sdm1 Mar 13 10:23:35 Tower kernel: BTRFS warning (device md4): duplicate device fsid:devid for 16d6aaf7-f0d9-419d-ac06-d0351d960bdb:1 old:/dev/md4 new:/dev/sdt1 Mar 13 10:23:35 Tower kernel: BTRFS warning (device md6): duplicate device fsid:devid for e5144b2d-b213-4aae-8b7a-07a4556cae15:1 old:/dev/md6 new:/dev/sde1 Mar 13 10:23:35 Tower kernel: BTRFS warning (device md2): duplicate device fsid:devid for 0983df5e-c2c3-413d-ab3e-a00d88e8cf0a:1 old:/dev/md2 new:/dev/sdo1 Mar 13 10:23:35 Tower kernel: BTRFS warning (device md5): duplicate device fsid:devid for fe9954eb-fe72-400e-9e51-a93a620db2b6:1 old:/dev/md5 new:/dev/sdp1 Mar 13 10:23:35 Tower kernel: BTRFS warning (device md1): duplicate device fsid:devid for 1b8fa8ee-850f-48f2-8614-af47d6577726:1 old:/dev/md1 new:/dev/sdi1 Mar 13 10:23:35 Tower kernel: BTRFS warning (device md3): duplicate device fsid:devid for ef88f475-319d-426d-b02d-89353e6cc2be:1 old:/dev/md3 new:/dev/sdf1 Mar 13 10:23:35 Tower kernel: BTRFS warning (device md2): duplicate device fsid:devid for 0983df5e-c2c3-413d-ab3e-a00d88e8cf0a:1 old:/dev/md2 new:/dev/sdc1 Mar 13 10:23:35 Tower kernel: intel_powerclamp: No package C-state available Diagnostics attached tower-diagnostics-20190313-1632.zip
  11. easiest way to to add it through community apps....
  12. When I set up the template I added all that were available at the time, you can add additional ones at any time here: When I get some time, I will try and add any new ones to the template.
  13. just to confirm your trying to access the gui from a 192.168.1.XX ip address?
  14. I dont imagine it will make much of a difference, this is an issue I've had since the plugin came out!!
  15. didn't work for me.....no sensors to select
  16. I tried deleting both & reinstalling...but ended up still having the same issue
  17. Tried manually running the sensors command and seeing what error it returns. I get the following: Error: File /etc/sensors.d/sensors.conf, line 2: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 4: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 14: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 16: Undeclared bus id referenced sensors_init: Can't parse bus name I removed the sensors.comf files and I can then reload the drivers and I can select the Temps I want to see, but as soon as I hit apply, The sensors drop down goes blank again & I get the same error as above if I run the command manually....
  18. DId you add your local network properly? ie. 192.168.1.0/24 or whatever local network your using? Also, are you trying to access it from within your network? If not then you have to add whatever network's you want to access it from.
  19. make sure "advanced view" is on for your docker template and add --dns 8.8.8.8 to the extra parameters
  20. I have a 24 bay SM server & a 10 bay tian server, as well as 2 24 port switched, my router & fibre modem all plugged into my 2700w UPS which gives me the following usage. Just set up graphana and started tracking it, as I always wondered as well what its costing me!! the specs of my server is in my sig.
  21. I've been trying to use this plugin for a while on one of my servers I always get the following: Jan 30 11:48:28 Tower kernel: i2c /dev entries driver Jan 30 11:48:33 Tower kernel: i2c i2c-0: found f75373 version: 20 Jan 30 11:48:33 Tower kernel: f75375 0-002d: hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info(). Jan 30 11:48:33 Tower kernel: i5k_amb i5k_amb.0: hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info(). Jan 30 11:48:33 Tower kernel: w83627hf: w83627hf: Found W83627HF chip at 0x290 Jan 30 11:48:33 Tower kernel: w83627hf w83627hf.656: hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info(). Jan 30 11:48:33 Tower kernel: w83793 0-002f: hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info(). Jan 30 11:48:33 Tower kernel: w83793 0-002f: Registered watchdog chardev major 10, minor: 130 If I go and manually try and run sensors I get this after the plugin has finished its detect: Error: File /etc/sensors.d/sensors.conf, line 2: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 4: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 14: Undeclared bus id referenced Error: File /etc/sensors.d/sensors.conf, line 16: Undeclared bus id referenced sensors_init: Can't parse bus name I have removed, tried commenting out the lines with issues and I can get sensors to work properly at command line, but not in the plugin... Any ideas?
  22. havey you set userid's etc in the docker template?
  23. no...... I wasn't sure if I removed petersm's plugin if it would affect the UI
  24. Downloaded THIS, placed in the /boot/extra folder & added a script to run after start of array. #!/bin/bash cd /boot/extra installpkg openvpn-2.4.6-x86_64-2.txz I tried just adding it to the extra folder and rebooting, but it still installed the older version requiring me to do an installpkg after.....