+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: WebOS error code -27 (/t-solved-webos-error-code-27)
WebOS error code -27 - SjoerdHekking - 2024-05-08
Dear reader,
I have read a ton of similar problems, to try and troubleshoot it myself. However, I am using Apache, combined with a reverse proxy and let's encrypt.
This has worked on dozens of devices, except for the WebOS app. Using the browser of the television does work, but is rather annoying to use, and above all, doesn't support all formats, thus, losing DV or HDR fallback support.
I read things on the nginx side, about x-header options, but if that's the case, how do I change it for apache correctly?
RE: WebOS error code -27 - TheDreadPirate - 2024-05-08
Apache has equivalent x-header options called "Header set X-Frame-Options". You either unset it or "allow-from" and provide your server's address.
https://stackoverflow.com/questions/17092154/x-frame-options-on-apache
RE: WebOS error code -27 - SjoerdHekking - 2024-05-08
(2024-05-08, 03:02 PM)TheDreadPirate Wrote: Apache has equivalent x-header options called "Header set X-Frame-Options". You either unset it or "allow-from" and provide your server's address.
https://stackoverflow.com/questions/17092154/x-frame-options-on-apache
Interestingly enough I thought I didn't set it, but it turns out, I did. Namely: Header set X-Frame-Options "sameorigin"
I changed it to: Header set X-Frame-Options "ALLOW-FROM http://your-server-address"
It does confuse me for, ALLOW-FROM is marked obsolete on MDN.