j0nnymoe

Can confirm, Nextcloud is a special case for us. Main thing is to make sure your image is up to date then proceed with the webui update.

This more a jellyfin question than docker question. I'm not a jellyfin or DLNA user, I'd suggest checking their docs seeing why it's doing this.

Container path should be `/music/` Host path should be `/mnt/disk2/Music` In jellyfin, you'd then select `/music`

Edit the template and add a `/music` mount and map that to your folder.

This is forum is for unraid support only. Please use our discord or discourse for support with our containers on other platforms.

This is a chrome issue not liking the self signed cert that the container generates. Unfortunately I'm not a chrome user so no sure what the fix is. I know there was a user that had the same issue earlier in this thread.

I personally just add the SMB shares via external storages. This is so that the user permissions on each share gets respected.

We've already stated we won't be supporting this container any longer.

I would suggest to ask over at the tvheadend forums, you'll likely get more help about this there. (Are you using unraid btw? Reason I ask, your UID/GID in the logs show 911 which isn't what it should be for containers.)

Is your disk full?

It's likely you won't be able to reverse proxy an IRC connection (Atleast to my knowledge)

quassel-web ≠ quassel-core.

Wait, penny just dropped, I've been looking at the default file for letsencrypt, not nextcloud itself. Get into the container of letsencrypt and see if you can `ping nextcloud`.

Ok, well looking at your default file, you've added a ton of stuff that isn't need. Confused why you've done that and used the subdomain proxy config aswell. You need to use the supplied default file, you've removed the bit that tell's nginx to use the proxy-conf.

502 usually means it can't communicate with the container. Is the nextcloud container still on the same custom bridge network as your letsencrypt container?

Yes that will work fine.

This thread is for users who need support on unraid. Please use our forum or discord for support.

This needs to be reported upstream to jellyfin then.

Could be a corrupted database? restore a backup of your appdata and see what happens.

You're best to report this upstream to Ombi direct.

When I wrote the article, I'm purely talking about the nextcloud container, Nothing else.

Already fixed and new image pushed.

If you wish to update via the webui, you have to wait for NextCloud to roll it out to you. (It's staggered for obvious reasons) There are instructions on the first post on how to update manually.

I always recommend using the SMB connection method with External Storages app.

These aren't our containers?