saarg

How do you know it's transcoding? You need to check which profiles the users you have are using. They should be set to pass if that is what you want.

It should have been built, and it was built successfully, but for some reason it's not being pushed to docker hub or github. I'll check what the issue is.

More info is needed. How is you setup and which profiles are you using. Which client are you using. If you are using the tvh gui and the player there, it will transcodes by default.

You do know that the two are separate? The nvidia build is a complete unraid build and you need to wait until the nvidia build of 6.8 is out before you update. Updating to stock unraid and then choosing the latest available nvidia build will downgrade unraid.

Did you check the certificate if it's really expiring? The certificate is renewed at night, so be sure to leave you server on or else it will not be renewed. you can also just add a new fake subdomain to trigger a new certificate.

Delete the appdata folder also if you want to start fresh. If you aren't using the database for anything else, it's probably best to nuke that one also, including its appdata folder.

Are you trying to import the config file of webgrab++ using the tv_grab_wg? Webgrab++ is a standalone software you run to get the TV listing in an xml file that you import into tvheadend using the wg grabber.

Yes

Don't exec into the container. Just edit the file in the appdata share for openvpn-as. Then you can use nano.

You could try running the docker safe new permission tool in tools of unraid. Choose the shares you mount in plex.

Your isp. You get a 404 on hub.docker.com?

You can't run the command if you can't get into the container. So yes, while it's running.

The default folder for www is /config/www or appdata folder of letsemcrypt/www. You probably have to restart the container for the changes to be active.

As long as you don't set an IP for the container, you can still reach it on unraidIP:port even when it's on another custom bridge, as you proxynet. You are correct in that both containers have to be on the same bridge to talk to each other. That's a security feature so containers can't talk to the host. I don't think you can set up a route in pfsense to the internal docker network. If you need mariadb in both the default bridge and in your proxynet, I think the best option is to set up one container in each bridge.

When it's included in a new release it should be available. You have to ask ddclient when the will release a new version. We are releasing the original ddclient and not the fork on github. Should probably shift it to the fork as the original version is dead.

It's a webserver, so you can do whatever you want with the landing page.

You are doing something wrong if the IP changed. Have you been using the internal docker network address? Don't use that. Use unraid IP:port (if you can specify port) or set your own IP, as I think you did. You have both on a custom bridge? Might be your database got corrupted. Don't know without logs. I don't know if you can specify the location for uploads. You have to consult the piwigo documentation to find that out.

If docker hub can't be reached from your server, you can't update the container, so that is probably the reason why you are still on an old version.

I'm going to answer that with a question and you will hopefully understand where to images are stored. Where is you appdata folder located?

If you can connect with your IP:8082 you have an open port that should be closed. You only need port 80 or 443 to the outside.

When you are in the user section there is a add new user button in the menu on the left. If you are on a mobile device that menu might be hidden. Click the sandwich button and it should appear.

Deleting the content of the codecs folder as it says in the post you quoted.

You should ask jellyfin why they stopped building their nightly containers. We have no plans to start building based on their commits.

Their last release was 3 days ago, and so was ours, so not sure how you can define that as stopped publishing builds?

That question is better asked to nextcloud. Nextcloud stores the file temporarily somewhere before writing it to disk and we have no control over where they choose to store it. Might be stored in /tmp inside the container, so you could try to mount a folder to /tmp and see if it changes anything. Do not mount unraid /tmp to /tmp inside the container as that might cause deleted files in tmp that shouldn't be deleted.