Jump to content

hooger

Members
  • Posts

    115
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

hooger's Achievements

Apprentice

Apprentice (3/14)

0

Reputation

  1. Anyway to get "fish" shell updated? The nerdpack is rocking version 2.x, but a lot of the plugins I need require version >3.x
  2. Is it possible to get "ncdu" added to this pack? It's a very nice tool for finding which folders/files are taking up all your space. Can find some screenshots here, as well as a link to the slack package here
  3. Just looking into this for future use. How would I handle having multiple domains pointing to the same server? Ex: My current nginx setup has 4 totally different domains, all coming in on the same ip/port then gets sorted out by nginx. Is something like that possible with this container? (I'm 100% new to letsencypt, only switching because of chrome/google no longer recognizing startssl)
  4. Having some trouble trying to get this ssh plugin to install I'm on the latest version of unraid 6.2, I've tried installing it via the Community Apps plugin, and manually. Any ideas?
  5. Asked and answered, it is removed when they issue a final release. ... DRM preventing my box from booting (BETA OR NOT) is UNACCEPTABLE. The fact that there has been no word from LT on this yet is UNACCEPTABLE. Guys, sort out your PR - please! It's a running joke!! ... If it truly is a "kill-switch" meant to protect data from a potential fatal bug, couldn't it be handled a little differently? Instead of stopping it from booting, couldn't it boot into a "degraded" mode. As in, the array doesn't auto-start on boot. And in order to start the array, a dialog could be prompted warning the user of the potential danger, then they would make the decision to start the array.
  6. He's not being hacked, this is very common if you expose port 22 (ssh) to the internet. It is an automated attack trying to get into the server, as long as you disable password (and root login) and use private/public keys he will be fine. I suppose you could implement fail2ban or other such programs out there to reduce the number of attempts. But this is a common occurrence these days, as long as your ssh server is sufficiently secure they can brute-force all they want. So just disable password login info here, and use private keys to login info here, and you'll be fine.
  7. The directory seems to be 777, but what is the actual files permissions? Deluge may be writing the file under it's own user with different permissions.
  8. Sometimes elsewhere in the BIOS you have to enable the boot feature. On my Gigabyte mobo I had to enable "LAN Boot" in a completely different menu, before it would show up under the boot options.
×
×
  • Create New...