Jump to content


Community Developer
  • Content Count

  • Joined

  • Last visited

  • Days Won


ljm42 last won the day on January 19 2018

ljm42 had the most liked content!

Community Reputation

117 Very Good


About ljm42

  • Rank
    Advanced Member


  • Gender
  • Personal Text
    the answer to life, the universe, and everything

Recent Profile Visitors

1870 profile views
  1. Just FYI - A few versions back Unraid added a robots.txt file, which should keep legitimate search engines from indexing a server that is placed on the Internet.
  2. Please see this guide: AFAIK it details the best way to run Unraid as a guest on an Unraid host.
  3. Very cool @Squid! FCP is awesome for this type of proactive notification No false positives here.
  4. @Squid is this something Fix Common Problems could detect?
  5. hmm... git doesn't seem to be installed in 6.7.0? root@Tower:~# git -bash: git: command not found root@Tower:~# whereis git git: root@Tower:/var/log/packages# ls git* /bin/ls: cannot access 'git*': No such file or directory
  6. This thread was obsoleted three years ago, but I went ahead and updated it to acknowledge that issues with transcoding to RAM may have changed since then. If you'd like to discuss that topic I'd suggest visiting the Plex: Guide to Moving Transcoding to RAM thread.
  7. If it works for you, great! But if you start having issues with Plex, this is the first thing I would change.
  8. Looking at top.txt file in your diags, Plex was indeed using 100% of your CPU at the time you generated your diagnostics: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 5958 nobody 20 0 1314160 75948 36220 S 100.0 0.9 13:52.16 Plex Medi+ see this I didn't recognize that, but a Google search for "unraid ACPI BIOS Error" says it is harmless, although you might try checking for a bios update: https://forums.unraid.net/topic/75337-acpi-bios-errors-in-syslog/
  9. It is a valid question, the Linux drivers for those cards may not be included in Unraid. If nobody can give you a direct yes or no, I would do a Google search for "unraid x470" and "unraid 10gbe" to see what you can find
  10. I have had mixed results with https://ipaddress . At a minimum you will need to bypass the browser warnings telling you that the certificate doesn't match the url. http://ipaddress will automatically redirect to https://hash.unraid.net . If your computer hasn't cached that address already and your Internet is down, it won't be able to do a DNS lookup, which causes the issue you are seeing. One solution is to add an entry to your local hosts file that points hash.unraid.net to the correct IP address. The downside is that this overrides DNS, so you need to remember to update the hosts file if the IP address ever changes. Another solution is to disable SSL by editing the /boot/config/ident.cfg file and changing USE_SSL to "no", then typing "powerdown -r" from the console to reboot. When it comes back up you will be able to use http://ipaddress to access the gui.
  11. I guess this is a good time to mention that you need to be careful when editing this file Also, be sure to use a good text editor that understands Linux line endings (such as Notepad++), definitely not the standard Windows Notepad.
  12. That starts the webgui. It is in your go script already, I was just showing that you want to copy the file before that line so the array will be able to auto-start.
  13. Copy the keyfile to /root . Easiest way is to add the copy command to /boot/config/go, before you start emhttp #!/bin/bash # let encrypted array auto-start (obviously, not secure) cp /boot/config/custom/keyfile /root # Start the Management Utility /usr/local/sbin/emhttp &
  14. Any response would just be speculation at this point. If you upload your diagnostics someone might have some ideas (Tools -> Diagnostics, then attach entire zip file to your next post)
  15. Sorry... I was looking in rc.nginx for other places to use this, and I realized the function name should be more like wait_nginx_down instead of wait_nginx_status It can easily replace the "sleep 3" in nginx_term and nginx_stop. But what about nginx_reload, is that actually waiting for nginx to be up instead of down?