a_n_d_y

Members
  • Posts

    90
  • Joined

Everything posted by a_n_d_y

  1. This is what I was going to use: https://www.amazon.com/gp/product/B011M8YACM/ Motherboard: https://www.supermicro.com/en/products/motherboard/A2SDi-4C-HLN4F I'll be backing often with the CA Backup plug-in to an external, but just wanted to make sure there weren't any unknown gotchas.
  2. Was considering the following: Using motherboard's internal USB 3.0 port and hooking up an SSD with a USB to Sata cable. I wanted to use Unassigned Disks to mount the SSD outside of the array just for docker AppData directories. Outside of maybe not getting the full disk stats, any concerns or known problems doing this?
  3. Looking for an Unraid docker template for ScPrime: https://hub.docker.com/r/scprime/scprime/ Cool crypto storage project focused on enterprise backup: https://scpri.me https://coinmarketcap.com/currencies/scprime/
  4. I think some of the PIA servers are having issues with Wireguard? I usually use Toronto CA, but had to change to Ontario CA to get it to work.
  5. No problems getting Wireguard with PIA working. Thanks!
  6. 1.) You could change port(s) on the other docker containers. I use a custom eth0 / br0 interface. This will put the container on its own IP, so it'll avoid port conflicts. I think you need to enable bridging if its not enabled by default. Settings > Network Settings > Enable Bridging Then that option should be available when editing the container. Custom interfaces are isolated from the host and other custom interfaces, so if you set it up this way and you need them to communicate with each other, this might be of some help:
  7. Did you update the firmware? Logs looked similar to mine before I updated the firmware. Again, for me personally, I had to run a firmware update on a Windows computer.
  8. Have you updated the firmware? I had to update mine in Windows. Its recommended to use a USB extension cable and be plugged into a USB 2.0 port. If you're still having issues I guess I would look over your docker logs to see if that gives you any indication of what's going on.
  9. Yes it is your container. I ended up changing docker containers to get it to work. Thanks!
  10. I see that and in mine it says serverPort: 1730. It seems port 8080 is being used in the container. I'm trying to change that to a different ports so I can use it with a VPN thats also using port 8080. Is that possible? Thanks,
  11. Where is the port setting in the config located?
  12. Same error message. I could not get it to work. I just set this up and seems to be working! https://github.com/syncarr/syncarr
  13. Nice! Just follow the integration for it here: https://www.home-assistant.io/integrations/deconz/ And the devices will pop up and be available in HA to do your bidding. Really easy!
  14. I believe sudo usermod -a -G dialout $USER adds the current user (root in your case) to the dial out group. The docker should be running under root unless your specifically assign it a different user to run under (I'm not sure how to do that, but I'm running mine with the default user fine). I used ls -l /dev/serial/by-id to get the serial ID. As long as you don't plug the Conbee into a different USB port than the one its in now in the future, what you have should work fine. Once you log into Phoscon > Hamburger Menu > Settings > Gateway, if it shows a firmware number, its connected. Otherwise it will say "not connected"
  15. In Community Apps, search for deconz and click the Click Here To Get More Results From DockerHub and install the container from marthoc. You'll want to set Network Type to Host. At the bottom of the page will be the link Add another Path, Port, Variable, Label or Device. It does what it says. Add the container path /root/.local/share/dresden-elektronik/deCONZ to point to your config directory, ex. /cache/appdata/deconz You'll also want to pass your device into the container. I just use the Extra Parameters field to do this: --device=/dev/[your_device] Then pass any of the environment variables you need listed on this page (passing them all is fine, just define the values): https://hub.docker.com/r/marthoc/deconz/ The Conbee II defaults to the device name /dev/ttyACM0. If you have another USB device like an Aeotec Zstick, it will also try to assign itself /dev/ttyACM0 or /dev/ttyACM1 (depends on which device is assigned first upon boot). Read this about setting a persistent name if thats the case: https://forums.unraid.net/topic/71372-usb-passthrough-device-location-changing/ Then add the Environment Variable DECONZ_DEVICE and enter the value of your persistent name, ex. /dev/[persistent_name] Make sure to telnet into your server and add the user to the dial out group the Drahznar suggested above. If you're having problems with the device connecting in the container, try updating the firmware. I did my firmware update in Windows as I couldn't get it to flash successfully using the docker firmware method described on the docker page. Attached is how I setup my container.
  16. 1. Yes 2. If Disk1 is part of the array, it will constantly be writing to the Parity drive. You might look into the Unassigned Devices plugin to add a disk outside of the array (you'll need another spare disk for this) and then move your completed download to the array. 3. Edit the docker, then click "Add another Path, Port, Variable, Label or Device" Change Config Type to "Path" Enter a Container Path, ex. /new_download_location Enter a Host Path, ex. /mnt/Disk1/Downloads Click save The path /new_download_location will show up inside of the container and it points to /mnt/Disk1/Downloads. Go into the qBittorent webui, Tools > Options > Downloads. Change Default Save Path to /new_download_location.
  17. Edit the docker container and put this into the repository field: binhex/arch-qbittorrentvpn:4.1.9-1-01 You can roll back to any release. Go to the Github page for the docker container and replace the text after the colon with the release number: binhex/arch-qbittorrentvpn:[release_number] If you want the latest release once an update that resolves these issues is available, change to: binhex/arch-qbittorrentvpn:latest
  18. If the docker is running, but the gui is not accessible, give this a try. Edit the container, change to Advance View and in the Extra Parameters, enter this: -e HOMEBRIDGE_CONFIG_UI=1 I don't think you actually need the variables HOMEBRIDGE_VERSION, CONFIG_UI_VERSION, HOMEBRIDGE_CONFIG_UI, HOMEBRIDGE_CONFIG_UI_PORT if you do the above. They don't seem to do anything after the initial installation.
  19. That stinks. Working over here fine. Might try removing the docker and image and then reinstalling with all the setting as is. Since the Config UI is just a plugin, if you have a running another Homebridge docker, could try just re-installing that plugin manually inside the docker container. Would be nice if someone was able to just port over OZNU's docker to be more Unraid compatible.
  20. OK I think I figured it out. Config UI X installs as a Homebridge plugin. It defaults to port 8080. You should update config.json manually for the port of the UI and then it should work.
  21. I happen to be using Network Type as Host instead of Bridge. You can either change it to Host or you'll have to pass the appropriate ports to the docker container (Homebridge service, GUI, possibly other stuff...) I believe that should do it.
  22. I'm not 100% sure since I have not had to debug anything. In the UI if you click on the docker icon (top right) > Settings, there are some options to Debug and run in Insecure. Looks like DEBUG=Alexa* is just filter? Might be something you could ask OZNU about.
  23. I can't directly help you with your question above. However, if you want to make using and managing Homebridge painless, including installing plugins, you should consider using the OZNU Homebridge docker. It has Homebridge Config UI X included: https://www.npmjs.com/package/homebridge-config-ui-x Community Apps > Search for "homebridge" > click "Click Here To Get More Results from DockerHub" Install oznu/homebridge Changes to Make: Repository: oznu/homebridge:latest Variables: /homebridge = homebridge appdata folder, ex. /mnt/cache/appdata/homebridge Enable UI: Add these variables HOMEBRIDGE_CONFIG_UI, set to 1 to enable HOMEBRIDGE_CONFIG_UI_PORT, set to 8080 or whatever port you want Then you can access the UI at the configured port above.
  24. a_n_d_y

    Node JS

    Anyone with experience running Node JS in docker? I tried using the official docker, but its not running. Not sure where to go from here.