Community Developer
  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by spants

  1. is there a 192.168.1 item in allowedNetworks key in your Preferences.xml file
  2. actually its name is Plex Media Server.log . (may be!)
  3. The plex logs are at: (on my machine) /mnt/user/appdata/plexmediaserver/Library/Application Support/Plex Media Server/Logs/ and the file: Plex (anonymous).log Does anything look strange with this file on your machine?
  4. that is weird. I wonder if plex stores an ip address in its settings. I will remote in to mine and take a look
  5. you just installed and uninstalled on the server? did you do anything to the clients? do you have any other clients you can try? I cant see how it could affect it ....
  6. any other plex clients you can try? Other than a server reboot, Im not sure what to suggest ...
  7. does everything else on the fire tv work? any logs from the plex docker?
  8. try clearing your browser cache or try private mode....
  9. Pihole should be fairly easy to use. Either run it on the server and use the servers ip address for the dns server for the clients.If this doenst work (you have another dns service on the unraid server) use the set separate IP address for a docker instance detailed a couple of posts back. If you want to disable pihole on one of all clients, just change their settings to use dhcp to get their settings from the router or change their dns settings to google and and reboot clients. Pihole doesnt affect plex directly - it may just be your dns settings on the clients
  10. have you set the clients to use pihole? 2 ways to do this - 1) on your router, set the dns servers to point to the unraid box (or pihole IP address if you have changed it) 2) turn off dhcp on the clients if you have not chosen (1) and manually add the pihole server ip as the dns server address
  11. would this help you? I think that KVM/VM subsystem can use port 53....
  12. Hi When the docker is updated by the docker owner, the template automatically shows that an update is ready (I am not building the docker....just supplying the template). Some of the changes to pihole need dockerfile changes so it best to wait until he updates the docker for all.
  13. would be worth a try!. Let me know how you get on
  14. I use the script with the UserScripts plugin to run every day. That works really well.
  15. Do you have to switch to maintenance mode first? - just a thought.
  16. The docker hasn't been updated yet (I only maintain the Template)... The reason is here:- ...hopefully soon!
  17. you cant change ports. DNS is port 53. The kvm system also uses port 53 dns which is why you have to do as the "fix" says.
  18. see this post for a resolution... seems to be kvm.
  19. Make sure that you add them to the blacklist - not the whitelist!
  20. try this, it sets the password for the GUI as well (which seems to randomly reset itself) #!/bin/bash DOCKER_NAME=pihole PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin # Download any updates from the adlists docker exec $DOCKER_NAME pihole updateGravity > /dev/null # Pi-hole: Update the Web interface shortly after gravity runs # This should also update the version number if it is changed in the dashboard repo #docker exec $DOCKER_NAME pihole updateDashboard > /dev/null # Pi-hole: Parse the log file before it is flushed and save the stats to a database # This will be used for a historical view of your Pi-hole's performance #docker exec $DOCKER_NAME # note: this is outdated > /dev/null # Pi-hole: Flush the log daily at 11:58 so it doesn't get out of control # Stats will be viewable in the Web interface thanks to the cron job above docker exec $DOCKER_NAME pihole flush > /dev/null # updates password for docker gui docker exec $DOCKER_NAME pihole -a -p newpassword
  21. it isnt as straight forward as I first thought and ran out of time. I will have another look in a week when my time frees up a bit
  22. ok, mine has been very stable with lots of devices attached
  23. ok, I pushed 1.4.10 for you - see if that helps