aptalca

Post your container settings

No issues at all with xfs formatted cache drive here (Samsung one, too)

As you can see at the bottom of the post you quoted, his issue was fixed when he deleted his appdata. I don't know what to tell you other than to say it is your appdata that's the problem. The file in question resides in the config folder and the path referenced in the log is merely a symlink that points to the file in your appdata folder.

If it's macvlan, it blocks connections between macvlan and host. Try to ping it from inside the letsencrypt container

Don't copy paste a conf from another source. Use an existing preset proxy conf and modify accordingly. The conf you posted above is missing all the ssl bits, and it tries to reverse proxy localhost, which won't work in a container. Also see the examples in the default site config for very basic confs

Check docker hub tags and you'll see the updates. Github repo also lists all the releases that will coincide with docker hub updates. We no longer do Friday updates. Instead, there are new builds pushed when either 1) there is a commit to the active branch 2) there is a new upstream release 3) the is an os package update

See two posts above yours

Could be a few things. If you're using btrfs cache pool, there is an existing unraid issue that causes it, not related to sab. You can also limit the number of processor cores sab uses so it doesn't use all during extraction

Add it to extra domains?

Realip module is already in there

Oh wait, I might be mistaken. It does have library selection for Plex but it might not have it for emby. You should ask on their github

Use the host ip and port for it

No idea what your issues are, but as a rule of thumb, don't update this container while you're away on vacation. Also, a backup plan is important (I have 3 vpn implementations running on 3 devices). With that said, my instance is rock solid. Runs for weeks and no issues.

I don't think it was confirmed as a btrfs bug. It could be specific to unraid's implementation of btrfs. Not sure. We need the unraid team to look into it and chime in.

That's a Plex issue as it's related to libs they package with their binary. You should ask on their forum.

Fyi, your sonarr is accessible from the internet. Everything works properly. Your issue is hairpin nat or nat loopback. PS. Don't forget to enable http auth for sonarr or you might notice strange shows added to your library

Literally two posts above your first one: "Check the Plex server log in the config folder to see why Plex is crashing. If it's corrupt database, restore from backup. Plex takes database backups automatically every 3 days"

Why did you change the port? Don't do things the conf doesn't tell you to do

See my response to someone else above

Check the Plex server log in the config folder to see why Plex keeps crashing for you

In ombi gui, open the emby server settings, there you can manually select which libraries you want ombi to scan

Check the Plex server log in the config folder to see why Plex is crashing. If it's corrupt database, restore from backup. Plex takes database backups automatically every 3 days

If you use the subdomain method, you don't need a base url

Your domain (external ip) is forwarded to your unraid gui. Fix your port forwarding. Follow the article I linked above

Letsencrypt server seems to reach a server, but it's not the letsencrypt container. So either your ip is incorrect, or your port forwarding. See here: https://blog.linuxserver.io/2019/07/10/troubleshooting-letsencrypt-image-port-mapping-and-forwarding/