saarg

The Cron job runs every night at about 2. You have to check the logs for why it's not renewing the certs. I think the log is named letsencrypt. Also restart the container and post the log. Be sure to redact domain and personal info.

You can click the padlock in the browser when you are on a page hosted on your domain and check when it expires.

That's because you set an IP for the container. Port mapping have no function then, as it's the same as running it in host mode. If you want to use port 443 you have to use bridge network mode.

The port mappings doesn't have any meaning when using HOST network, so ignore it.

You need to install the driver to use your adapter. Then use /dev/dvb as the path for the device pass through. If you are using 6.9.x I don't know if the permissions are set correctly, so make sure nobody has the correct permissions for the adapter. You can't pass through using /dev/bus/usb as the container doesn't have any drivers.

Sorry, crystal ball is still in repair shop. If you want help, a more detailed description of what you are doing, container logs (full) and docker run command (no screenshots) needs to be posted.

Please post the docker run command instead of a screenshot of the template. A screenshot misses a lot of information needed.

Sounds like a bug in Jellyfin. We set /config/data as the data for and for some reason Jellyfin doesn't care about that for that file.

I have used unraid to shut it down.

I highly doubt it's the update that is the issue. It's probably docker that force the container off that causes the corruption. I always shut down other containers using mariadb before updating it.

That would go in the nextcloud thread. Nothing to do with swag.

Go West? We are not mind readers, just so you know.

That is not needed at all. Something else is wrong in your setup.

Yes. Why wouldn't it?

We have nightly builds.

You should have a read in the docker faq to get some basic understanding of how docker works. You need to volume bind that path to the container to use it.

That is an issue with unraid and not Plex, so better to open a new thread in the general support subforum.

Try using a tag for the previous version.

I have no idea to be honest, but might be one of the --cap-add or privileged doing it.

Even if we update the default file, you will have to delete it and restart the container to get the updated one.

I don't see anything wrong there. Does it stop if you stop the container?

Start by reading first post, then wait until it's available as nextcloud decide when you get.

It doesn't help to use the tag as you have to update nextcloud inside the container. Updating the container doesn't update nextcloud.

Never used it, so can't really help with it. Did you modify any config files related to fail2ban that might interfere with it?

This container use certbot to get the certificate, so why is this needed?