Rojma

I can confirm that the MakeMKV container is working fine for me in UnRaid 7.2.4.

Never mind I figured it out. Under Interface Rules in Network Settings, I had to move my new dual port network card so that they were assigned to interfaces eth0 and eth1, and the previous internal network port as eth2 (it was previously eth0). I also made sure that the port that was connected to the internet was assigned to eth0. Once I did that, I enabled bridging on eth0 and made sure the bridging members of br0 was set to eth0. Once I did that, the WebUI menu option in the docker containers started to work and I was no longer getting the errors in the Edge developer window. Thanks for the tip that led me to how to fix this.

@kiteboy I'm having the same exact problem - recently installed a new network card and the WebUI link doesn't work in Docker containers anymore. Typing in the URL of the container though does confirm the container is working. I am getting the same error message in developer mode in Edge (also doesn't work in Firefox or Chrome). Can you elaborate on how you fixed it? Not sure I understand that you had to move this back to br0 rather than br1?

FYI version 1.18.2 of MakeMKV has been released. Thanks!

FYI version 1.18.2 of MakeMKV has been released.

Thank you for the response @Djoss. I updated to the suggested image and confirmed that the error no longer occurs. Thanks for the fix. Should I keep the image as jlesage/makemkv:ffmpeg7?

I wanted to report an error that I am seeing with this docker version of MakeMKV. When ripping the 4K UHD disc of Elio, I got the following error messages in the MakeMKV log window: FFMPEG_ERROR: FFDEC000: [truehd @ 0x147b99b5fb40] No restart header present in substream 1. FFMPEG_ERROR: FFDEC000: [truehd @ 0x147b9990be40] No restart header present in substream 1. FFMPEG_ERROR: FFDEC000: [truehd @ 0x147b987a8a40] No restart header present in substream 1. ... The error repeated 103 times, with the 0x code being different most times (although sometimes it would repeat once or twice). The ripping job though appeared to finish without issue. I was not trying to transcode any audio to FLAC or other format - the audio was being copied as is. I tried with both the Default profile and a Custom profile (that just changes something with Forced subtitles) and the error occurred both times. I used MakeMKV on Windows 11 to rip the same disc and did not get the above errors. I also tried the binhex docker version of MakeMKV on the same Unraid server where I got the above errors and again didn't get the above errors. I searched in the MakeMKV forums for the above errors, and it seems like the problem might be related to the version of ffmpeg, and upgrading the version of ffmpeg might resolve the error. Would it be possible to update the docker image with a newer version of ffmpeg to see if it resolves the error?

I am on UnRaid 7.1.4 and for the life of me, I can't get copy and paste to work from my PC (Windows 11 24H2) into a VM in UnRaid also running Window 11 24H2. I have tried the default noVNC and also installed RealVNC but neither work. In the properties of the VM I have enabled the option VM Console enable Copy/paste, but this doesn't make a difference. I've tried installing the Spice guest agent in the Windows VM, but it still doesn't cause copy/paste to work (is this even needed when using VNC as the console protocol vs. Spice?) I've also installed the virtio drivers and virtio guest tools from the virtio-win-0.1.271 ISO, but still its not working. I have a program that utilizes Windows Hello for authentication. Windows Hello doesn't work in an RDP session, but does work in the console session via VNC, which is why I want to primarily use the console session via VNC instead of RDP (RDP otherwise works fine). I have read a lot of posts, but they are either lacking details, or are older posts from older versions of UnRaid before the VM Console enable Copy/paste option was added. What am I missing? How do I get copy and paste to work for a Windows VM?

Is there a way to persist device paths/names (e.g. /dev/sr1, /dev/sg2, etc.) for optical drives that will survive reboots and/or unplugging/re-plugging external USB optical drives? I've done some research and if I am reading correctly, it might be able to be done with udev and udev rules, but I'm not exactly sure how to go about it with UnRaid. Background: I have media server running on UnRaid. As part of that, I have several optical drives on the server that I use with MakeMKV docker containers. I pass in the necessary device parameters to the MakeMKV docker containers so that they see the optical drives. Some of the optical drives are internal connected to internal SATA, while others are external connected via USB. If I reboot the server, all of the drives, including the internal ones, seem to randomly reassign their device paths. They don't stay the same between reboots. The same happens if I either disconnect/re-connect or turn off/on the external USB optical drives. I then have to look up the new device paths for the optical drives and update them in the MakeMKV containers. This has become a bit of a pain. I would like for the drive paths to persist so that I don't have to continuously update the Docker containers with the updated device paths. Is there a way to accomplish this?

Never mind. I tried it again and it worked. Not sure what I did wrong the first time.

I have multiple optical drives connected to my UnRaid server. Right now, I have separate instances of MakeMKV dockers set up, one for each optical drive. This works with no issues. However, is there a way to get one docker instance of MakeMKV to see multiple optical drives? I could then select the drive I want to use via the drop-down menu in MakeMKV, similar to how the Windows version of MakeMKV works when I have multiple optical drives connected to my Windows device. I tried adding additional device parameters for the additional optical drives to the docker container settings (the same ones I use in my separate instances of MakeMKV), but that didn't seem to work. Any help would be appreciated. Thanks!

I noticed MakeMKV has been updated to 1.18.1. Any idea when the container will be updated?

I had tried several browsers including Edge, Firefox, and Chrome. However, I did end up getting this to work and it ended up just being the field working in an unexpected way. When I select the field, it puts the cursor at the start of the field instead of the end of the field. I first wanted to delete the current value in the field, so I tried both the Backspace and Delete keys on the keyboard, and they didn't work and didn't erase the current value. I also tried highlighting the field with my mouse but that also didn't work and it wasn't highlighting the value. I just assumed that the field wasn't working and couldn't be edited. However, when I finally tried just entering in a number, it erased the current value and started to put in the desired value. I had never actually tried to enter a number. A bit of oversight on my part, but also the field worked in a bit of an unexpected way.

I have an NVMe SSD set up as a cache drive. I need to change the temperature threshold setting for the drive since they are expected to get a lot hotter than a traditional hard drive. When I select the drive under Main, the Warning disk temperature threshold and Critical disk temperature threshold setting under Cache Settings > SMART Settings aren't editable. Where can I change these settings? I feel like I am missing something obvious but can't find the setting. I did a lot of searching and found a lot of hits from an issue a few years ago where the setting could be changed, but the setting wouldn't stick. This isn't the problem I am having - I can't change the setting at all and the field isn't editable. I am on Unraid 6.12.13.

I just wanted to report an issue that I had today with the Backup Appdata plugin. I was replacing my cache drive so used the backup/restore functions of the Backup Appdata plugin as part of the process. Most everything worked, but I had a minor issue with the restore for the Channels DVR Docker container. Apparently, Channels DVR downloads some binaries into a folder within it's appdata folder. The name of the folder is the same as the current version of Channels DVR. It then creates a symbolic link to that folder and calls it "latest". When I restored from backup, some of these folders ended up being empty and caused issues with Channels DVR. I saw another post here with similar issues with Plex and symbolic links, but figured I would also report the issue I had. It doesn't look like the plugin properly handles symbolic links.