a_n_d_y

Members
  • Posts

    99
  • Joined

Everything posted by a_n_d_y

  1. I went from 5.14.23 to 7.1.68 a while back and only had to make some adjustments to the AP Groups, so I can confirm that worked in my situation. I've upgraded to 7.3.83 since then. Hope that helps.
  2. Just upgraded from 7.2.95 to 7.3.83. Everything went smooth and seems to be looking good. I do have an UAP-AC-IW, but its being powered off a USW-Lite-16-PoE, so no problems.
  3. Every once in a blue moon after rebooting my server, containers on a custom network like br0 are not accessible. Rebooting has always fixed it for me.
  4. @slughappy1 This container is just for the UniFi Network Controller. For hosting UniFi Protect, you need either the Cloud Key Gen2 Plus (this is what I use), UNVR or one of the UDM Pro models.
  5. Finally made the leap from 5.14.23 to 7.1.68 today without any problems. Just had to update the AP Groups to get everything like how it was. Not the biggest fan of the updated UI.
  6. Its working! Thank you very much!
  7. On the My Servers Dashboard, the last time it updated was yesterday. In Unraid, flash backups is showing as Activated: Not up-to-date Clicking the update button doesn't seem to be doing anything. I've tried signing out, reinstalling, rebooting, reinitializing... not sure where else to go from here. Any help is appreciated, thank you.
  8. I just tried manually installing the docker scan, but couldn't get it to work.
  9. I found this tool from Docker: https://github.com/docker/scan-cli-plugin#how-to-build-docker-scan Haven't installed it or know if its applicable to Unraid.
  10. 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.
  11. 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?
  12. 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/
  13. 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.
  14. No problems getting Wireguard with PIA working. Thanks!
  15. 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:
  16. 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.
  17. 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.
  18. Yes it is your container. I ended up changing docker containers to get it to work. Thanks!
  19. 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,
  20. Where is the port setting in the config located?
  21. 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
  22. 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!
  23. 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"
  24. 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.