Jump to content

Leifgg

Members
  • Content Count

    407
  • Joined

  • Last visited

Community Reputation

14 Good

About Leifgg

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  • Location
    Stockholm, Sweden

Recent Profile Visitors

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

  1. Have a look in your appdata share and open your Plex folder. Browse to Library/Application Support/Plex Media Server/Crash Reports/ Here you have folders for each version you have had installed and the name of the folder is the same as version number string. So just use this name to specify what version you would like to use.
  2. Sorry I misunderstood, I was assuming you meant that the UPS itself needed to have an Ethernet interface…
  3. It’s not a ”must have”, cool yes but not needed. USB will work, it will be the “master” server that connects to the other servers and initiates the power down, it’s not done by the UPS. Just remember that the router and switch need to be on the UPS as well.
  4. I am using Sandisk Cruzer Fit (the USB 2.0 version) in my servers without any problems.
  5. I am using same version as you (Plex inc) without any difficulties. Only setting I have that is different is the mapping to the appdata folder, I am using /mnt/cache/appdata/Plex/ where you have /mnt/user/appdata/PlexMediaServer/ I don't believe that it makes any difference but you could try changing from /user/ to /cache (from user share to disk share, assuming you are using a cashe disk). I has been mentioned for other containers that this could make a difference.
  6. What I would recommend as first step is to setup transcoding to disk. If you have cash disk use that one (any type, don't need to be an SSD), if not do it to the array. Ask if you need help. You shouldn't try transcoding to RAM until you have Plex working first. You can read more about transcoding to RAM here:
  7. Not sure I understand what you would like to do, if it’s transcoding to disk or to RAM. If you have the Transcoder temporary directory in Plex set to /transcode then you should also have a folder mapping with a Container Path: set to /transcode If the Transcoder temporary directory in Plex is set to something else then the folder mapping for the Container Path: should be set to the same. If they aren’t the same, you will transcode to disk and in this case the docker image. Depending on the size of the docker image you could run out of space when transcoding. The setting that configures the transcoding location is the Host Path: If it’s set to /tmp you will transcode to RAM and hopefully you have enough RAM to do this. If you prefer transcoding to disk, you need to configure Host Path: with the location (folder) that you would like to use. Could be something like /mnt/user/appdata/transcode or similar. Preferably a folder located on an SSD disk but that’s up to you.
  8. Here is an example…. I don’t use binhex container right now, but it shouldn’t be to much different. I have configured Plex to use the folder /transcode (this is what the Plex app in the container can see). Then I have a folder mapping for the Plex container that maps /transcode inside the container (Container Path:) to a location outside the container (Host Path:) In this case I have mounted an unassigned disk (not belonging to the array and not a cash disk). When browsing unassigned disks will show up at /mnt/disks I have labelled my unassigned disk to Unassigned (otherwise I think it will show up with its s/n). I have also created a folder Plex_transcode on that disk that I will use. The Access Mode: should also be set to RW/Slave /Leif
  9. Do you get out of memory errors when using Plex? If that is the case it might be related to transcoding and how the folder mapping is set for the /transcode folder
  10. And not to forget, having a Plex Pass also support the developers to keep a great product getting even better….
  11. Have a look here: https://www.plex.tv/features/ Basically Plex pass gives some more features as well as Beta releases...
  12. Edit the container like described here: Should look like this:
  13. Updated to the latest image and everything is back to normal. Once again, Thanks!
  14. Updated my CrashPlan Pro Docker today but it did not start up, GUI only shows a black screen and log is repeating "app starting CrashPlan...". Any ideas on whats happening?