saarg

I guess that would be the logical move, but we need to let this one live for a while until people notice. Or maybe just stop it from working so people notice?

Please use the correct support thread. You are not using our container.

Not sure why you need to route it through a VPN, but this is out of my scope to help with.

When we add the fix in the stable release, you should remove any scripts you have running. If you did it manually, you don't have to do anything. We are not only unraid users in linuxserver, so we want to concentrate our support on our own platforms. That is the main reason. But the 6.9 saga didn't help either. It's only 3 of us that is still reading the forums here at times. For best support, check out https://www.linuxserver.io/support

Neither unraid or the container use a public IP. You should get the same IP doing curl of config.io in both unraid and the container.

Please remove that log and pastebin it. It's a pain to scroll on a mobile device. It's also the unraid log, which will not help much getting help to get Jellyfin running. I don't remember if you are trying to install Jellyfin and use existing appdata or start from scratch (thank your log for that)? If you are not starting from scratch, please try it.

That is a question for the onlyoffice container you are using and not our nextcloud container.

Set the Daemon to at least 600, or else you will get banned from checkip. Is your dyndns provider supported by ddclient?

ddclient is running as long as the container is running and the config is copied to the correct place if it's edited. You have not supplied any usable info to be able to help you. Post the full logs and the docker run command (no template screenshots).

That is normal.

The support link goes to our support alternatives, and it's intentional. It doesn't make sense for us to give support on other platforms than our own as we are rarely reading this forum anymore. This is the way it will be with new container templates and the support link.

So Jellyfin pushed tonemapping to the stable builds? I fixed that for the nightly build, but I guess I forgot to add it to the stable build. The fix is the same as you have done by adding the icd file.

Did you follow the comments for cloudflare in the ddclient.conf file on theie GitHub repo? It has info on how to set it up and from the looks of it, you haven't read it.

It doesn't seem like you are running unraid, so you are in the wrong place for support. Join our discord server to get help.

I don't know why.

upstream_app needs to be all lowercase, so you need to change the container name. I have no idea about the location part as I'm no nginx wizard.

You have to point it to something, or else nginx doesn't know where to send the traffic.

Simply restoring the appdata should not lead to this. But with the limited info you supplied, it's hard to say what happened.

There is no workaround. You have exceeded the limit because you have tried too many times. You should have enabled staging to test getting the certs. You could use a duckdns domain until your domain is not banned anymore.

You are changing things you should not change. Change the port back to 443 and protocol to https in the proxy conf.

Have you modified the proxy conf or changed the container name?

Swag can't connect to nextcloud, so it's probably not on the same custom bridge.

Did you try to claim the server using the token? The correct env variable to use and where to get the token is in the readme.

I also asked you a question. Have you tried using the Plex claim?

Would be better if you described what you are seeing more in detail. What is the exact error message you are getting and when. Are you connecting from a computer on the same subnet as the Plex container? Also post your docker run command.