SOLVED: struggeling with Hardware acceleration in docker (Intel)

[TheDreadPirate]

The published server URI is for using an alternate address when using service discovery with local clients. For example, instead of a client discovering your server and simply using the LAN IP on port 8096, you can use the URI field to publish your reverse proxy address.

I'm assuming you are using a reverse proxy, and I'm assuming it is Nginx. Can you share your config via pastebin? Censor the domain name.

[Tone]

I'm using apache as reverse proxy, this is the jellyfin-config in my apache:
https://pastebin.com/01gFktPN

[TheDreadPirate]

Is there more? That is just the location, but what about all the configs and options for https?

I'd like to see the entire virtual host config (censor the domain).

[Tone]

My virtual host is kind of a mess.
I deleted all other locations for privacy reasons, they shouldn't matter in my opinion.

I noticed I have some websocket rules for vscode.
Don't know if they are a problem. What do you think?

https://pastebin.com/1vvWDje9

[TheDreadPirate]

Your CSP is way off.

Code:

"default-src https: 'unsafe-eval' 'unsafe-inline'; img-src https: 'unsafe-eval' 'unsafe-inline' 'self' data:; object-src 'none'; frame-ancestors 'self'; connect-src 'self' wss:"

Our Apache docs don't have any CSP documentation, but out Nginx documentation does.

Code:

"default-src https: data: blob: ; img-src 'self' https://* ; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' https://www.gstatic.com https://www.youtube.com blob:; worker-src 'self' blob:; connect-src 'self'; object-src 'none'; frame-ancestors 'self'";

You should be able to use our Nginx CSP config directly paste it into your Apache CSP config.

[Tone]

That was the reason!

Interesting that only edge and chrome had a problem with my config.
Maybe I find which exact setting in the line was the problem.

Thanks for your EXCELLENT support!
That really cannot be taken for granted.