jellyfin-webos icon indicating copy to clipboard operation
jellyfin-webos copied to clipboard

Published 20 hours ago • verified publisher icon jellyfin

Unknown error when connecting

Open besendorf opened this issue 2 years ago • 10 comments

I just installed the 1.0.1 testing release but when entering my hostname the apps says: "Unknown error occured, are you connecting to a Jellyfin Server?"

How can I debug the app? I tried ares-inspect -d tv org.jellyfin.webos which returned Application Debugging - http://localhost:1178/devtools/inspector.html?ws=localhost:1178/devtools/page/27453fc1-e07d-487b but the website on localhost doesnt display anything and the app also doesnt start after entering the command

besendorf avatar Jan 10 '22 20:01 besendorf

I have an issue where entering the host doesn't work but using the IP does work Edit: just saw this #21

As for remote debugging WebOS Apps: https://webostv.developer.lge.com/common-page/faqs/debugging-web-inspector-not-working-chrome-v80/? Fastest workaround would probably be to download the Chromium v68 binary

samcon avatar Jan 10 '22 21:01 samcon

@besendorf Just to be clear (because you did comment in the other issue), were you able to connect after specifying the full host name, or did it still return an error?

anthonylavado avatar Jan 11 '22 16:01 anthonylavado

I changed the domain to a FQDN and then I received the error I described in this issue

besendorf avatar Jan 11 '22 19:01 besendorf

@besendorf Ah okay. I'm assuming you have a .home.arpa address as mentioned in the other issue?

The URL validation is from a older library so that's likely why it didn't accept it. We'll see how it goes after I remove that check.

anthonylavado avatar Jan 11 '22 19:01 anthonylavado

No I didnt configure the .home.arpa yet but I have a public FQDN with a Lets Encrypt certificate

besendorf avatar Jan 11 '22 19:01 besendorf

You might be running into #63 then. I don't have any other ideas (or solutions) right now...

anthonylavado avatar Jan 11 '22 20:01 anthonylavado

It seems #63 was the issue I had. I enabled a jellyfin.home.local domain in my router and now the client at least tries to connect but then the connection times out after ca 3s

besendorf avatar Jan 11 '22 21:01 besendorf

I ran into this issue recently. It's definitely due to the Lets Encrypt Root certificate expiration. Easiest way to fix this is to use a ZeroSSL cert on your Jellyfin subdomain instead of Lets Encrypt. I recommend using acme.sh to issue the cert.

bsmithio avatar Jan 30 '22 16:01 bsmithio

Seems that LG has allot of issues with letsencrypt: https://www.lgwebos.com/topic/7866-lg-webos-40-and-below-letsencrypt-root-certificated-expired/

Dycelll avatar Jan 30 '22 17:01 Dycelll

I no longer have this issue with 1.2.2 might be that my network changed though. Could be closed imo. Not sure about other people's issues

besendorf avatar Mar 06 '24 14:03 besendorf