saarg

As long as you choose the new path in the appdata field in the container, you can move the files around as you want. If you are only using the cache drive you should set it to cache only. Cache prefer will move the files in some situations to the array.

You don't know how you set up nextcloud?

Have you done any changes lately?

Is this from plex's free stuff? I would think it's better to ask Plex directly.

The point isn't to set it up the same way as you had it, but to test with a new clean setup if its working. If you add back the appdata you are back to the old setup. Set up a fresh new plex and then add the movies folder so you have something to test with.

What do you mean by adding back the library folder? If it's a folder in appdata then don't. You want a clean config. Also be sure to delete image when you remove the container.

If it's working with a new install, there is something broken in your old install. I can't really help with that as I don't use or know how grocy is programmed. It shouldn't really matter if it's in a docker or not for finding out what is wrong from the developers side. But you posted on reddit as they asked. It could be a corrupt database or a setting in your config.php that is wrong for newer versions. Or maybe permissions? I guess you are copying the files using root? Then the permissions will be wrong and you need to change it to nobody:users. You don't have to redact your internal IP. It's internal and doesn't reveal anything sensitive data.

I didn't say you should delete the current setup. Set up a new one for testing. As long as the other container is stopped and you don't use the same appdata folder and name, your old setup is safe.

You are exposing it to the whole world, that is not the same as having access on your local network.

I think you can just delete the file and restart the container and Plex will download it again. The process should not flash but show until it's finished transcoding. Why not start with a new fresh Plex container and appears to be sure there is no leftovers from the guide and your attempts. Then follow the instructions on the first page of the Nvidia driver thread.

Please don't reverse proxy your unraid webgui. It's not a hardened system. If you absolutely need to access it remotely, do so only using a VPN. When using a custom bridge for swag you can't talk to unraid, so it will not work.

I don't know what you mean by the login section, but you don't need to modify anything in the default file of swag to get any reverse proxy going. Referencing a guide isn't helpful for us either. Post what you have done so we don't have to go through a guide. If you are using the name to resolve the containers you need to create a custom network bridge or else it will not work. All containers talking to each other has to be on the same custom bridge. Is that done?

Is your database server running correctly?

That was something needed a year ago to get hardware decoding working. Hardware encoding have been working without any needs to rename files and create files. So revert your changes.

They should be able to figure out what the issue is. If it's theirs or ours. They just pointed you here without any attempts to find the issue? Is it the same problem if you set up a new instance with an empty appdata folder and database? And no reverse proxy if you have that.

If you have modified any config files, you have probably messed up something. There is no reason to modify any config files to get hardware transcoding working. You could try to disable both transcoding options, restart the container and then enable it again and restart the container.

Sorry, auto-correct changed grocy to group. I'm a part of linuxserver 😉 So try asking the grocy guys

The env variables only work the first time you start the container and has an empty appdata. After that you have to edit the config file to change it.

Yes, that was my thoughts also, but figured it out right after I posted.

I dont have any suggestions. I don't know grocy at all. You can try to ask the group guys if they know why it happens.

It's the environment variables for setting up the database connection and type. If you look at the 50-config file you can see what they are. But they are only set on first container run when there is no config file in the appdata folder.

Maybe related to this? https://github.com/linuxserver/docker-grocy/issues/30

I dont know why sqlite was chosen, but did you consider that it might have been supported at the time we released it? It is still supported in the current version. You can configure the database you want by editing the config file. Looking at the container it might seem like we haven't really released it properly as there are some env vars that is missing from the documentation.

Not so easy to help when you do not post any logs or run command.

Not until alpine release it in alpine 3.13.