saarg

Please post full logs, not only the error. Earlier log you showed a cert was generated. You can use staging to test so you don't get rate limited. Did you read the blog post you linked? Have you tried setting up the nginx container to see if you can access it on port 80 remotely or if your isp blocks port 80?

No need to post an issue on github. Github is not used for support questions, but bugs. You have to use the command line to update nextcloud. Webui works for some, but not all. The update is not under our control as that is all nextcloud. There is a link in the first post to a update guide.

Are you using unraid? The reason I ask is that you have not set the PUID & PGID values and those are default there if you use unraid and install through CA. If you are not using unraid, this is not the place to get support. Go to our discourse forum or discord.

You can start by posting the container log and the docker run command.

Wait a moment... You use win10?! I always imaged you only running Slackware command line only 😛

This is a support thread for unraid users. Since you are not using unraid, please post it in our Discourse forum or use Discord.

Impossible to say without any info.

It does not have to do with not finding your media. You need to set up the server and add the folders you set up. Try changing the appdata path to /mnt/cache/appdata/plex instead of /mnt/user/appdata/plex. If you haven't been running plex before on unraid, try deleting the plex appdata folder before applying the changes. Also post the log appdata/plex/Library/Application\ Support/Plex\ Media\ Server/Logs/Plex Media Server.log

Did you try xen-pciback.hide with the syntax I said? And please post the output of the command I posted.

vfio-pci.ids only binds the specified device.

I don't understand the part about your NAS is not an authorized device so the server can't connect? You are not going to see the NAS as an authorized device. Your plex server will show up on your account. I assume that by NAS you mean unraid? You mount those folders to the container. So that is not an issue. Your issue is that for some reason you can't connect to the container. Post the log of the container so we can see what is happening. Also, you have to be on the same network (as in 10.0.0.X) to be able to access the container. And just in case you don't know. Your host path for transcodes is /transcodes which will be in RAM. You then might have issues that you RAM get filled.

It does that since that is the way to do it. You use the PCI number. You are confusing PCI number and the vendor:ID that is used in the syslinux.conf using vfio-pci.ids. You can try the one I suggested, but I don't think it will work as none of the other 2 have. But it doesn't hurt to try it. It's just a reboot away. Post the output of lspci -k and post it here. Both for your current and after doing the xen-pciback.hide.

The error in the beginning of the post is not in the full log you posted. In the log it says the certificate was created. Without your docker run command its hard to say if your port forwarding is correct. What does not work?

It is the PCI address in the new method. The post you quoted says the new method uses addresses 😉 You can also use PCI addresses with xen-pciback.hide in your syslinux.conf. I haven't really checked if it's still available, but it doesn't hurt to try it. syntax is as below. xen-pciback.hide=(08:00.0)(08:00.1)

Usually in /mnt/user/appdata/nameofcontainer. Check in unraid docker settings what you have set there as default if you are unsure.

It gets added to letsencrypt when it's built, so whenever there is an updated package for the container. You can just add it to you proxy folder and it will work.

That just means nobody made a proxy conf for subdomain.

I don't know how to check the database. You probably have to Google how to check a mariadb database.

Probably a corrupt database. Try restoring a backup.

You don't have control over duckdns.org. You need to add your part of the address before that, like myurl.duckdns.org. Not sure how you managed to get a cert that way. Do you only get an email saying it is expired or do you see it in the browser going to your domain?

Check the link in my signatures. If you don't see it, then you have to turn on signatures in your control panel. Or check the docker faq.

This container doesn't use Apache, but nginx. So if you didn't use this container I find it strange you are posting this here. What might seem easy to you might not be as easy for others. For people not used to setting up a VM with all the requirements, this docker is easier.

Please post your docker run command. The screenshot doesn't show all the info we need.

If you think this is a simple compile on boot job, you have clearly not read much in this thread or understand anything about how much work, manual that is, to get this to compile. If it was a simple script job for each unraid release, it would have been released shortly after. But it is not. If you want to test unraid releases the second they are ready, run a clean unraid build.

There is a tiny one character bug when you go to the settings of UD from the Main page and hit the done button. It then takes you to unraid_IP/Settimgs instead of unraid_IP/Settings. If you go from unraid settings to UD settings and hit Done, it works.