search

jellyfin / jellyfin-webos

WebOS Client for Jellyfin
https://jellyfin.org
Mozilla Public License 2.0
638 stars 65 forks source link

Unknown error when connecting #71

Open besendorf opened 2 years ago

besendorf commented 2 years ago

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

samcon commented 2 years ago

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

anthonylavado commented 2 years ago

@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?

besendorf commented 2 years ago

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

anthonylavado commented 2 years ago

@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.

besendorf commented 2 years ago

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

anthonylavado commented 2 years ago

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

besendorf commented 2 years ago

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

bsmithio commented 2 years ago

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.

Dycelll commented 2 years ago

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

besendorf commented 6 months ago

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