ikiya13

Members
  • Posts

    9
  • Joined

  • Last visited

ikiya13's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. I am currently having issues transcoding into H265 using Intel QSV. I am using the two-part plugin (Tdarr_Plugin_JB69_JBHEVCQSV_MinimalFile and Tdarr_Plugin_JB69_JBHEVCQSZ_PostFix). I have looked at the scripts and didn't see anything needing modification. After the video is done transcoding, I am unable to play the file using Plex web (shows errors "Error code: s3014 (Media)" "Error code: s3015 (Media)" and "Error code: s3016 (Media)" in quick succession). I am however able to play the videos on the Plex mobile client. I am not sure if this has something to do with Tdarr or Plex, but I haven't been able to find anything useful in either domain. I was hoping that someone else may have had the same issue and would share their experience. If not, maybe someone can suggest a better QSV H265 plugin.
  2. Do you mind providing me the links for those? Thanks! sike, here they are- github: https://github.com/linuxserver/docker-ombi discord: https://discord.com/invite/YWrKVTn
  3. I have had this problem for several weeks at this point, I think it's beyond a problem with Plex auth.
  4. I, as well as my users, are having issues using the "Sign in with Plex" authentication option. Everything used to work fine then I had some users message me that logging in via Plex was not working. After doing some research I got the idea that some .db files must have been messed up and a clean install is what I did. After doing a clean install and making sure everything is up-to-date, I am still unable to use Plex authentication in Ombi. I am able to log in using an Ombi account, but I would rather not have to force my users to do that. The Ombi logs via Unraid show nothing, and the logs in the appdata folder is just a plethora of [Debug] Batch acquisition of 0 triggers with other messages sparsely added. I appreciate any help and I'm sorry if this has been answered elsewhere, but I was unable to find it.
  5. I'm having trouble logging into my PopOS VM. I have setup WOL as well as turned on screen sharing in PopOS. I have set the screen share password to the same one that I use to log into the VM. WOL seems to be working fine. I can see the VM turn on in my unraid dashboard, but it refuses to connect to apache guacamole because it is sitting on the log in page for PopOS. Once I enter the password using VNC through unraid, I can then connect to the VM through apache guacamole. I'm pretty sure I have followed spaceinvaderone's tutorial correctly but I can't seem to figure out where I am going wrong.
  6. Found the solution thank you! I had another container running that was also bound to 25565 which was preventing AMP from starting.
  7. Edit: I was testing out switching from MineOS to AMP so I still had my MineOS container running, which was bound to 25565. This is what was causing my error. Hopefully this can help someone if they have the same problem. I'm currently having trouble getting the container to start. I have set a custom MAC address, inputted my AMP license, and left everything else stock. No matter what I do or however many times I reinstall the docker container I get the same generic error: "Server error": Furthermore, the syslog shows this message each time I try to start the container (sorry not sure if redacting things actually makes things any safer did it just in case): I think this is a networking issue, possibly related to the MAC address but I'm not sure. I don't want to start the container without the custom MAC to avoid the licensing headache. Any help would be appreciated
  8. Ok I just reassigned it and I think we're good. I'll update this thread if anything changes.
  9. A couple hours ago I restarted my server for the heck of it, and when it came back up, the cache drive wasn't detected. I did a few more restarts, still nothing. It wasn't even being detected in the BIOS. I had to take out my NVME SSD and plug it back in for it to show, but now it's showing up as an unassigned drive. How can I get it back to its cache status like it was before. I have all my docker containers and VMs on there so I am looking for some community backing before making moves on my own.