jumperalex

Members
  • Content count

    1956
  • Joined

  • Last visited

Community Reputation

3 Neutral

About jumperalex

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. Never mind. I was too impatient and didn't know about the default 180 second "Shutdown grace delay" before which the ups will actually shut itself down. On the status screen is it called " DSHUTD "
  2. Wait is the point here that we need to set it to "NO" to get the UPS to turn off? I'm just now looking to make this happen and I can't seem to. The server shuts down just fine, but the UPS stays up. tower-diagnostics-20170518-1735.zip
  3. Not even a sale really, but cheaper than Amazon by like $30 https://www.newegg.com/Product/Product.aspx?Item=N82E16822146116&ignorebbr=1 This is their "new" 4TB apparently as compared to the HGST Deskstar NAS 4TB 7200RPM SATA III 64MB (0S03664) which is the one I think Backblaze reports on.
  4. http://www.microcenter.com/product/469984/Barracuda_4TB_35_Hard_Drive_-_OEM
  5. So you're the guy!!! ... the one that responds to Amazon questions with "I don't know"
  6. OMG OMG OMG ME ME ME BETA BETA BETA WOOT WOOT WOOT [remembers he has no GPU on his server]
  7. needo isn't around much these days. linuxserver.io is probably most recommended and support plexpass and betas. Maybe so but he's definitely still updating it. In fact I just got an update today to 1.4.1.3662 That is the nature of the docker "update" by restarting it. It goes out and gets the latest build from Plex. Needo hasn't touched the docker container code in months. The implication is that the docker code needs to be touched. Is there something about Needo's docker code that needs updating?
  8. Be sure you do not have any old plugins installed like the dynamix.plg that was a beta test version. I would start in safe mode and see if that works, and then start re-installing plugins to see if one is breaking unRAID. I tried this already but was not able to start docker with 6.3. I deinstalld all docker plugins and deaktivated docker, then upgrade to 6.3 and then i tried to create a docker image and start it. Creating was possible but no start. Did all from scratch severel times but no luck - as soon 6.3 is on, docker cant be startet. Start 6.3, attempt to start the docker, give logs. If no docker is even shown for you to be able to start, then post logs. Either way, needs logs or can't help.
  9. How can i do a restart command? Dashboard -> click on Plex to show context menu -> restart -> -> Profit!
  10. FWIW, plex wasn't accessible, despite the docker "running" until I issued a restart command for it. Then all was good. This was after first reboot after update.
  11. I seem to have the same issue. Did you erase the appdata openvpn folder and start over fresh? I have all my devices setup and would hate to have to recreate it all. Thanks Yes that is what I had to do. I only have one user and two devices so I wasn't too concerned about retaining settings. You might get away with just moving the bin folder out of there and see if it recreates correctly. Or go the other way and start with a fresh appdata folder and then can you import your device connection settings?
  12. hmmm I just tonight told it to update from the Docker tab. I take I just need to delete the whole thing? So I removed the container and the image. Repulled from CA and I'm still looking at 2.1.2 Would it be because I reused my appdata folder without emptying it? EDIT: [sigh] yup that was it. cleared out appdata. I'm sure somewhere in this thread it is mentioned.
  13. sooo openvpn-as is now up to version 2.4 but I only seem to grab 2.1.2 .... am i missing something?
  14. So just to bring my own thread back OT I feel like we're got a few open questions concerning the real threat surface of: The mover script / MV at risk of malformed file names; I can't imagine this is easy or lucrative enough for a black-hat to even try Docker apps being granted R/O access to shares they don't need R/W access; this can at least reduce the impact of an attack Docker itself and how to mitigate its compromise; I think the answer is backups ... anyone else? Compromise of any media player, like Plex's custom ffmpeg, via malformed media file posted to torrent sites; could be lucrative if its possible. Let's say, a poisoned GoT torrent hmmmm Ditto for a malicious RAR and the tool being used to extract it I mean these are the server side attacks that I can think of for a box like mine, but the way I see it, all except a Docker exploit can only hit my media/torrent which is less of a concern than my PC backups which hold actual important data. Still it would be nice to discuss ways to further prevent an attack and limit the extent of the damage should it happen.
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.