trurl

Tools - Diagnostics, attach complete zip file to your next post.

https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564314

Did you try installing an earlier version as discussed in the posts just above yours?

You have too many missing disks. Single parity will only allow you to run with one missing disk. And will only let you recover the data of one missing disk. Do you mean you would now like to simply forget about those other disks and any data they might have had, and go ahead and run with fewer disks than you had before? If so, then you will have to set a new config and rebuild parity. Probably you shouldn't do anything but get rid of that controller and work with us to get all disks working again. I think it's possible none of your disks have failed and the controller is the cause of all your problems. That and the fact that you didn't ask for advice when you had the first problem and just decided to do something that made things worse.

Your screenshot is showing you have 3 missing disks and it says you have too many missing disks. Which agrees with your diagnostics. Did you used to have more disks? What have you done?

You have too many missing disks. Post a screenshot of Main - Array Devices and Main - Array Operations.

You can map any host port you want to the container port 8080

Don't change the container port. You have set the host port as you want it to be, and that is OK, but you have changed the container port to match. You have to leave the container port alone and let it use the port the container expects it to be. That is what mapping is all about. The container port corresponds to (mapped to) a different port on the host. Just like with volume mapping. /config in the container corresponds to (mapped to) a different path on the host, /mnt/user/appdata/openvpn-as. Understanding mapping is most of what you need to understand about setting up any docker all by yourself and without relying on anybody else to tell you exactly what you need to do.

Post the docker run command that results from attempting this in bridge mode.

Maybe you should look at a different solution. Many routers have OpenVPN builtin and you don't have to bother with getting a docker or anything running on Unraid. There is also the Zerotier docker which might work for you and be easier to setup.

Did you actually try this? You mostly just seem to be telling us lots of different things don't work, and frankly, I haven't been able to figure out what you have even tried. It all just comes out as a bunch of stuff all running together. You need to take a single attempt, explain it completely and clearly, and let us help you clear it up. I don't know if we are having a language barrier, or you just don't understand enough to express things in an intelligible way. The key to mapping ports is to leave the container port as it is already configured to be and don't even attempt to change it in any way. Instead, change the host port that maps to that container port. Whatever port you want to use on the host side will be translated by the docker engine to the port the container is expecting as long as you don't change the container port part of the mapping.

Please edit your post and delete all of those separate files, then attach the Diagnostics zip file you downloaded instead.

Seems orders of magnitude more complicated to implement.

Do you understand mapping? What port mappings are you using when you set it to Bridge mode?

Seems like is exactly the functionality you would want. What would a button do, restore everything? Even Windows Recycle Bin makes you select what to restore.

If you are using Host then you can't map ports. Not sure if you understood that from things already said here since you seem to be trying things at random.

Post your diagnostics and docker run command. https://forums.unraid.net/topic/37579-need-help-read-me-first/ https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564345

One way to work around this is to refer to user0 for the share that doesn't use cache. mv /mnt/user/share1/file.txt /mnt/user0/share2/file.txt Unfortunately, users aren't aware of the problem or the workaround. To the user, it is surprising behavior, but not as potentially disastrous as the surprise they get with the "User Share Copy Bug". Lots of ways users and their setups can work with files directly on the server instead of over the network these days and without ever going to the command line.

Tools - Diagnostics, attach complete zip file to your next post.

Understanding volume mapping will go a long way toward avoiding those snags in the first place. See the Docker FAQ. https://forums.unraid.net/topic/57181-real-docker-faq/

You could do it with Krusader depending on how you have the volume mappings.

You must have accidentally created a share with the same name. Any top level folder on cache or array is automatically a share. Maybe something you did in Krusader.

You are missing the mapping for /audio, and obviously the /config mapping isn't the same, but as long as you copy all the /config from needo to L.io seems like it should find your plex library and go with it. Did you copy the contents of /mnt/cache/Apps/Docker/apps/plexmediaserver/ to /mnt/user/appdata/plex_lio ? Did you check to make sure they had the exact same folder structure and contents?