LG Webos app Error 27

[skew78]

Hi,

I have 2 Jellyfin servers. Both are accessed through URLs with a path like https://server.example.com/user/jellyfin/

On the same TV:

• Server A works
  
• Server B worked at first
  
• after I disconnected Server B from the TV app, I could no longer reconnect it
  

Now:

• on LG WebOS, Server B gives error -27
  
• on Samsung TV, Server B says no users found
  
• on PC/browser, both servers work fine
  

I reinstalled Jellyfin on Server B, and after reinstall the browser showed a different/incompatible server warning for the same URL. Logs show:

• System initialisation detected. Seed data.
  
• web auth still succeeds afterward
  

I also checked versions:

• Server A was 10.11.6, Server B was 10.11.8
  
• I updated Server A to 10.11.8 too, and it still works
  
• so this does not seem to be caused by 10.11.8 alone
  

I already tried:

• delete/re-add server in TV app
  
• uninstall/reinstall TV app
  
• reinstall Jellyfin on Server B
  
• exact URL with trailing slash
  

Does this sound like a TV app cache / stored server identity issue after reinstall ?
Is there a known way to fully reset that association on LG WebOS / Samsung TV ?
It seemed I trying everything and nothing works.

Thanks.

[esjaysee]

Hi,

I have 2 Jellyfin servers. Both are accessed through URLs with a path like https://server.example.com/user/jellyfin/

On the same TV:

• Server A works
  
• Server B worked at first
  
• after I disconnected Server B from the TV app, I could no longer reconnect it
  

Now:

• on LG WebOS, Server B gives error -27
  
• on Samsung TV, Server B says no users found
  
• on PC/browser, both servers work fine
  

I reinstalled Jellyfin on Server B, and after reinstall the browser showed a different/incompatible server warning for the same URL. Logs show:

• System initialisation detected. Seed data.
  
• web auth still succeeds afterward
  

I also checked versions:

• Server A was 10.11.6, Server B was 10.11.8
  
• I updated Server A to 10.11.8 too, and it still works
  
• so this does not seem to be caused by 10.11.8 alone
  

I already tried:

• delete/re-add server in TV app
  
• uninstall/reinstall TV app
  
• reinstall Jellyfin on Server B
  
• exact URL with trailing slash
  

Does this sound like a TV app cache / stored server identity issue after reinstall ?
Is there a known way to fully reset that association on LG WebOS / Samsung TV ?
It seemed I trying everything and nothing works.

Thanks.

Are both running on the same computer?

[skew78]

No, they are two separate app hosts.
I access them through different HostingByDesign (https://hostingby.design/app-hosting) instance URLs:
xxxx.lw.itsby.design and xxxx.lw.itsby.design. Xxxx being different letter or numbers
I don’t know if they happen to be on the same physical machine underneath.

[skew78]

I tried connecting thtough jellyfin app on xbox, and it works perfectly. The app on LG is outdated, it's from 03.2024. It it possible to developer to update app for LG Webos ? Maybe it's the problem

[KimNoSubstitute]

Yeah, the WebOS app hasn't been updated since 2024.

Anyway, it can be fixed by adjusting the nginx config. This issue discusses it, and the sample conf has it fixed.
linuxserver/reverse-proxy-confs#731
https://github.com/linuxserver/reverse-p...onf.sample

[dreamon]

The Jellyfin WebOS app is not actually a client, it's just an official wrapper that packages the standard Jellyfin web interface into a native application for LG smart TVs.

lucky for us, now there are frequently updated open-source clients available for webos that you can use, give them a try:

MoonFin:
https://github.com/Moonfin-Client/Smart-TV

LiteFin
https://github.com/MoazSalem/litefin

moonfin will be available on LG Apps store really soon (dev said it might take a week until lg staff reviews the app).

for now, you are going to sideload them via developer mode.

both clients require your Jellyfin server to be updated to at least version 10.11.x (ideally 10.11.11).