SOLVED: lan connection error

[lokide]

Hello,

First of all, thank you for jellyfin

I'll try to describe my problem.

Everything works great, I have activated https mode, since I have a domain, I have the ssl certificate by let's encrypt and everything works as expected.

My problem is the following:
Last week there were some problems with internet, so I wanted to connect to jellyfin using the local lan ip address, instead of the domain. Not working.

If I try from the browser, works with no problem, the server is detected, I can login, etc, of course there is an error about the certificate since it's connected with the domain.

If I try from my android phone connected to the wifi, using the jellyfin app or the tv, using the jellyfin app, connected with ethernet, I can't connect to my local server, it only works with the domain connected to the let's encrypt certificate.

The only reason I want to be able to connect using my lan address is that if internet for some reason goes down, I can't reach my homeserver, since the ip is no longer reacheble since there is no internet and in italy we have dynamic ip addresses.

Hope I was clear enough.

To recap:

From Browsers
https://domain:8920 WORKS
https://192.168.1.18:8920 WORKS

From TV/Android using the Jellyfin APP
https://domain:8920 WORKS
https://192.168.1.18:8920 NOT WORKING

So my question is, I'm doing something wrong? Is there a setting to being able to use both my domain address and the local lan one from android/tv apps? Or it's some kind of limitation of the apps? Something about the certificate or maybe there is a setting somewhere I've set wrong?

My homeserver for now runs on windows on latest version, 10.10.6

Thank you.

[bitmap]

The cert may be the issue. I recall there was a problem (?) with the Android app where it wouldn't work when you're essentially asking for HTTP when Jellyfin is set up with HTTPS through the software itself. The recommended approach is definitely a reverse proxy, which works exactly as you'd like, except serving HTTP on LAN. I don't believe that the apps have a way to acknowledge and proceed with an invalid cert, so they just don't function. This is actually decent behavior, since most of the time you don't want to connect to a site with an invalid cert.

[TheDreadPirate]

You said you got a valid cert from LE, but are you using a reverse proxy or are you using Jellyfin's built in https server? Since you are using port 8920, I am assuming you are using the built in https functionality (not recommended).

Did the installed cert expire? LE certs are only valid for 90 days. And Jellyfin does not have an auto-update mechanism.

[lokide]

I'm using the built in functionality, my cert autorenew itself using a script I've setup and it's currently valid.

[TheDreadPirate]

I'd imagine since you aren't using the domain name that the cert is no longer "valid". When you access Jellyfin via the IP from a browser, do you see a warning?

[lokide]

I'd imagine since you aren't using the domain name that the cert is no longer "valid".  When you access Jellyfin via the IP from a browser, do you see a warning?

Yeah, of course, the warning saying that the certificates is not valid since it's for the domain, but you can ignore the warning and move on on browsers, I was hoping at least that I could ignore it also in the apps, or something else.

What else I could do to make it working like this?

[TheDreadPirate]

You can't. There is no way to ignore those warnings on most TV devices (Roku, Android TV, etc.) or within most Android/iOS apps.

If you're on LAN just use http for devices that stay on LAN?

For devices that come and go, as long as you have NAT loopback enabled or setup custom DNS entries on your router the traffic will stay local when using your domain name.

[lokide]

You can't.  There is no way to ignore those warnings on most TV devices (Roku, Android TV, etc.) or within most Android/iOS apps.

If you're on LAN just use http for devices that stay on LAN?

For devices that come and go, as long as you have NAT loopback enabled or setup custom DNS entries on your router the traffic will stay local when using your domain name.

Ok, that solved my issue. I tried this way before, but I had the idea it wasn't working. After your reply I tried again to remove the "force https", but this time I've restarted the jellyfin server and works.

I'd say we can close this. Thanks for the brainstorming!