saarg

You could have checked docker hub before asking maybe?

You can't use the same container path in two folder mappings. They need to be different.

Yes, it's deprecated. It's a pain in the ass to maintain as it breaks on every update. The latest release should work.

Then you don't need to use the port and should close it. You only need port 443/80 open.

Why are you using the port when using your domain? You are reverse proxying it, right?

You don't use context path for subdomain. It's only for subfolder.

That's not something we set, so if you haven't set it yourself, then it's in the upstream package it gets set. In which config file is it set?

No it's not possible. You can install it using our customizing option found in the below link. https://blog.linuxserver.io/2019/09/14/customizing-our-containers/

I would not advice to use latest unless there is a feature you need. New developer started working on it and it breaks now and then. The two versions are identical.

Using the script function it will survive updates.

No

Check if you enabled debug logging. You can safely delete those logs.

Then it's still using the version that ubiquiti pulled as latest. Delete all unifi-controller images and then change something in the template and add it back and hit apply. Then it should pull the correct version.

You don't need to specify latest. Remove the latest tag and then do a force update. It's probably using the latest tag on your system and not our latest tag.

The latest version we released is 4.6.0.50, so you haven't updated your container. It's probably just using the latest version you had on your system, so do a force update.

That makes no sense. Latest is 6.2.25.

Docker run command and container log is needed for others to help.

As long as you have a wildcard cname set in cloudflare, you can delete the other subdomains.

You don't have to set a came in cloudflare when using wildcard. Wildcard is for everything. I guess you are using a custom docker network for swag and radarrs, so no need to change the port in the proxy-conf as swag talks to the containers using the name. It is all internal in the custom network and therefor you use the container port.

Use an earlier tag. It's an upstream issue.

No, the traffic doesn't go out and in again. Your router is doing hairpin nat. There is no reason to set it to host network mode.

https://blog.linuxserver.io/2019/09/14/customizing-our-containers/

It gets copied on every start, so no point in deleting it. Edit it instead of deleting it. It is set up this way so we can supply a working setup the first time you use the container and in case the user has messed up the default file, can delete it and get it back to a working state.

There is no www-data user in our container. The I/O error is most likely something wrong with your disk/controller and not an issue in the container. So check the drive and filesystem for errors. Of you find errors, you should open a new thread in the general forum the get help as it's not container related.

Then you need to ask alpine Linux to enable it in their ffmpeg build.