saarg

Remove the command and execute it after you have exec into the container.

For the hardware that can use direct play, use that. No point transcoding something that can be natively played on the device. For the devices that you have to enable transcoding to get it to work, try changing the resolution/bitrate the transcode outputs. What does the now playing page says about the transcoding? From codec to which codec.

I guess you don't see your unraid server as a NAS. Your database needs to be on a filesystem and not a fuse/network storage.

No, that is the host port. Use 443.

If you use a custom bridge, you use the container port, not the port you mapped on the host side. As for the 400 bad request, I don't know what it could be.

I never set one up myself, as the one I had was dead when I tried setting it up in oscam. Oscam doesn't find the device. The device ID I was talking about is not xxx:yyy, it's just one number and you have to find it using a special tool. You can try setting the ID from 0 to 6 and see if it works. There is a section in the webui where you can see all available devices. Don't remember where and I don't have access to setting up oscam now.

Is the smargo even using a device ID like that? From what I remember from years back you have to find the ID of the reader using the smartreader tools. Googling smargo and oscam confirms that. Also the protocol should be smartreader or mouse.

Might be permission errors. Have you tried to change permissions for the smargo?

That doesn't make sense as your proxy is using the same address. Something locally on your computer blocking the page? Or any setting you have done in papermerge?

Try using legacy boot and see if that helps.

Are you using a custom bridge? The name of the container has to be all lowercase. Your is OnlyOfficeDocumentServer which will not work. So change the container name to all lowercase both in the proxy-conf and the container template.

Nginx has nothing to do with the renewal process, so no point looking in those logs for an answer. You have not said anything about the result of what you checked from the troubleshooting guide.

502 means swag can't connect to nextcloud. You have added your domain to two array entries. Try removing the www.x.net. How are you accessing the URL? Inside your network or from the outside?

Change the upstream port from 443 to 1443 in the proxy-conf. Our confs are based on using a custom bridge and talk internally on that bridge, but you are using the default bridge, so you have to set the port to the one you used in the nextcloud template.

There is something wrong with permissions indeed. From the container log UID is set to 911. That is the default number for abc. It should have been 99. The run command looks good, so not sure what is happening.

Doesn't look like a permission issue. Have you had it running before or is this a new install? Post the docker log for the container.

Have you followed this troubleshooting guide https://blog.linuxserver.io/2019/07/10/troubleshooting-letsencrypt-image-port-mapping-and-forwarding/

wayner.dyndns.org goes in the domain field. You do not own dyndns.org.

The emby stats server was the plugin until the developer decided to build it as a server.

I'm sorry, I will put my busy life, working and moving houses from morning to late night tha last month to help you. I'll also install network in the house with my foot I just had surgery on that I can't use, so I can set up my servers and computer to help troubleshoot. This is all volunteer work, so please remember that. I answer if I have the time and setup to do it.

GitHub would be the correct place I believe.

You can't add anything to the stream. You get what the sites adds to the feed.

Yes they are correct. I thought no this happens if you are using existing appdata to set up the container again. From my testing it worked with the env variables in the template.

Ask Plex.

Is there anything missing in the env variables? That is the only reason I can think of. If not, you should probably open a thread about the issue as this is an unraid issue and not the containers issue.