Djoss

Clearing the browser's cache usually fixes this kind of issue.

Which error are you getting exactly ? Is the error preventing the disc to be ripped ? Also, what is the model of your drives ?

Could you try to rip the disc manually and provide the output ? First, login to the container: docker exec -ti MakeMKV sh Then, to rip disc 0, execute: env HOME=/config /opt/makemkv/bin/makemkvcon -r --progress=-same mkv disc:0 all /output/manual_rip_test If you don't know the disc ID, you can run: /opt/makemkv/bin/makemkvcon -r --cache=1 info disc:9999

With the latest version, in MakeMKV you click View->Preferences. Under the "General" tab, you have a checkbox "Enable Internet access".

Not sure to understand what was the issue/fix. Could you elaborate ?

No need to remove them. You can just clear the value of you don't need them,

Can you try the same proposed steps: Access in a private/incognito window. Look at the browser's console (in developper tools) for any errors. This should indicate the reason of the failure.

In addition to the "normal" UI, CloudBerry Backup also provide a web interface. This is what you get over port 43211.

Try to access in a private/incognito window. If you still have the issue, look at the browser's console (in developper tools) for any errors. You may also want to share your reverse proxy configuration.

Did you enable WebSocket support on your reverse proxy ?

In the container's setting, you can adjust the following field: Automatic Disc Ripper: Minimum Title Length

Correct, in this version, AMC was not implemented yet.

It's the cache of your browser that you need to clear.

Where are you restoring the files ? If you are restoring at their original location, you first need to make /storage read/write (it is read only by default). You can change this in the container's settings (don't forget to toggle to the Advanced View).

For HandBrake to display these kind of characters, you need to edit the container's settings and add a new "Variable" named "ENABLE_CJK_FONT" with a value of "1".

You need to edit the container settings and add a new "Path". This basically maps a path from the host (unRAID) to a path in the container.

WebSocket support must be enabled only when your proxied application requires it. When enabling Cache Assets, some assets, like images, will be served by NPM instead of your proxied application. I guess this can provide some performance improvements when a lot of them need to be loaded.

Container image has been updated.

@Rejserr, the web server is not starting because of the missing certificate file. If the certbot command suggested by @mattie112 doesn't fix the problem, you should try to edit the file under /mnt/user/appdata/NginxProxyManager/nginx/proxy_host/ that contains the following lines: ssl_certificate /etc/letsencrypt/live/npm-9/fullchain.pem; ssl_certificate_key /etc/letsencrypt/live/npm-9/privkey.pem; And comment them: # ssl_certificate /etc/letsencrypt/live/npm-9/fullchain.pem; # ssl_certificate_key /etc/letsencrypt/live/npm-9/privkey.pem;

You could verify if the time inside the container is correct: docker exec CloudBerryBackup date

Look at /mnt/user/appdata/NginxProxyManager/log/letsencrypt/letsencrypt.log for more details about the challenge failure. Probably that NginxProxyManager is not reachable from the Internet ?

The custom config you put there is inserted under the "server" context. The "log_format" statement is not allowed to be defined there. You could try to add "log_format" to /mnt/user/appdata/NginxProxyManager/nginx/http.conf. However, I'm not sure if it will work well since the log format is already defined somewhere else.

The problem seems to be the ownership of /dev/sr5, which is root/root On my machine, I have: crw-rw---- 1 root cdrom 21, 1 Sep 8 19:08 /dev/sg1 Do you have something that change the ownership of the device ? You can try to set the group back to "cdrom" with: chgrp cdrom /dev/sg5 You can also run MakeMKV as root by setting the User ID and Group ID to 0, but that's not ideal.

So if I understand correctly, the “Network Type” is not set to “Bridge”, but to “Custom : br0”? If this is the case, you are correct in saying that port 8080 can’t be changed. Container’s ports can be mapped to something else only with a “Bridge” network type. You can try to login to the container (docker exec -ti NginxProxyManager sh) and see if you can ping your other container from there.

For some reason NPM is not able to access 170.63. Is NPM using the default bridge network ? What about 170.63 ?