KnifeFed

Members
  • Posts

    72
  • Joined

Everything posted by KnifeFed

  1. 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.
  2. Happy new year, buddy. The config is in /root/.config/bashtop
  3. Just extract the CA_backup.tar file and you'll have every data folder separately so that you can restore whichever files you want.
  4. Could it be that it's a dependency of some other package? Mine might come from Fish shell.
  5. 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
  6. All my containers are on the bridge network, except binhex-plexpass which is on host.
  7. 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. unraiden-diagnostics-20211202-2353.zip
  8. On https://github.com/jkirkcaldy/plex-utills/wiki/Installation 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.
  9. Right, but why add it to the CA template, is what I'm saying.
  10. 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?
  11. ^To fix the font, you can do: .ca_readmore { font-family: unset; } .ca_readmore::before { font-family: FontAwesome; }
  12. 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.
  13. The post right above yours is actually me saying a reboot did fix it
  14. Edit folder -> "Add another button" -> "Config type:" "Docker Action" -> "Action:" "Start/Stop/Restart"
  15. The fix was to reboot the server. Who would have thunk it?
  16. It seems that in May, the release notes decided to travel back in time
  17. This is what I did initially, i.e. tried a whole bunch of endpoints with the same result, leading me to believe it wasn't an issue with the endpoints, especially seeing as they all have an online status on the Mullvad website. However, now I tried a bunch again and suddenly one worked. I guess Mullvad has been experiencing some weird issues today. Thanks for your help troubleshooting!
  18. Yup, that's the Mullvad DNS server. I removed it and set NAME_SERVERS to "1.1.1.1,1.0.0.1" but got pretty much the same result. supervisord2.log
  19. My container crapped out all of a sudden. It seems DNS resolution is no longer working and the status for every tracker is "Not working". I'm using WireGuard via Mullvad. I've rebooted the server and my router. I've generated new WireGuard config files from Mullvad and verified they're unchanged. I've attached my debug log. Any ideas? supervisord.log
  20. Was there ever a fix for this? I had some garbage containers created due to partially failed `docker build` commands. Performing a complete `docker system prune --force --all --volumes` got rid of them everywhere except from CA Appdata Backup/Restore and CA Application Auto Update.
  21. Would it be possible to run Krusader via Xpra instead of VNC? I find Xpra seamless mode to be a much better experience than VNC.
  22. You can use '/usr/local/emhttp/webGui/scripts/notify' in your script: notify [-e "event"] [-s "subject"] [-d "description"] [-i "normal|warning|alert"] [-m "message"] [-x] [-t] [-b] [add] create a notification use -e to specify the event use -s to specify a subject use -d to specify a short description use -i to specify the severity use -m to specify a message (long description) use -l to specify a link (clicking the notification will take you to that location) use -x to create a single notification ticket use -r to specify recipients and not use default use -t to force send email only (for testing) use -b to NOT send a browser notification all options are optional notify init Initialize the notification subsystem. notify smtp-init Initialize sendmail configuration (ssmtp in our case). notify get Output a json-encoded list of all the unread notifications. notify archive file Move file from 'unread' state to 'archive' state.