• Posts

  • Joined

Everything posted by KnifeFed

  1. Check if you have "/boot/config/plugins/user.scripts". If so, your scripts should be in the "scripts" folder there, which you can back up and then re-install the plugin.
  2. There are pre-built binaries of bat that you can just put somewhere in your path, in the meantime.
  3. I have qBittorrent run a script upon download completion, so it runs from within the container. In this script I can `curl http://<server ip>:<container port>` of one container without issues, but for another one, it fails to connect and times out. If I replace `<server ip>` (e.g. with `<internal container ip>` (e.g. it works fine for both containers. Does anyone know why that is? All containers are on the same custom Docker network. Also, `curl http://<container name>:<container port>` works from within all containers except binhex-qbittorrentvpn, where I get `Could not resolve host: <container name>`. Any way to get container name resolution working?
  4. Node v14.13.0 is built-in to Unraid 6.9.2. If you need a newer version, run it in a Docker container.
  5. No need for that. You can run them directly like: bash /boot/config/plugins/user.scripts/scripts/<name>/script
  6. I think it's been down for a while now. is a good alternative.
  7. That's exactly what you should do Never create directories straight in `/mnt/user` because Unraid will treat them as user shares, which is all fucky.
  8. You should definitely fix that. Where are your appdata folders "spread around"? Usually one would want all appdata under `/mnt/user/appdata` (or `/mnt/cache/appdata`, only if you have a cache pool). When you create a new container, you need to make sure `/config` (or whatever the mount point is called in the particular image) points to `/path/to/appdata/<name of container>`. This usually happens by default when installing from a CA (i.e. not directly from e.g. Docker Hub). Go to `/Settings/DockerSettings` in the web UI and check that `Default appdata storage location` is what you expect it to be. If not, choose `Enable Docker` -> `No` to shut down the Docker service and then you'll be able to change that path. After that, enable Docker again.
  9. It sounds like you're not using the actual CA template. It's named "plex-utills" but if you search for that, you won't get any results. You have to search for "plex utills", i.e. without the hyphen.
  10. Happy new year, buddy. The config is in /root/.config/bashtop
  11. Just extract the CA_backup.tar file and you'll have every data folder separately so that you can restore whichever files you want.
  12. Could it be that it's a dependency of some other package? Mine might come from Fish shell.
  13. Doesn't it come default with Unraid? Otherwise I don't know why I have it: $ which jq /usr/bin/jq $ jq --version jq-1.6
  14. All my containers are on the bridge network, except binhex-plexpass which is on host.
  15. Hi, I've had a few (infrequent) kernel panics and I'm wondering what might be the cause. Here's a photo of what it said on screen when it happened just now: I've successfully completed Memtest twice, first during initial build in early '21 and again after adding more RAM a few months ago. It's ECC RAM. I've attached my diagnostics. I would appreciate any insight, thanks.
  16. On it says "Go to the community apps plugin page on your unraid server and search for Plex-Utills and click install.". If you search for "Plex-Utills" in CA, nothing comes up. You have to search for "plex utills" without the hyphen. Not sure why.
  17. Right, but why add it to the CA template, is what I'm saying.
  18. Because Unraid adds the TZ variable to all containers by default (based on what you have your timezone set to on http://<SERVER>/Settings/DateTime). @jkirkcaldy How come this template sets a duplicate TZ variable?
  19. ^To fix the font, you can do: .ca_readmore { font-family: unset; } .ca_readmore::before { font-family: FontAwesome; }
  20. I really wish you hadn't removed the Docker Hub integration. I realize the templates were pretty bare-bones but it at least filled out the name, description, repository etc. making it a lot faster than going to the Docker page, manually adding a container and starting with a completely blank template.
  21. The post right above yours is actually me saying a reboot did fix it
  22. Edit folder -> "Add another button" -> "Config type:" "Docker Action" -> "Action:" "Start/Stop/Restart"
  23. The fix was to reboot the server. Who would have thunk it?
  24. It seems that in May, the release notes decided to travel back in time