saarg

Using the command line.

Edit it using unraid and not windows.

Why not set the staging variable to true, then change something, like adding a subdomain, and start the container. Then you can test it as it does a test of creating a certificate, but doesn't really create it. You also don't get ratelimited.

Don't know the command to list folder size by heart, but Google probably knows. You could test with a file you know will not fill your docker.img and then run the command to find the big folder.

Have you tried to find the folder that grows inside the container?

1. Please use the code tag when posting logs, as it makes it easier to read. 2. What is the issue? We can't read your mind. 3. You need to post the reverse proxy configs. 4. Is it only an issue when using the reverse proxy or also if you access them using IP? If it happens using the IP, it does not belong in this thread. 5. Revert your changes. Also post exactly what you have done.

As always, when it is available in the unifi repo.

Check the tags page using the docker hub link in the first post. Then use that tag after the repository in the repository field. linuxserver/medusa:the-tag

There isn't much to read up on. Toggle to advance mode in the top right corner of the container template and the extra parameter field is visible. Then you can add whatever docker parameter you need.

Shit... We just pushed 5.11 for the LTS tag 😝

Python 2 is EOL, and alpine removed python 2 from their 3.12 release. So you need to update your scripts to use python 3. The binary is called python3.

Or you can just click the Add another Path, Port, Variable, Label or Device at the bottom of the template and choose variable and fill out the fields.

You have to use the variable RUN_OPTS and set -6 or --ipv6 as the value in the docker template.

The solution to that is to build the system yourself then 😉

He did not answer you in that post, but another user. He even quoted the user. He even followed up your answer saying it wasn't for you 😉

No.

I'm not aware of any automatic ripping in this container. Are you maybe using djoss's container? That one has automatic ripping.

We deprecated this container a long time ago. So you need to use another serviio container.

If you get the same errors in the browser if you shut down the containers, the issue is your port forwarding or your ISP started blocking ports. Your port forwarding looks to me to be the wrong way, but you don't post more from the router, so hard to say. Logically the wan port would be on the left side and the internal port on the right side. Do you only choose from a list of computer or did you write in the name of the server yourself? Might try with the IP instead.

The dvb plugin only checks at boot, so as long as you install the driver yourself, the dvb plugin will not show it. The dvb plugin doesn't hand anything over.

It means that when the pull request on our repo on GitHub that contains the added package is merged with the current code that builds the container, there will be built a new image for the container.

The plugin is running as root so it has access to the dvb device.

Then I do not know what is happening. Permissions should be correct now.

It will be added when the PR to add the package is merged.

You don't do anything in the tvheadend container. Also, have the container stopped when you do permission change on unraid. Then start the container and show me the permissions of /dev/dvb inside the container.