Can't login to emby server via domain

[kierankihn 0]

I am trying to login to my emby server with my domain, but I received an error "Can't connect to the server".

I've tried filling in https://emby.kierankihn.com for host, and filling in 443 for port.

In Kodi's log, the requested url is correct, like so:

2024-01-20 09:25:13.758 T:7920     info <general>: EMBY.emby.emby: tryConnect url: https://emby.kierankihn.com:443
2024-01-20 09:25:13.759 T:5544     info <general>: EMBY.emby.http: THREAD: --->[ async queue ]
2024-01-20 09:25:13.786 T:7920    error <general>: EMBY.emby.http: [ ServerUnreachable ]
2024-01-20 09:25:13.786 T:7920  warning <general>: EMBY.emby.http: Request no send, retry: 1
2024-01-20 09:25:13.806 T:7920    error <general>: EMBY.emby.http: [ ServerUnreachable ]
2024-01-20 09:25:13.808 T:3168     info <general>: EMBY.emby.emby: THREAD: --->[ Reconnecting ]  / 
2024-01-20 09:25:13.808 T:3168     info <general>: EMBY.emby.emby: Emby client already closed
2024-01-20 09:25:14.809 T:3168     info <general>: EMBY.emby.emby: Reconnect try again:  / 
2024-01-20 09:25:24.810 T:3168     info <general>: Skipped 9 duplicate messages..
2024-01-20 09:25:24.810 T:3168     info <general>: EMBY.emby.emby: Reconnect try again:  / 

If I turn on debug logging, I get an extra log like this:

2024-02-06 09:36:47.095 T:1356    debug <general>: EMBY.emby.http: [ ServerUnreachable ] {'url': 'https://emby.kierankihn.com:443/emby/system/info/public', 'timeout': (15, 300), 'verify': True}

But in my clash client (a network proxy tool), I can't find the request record

In this case, I also cannot find any record of the request in the nginx logs.

Screenshot link is https://github.com/MediaBrowser/plugin.video.emby/assets/114803508/ba3af3de-30c0-4333-85c5-8c932a9d5f68.

I've also tried filling in emby.kierankihn.com for host, and filling in 443 for port.

In Kodi's log, the requested url is over http instead of https

2024-01-20 09:54:30.012 T:5416     info <general>: EMBY.emby.emby: tryConnect url: http://emby.kierankihn.com:443
2024-01-20 09:54:30.217 T:3132     info <general>: EMBY.emby.emby: Reconnect try again:  / 
2024-01-20 09:54:31.010 T:5416    error <general>: EMBY.emby.http: [ ServerUnreachable ]
2024-01-20 09:54:31.010 T:5416  warning <general>: EMBY.emby.http: Request no send, retry: 1
2024-01-20 09:54:31.217 T:3132     info <general>: EMBY.emby.emby: Reconnect try again:  / 
2024-01-20 09:54:32.018 T:5416    error <general>: EMBY.emby.http: [ ServerUnreachable ]
2024-01-20 09:54:32.217 T:3132     info <general>: EMBY.emby.emby: Reconnect try again:  / 
2024-01-20 09:54:42.220 T:3132     info <general>: Skipped 9 duplicate messages..
2024-01-20 09:54:42.220 T:3132     info <general>: EMBY.emby.emby: Reconnect try again:  / 
2024-01-20 09:54:52.222 T:3132     info <general>: Skipped 9 duplicate messages..
2024-01-20 09:54:52.222 T:3132     info <general>: EMBY.emby.emby: Reconnect try again:  / 

If I turn on debug logging at this point, I get the same message as above:

debug <general>: EMBY.emby.http: [ ServerUnreachable ] {'url': 'https://emby.kierankihn.com:443/emby/system/info/public', 'timeout': (15, 300), 'verify': True}

In my clash client's log, I found a request sent to emby.kierankihn.com on port 80 (not 443)

Screenshot link is https://github.com/MediaBrowser/plugin.video.emby/assets/114803508/2311b9e8-f462-4c35-90b9-83bbee4d6dec.

In my nginx's log, my server returned a 301 to this request (redirected it to https).

*.*.*.* - - [06/Feb/2024:01:54:10 +0000] "GET /emby/system/info/public HTTP/1.1" 301 169 "-" "python-urllib3/2.1.0"
*.*.*.* - - [06/Feb/2024:01:54:11 +0000] "GET /emby/system/info/public HTTP/1.1" 301 169 "-" "python-urllib3/2.1.0"

If I fill in my server's IP address for host and fill 8096 for port, I can connect to my server successfully.

However, it's not secure to access directly with ip and port (especially when I need to expose the port to the public internet), so I'd like to access via my subdomain and https. Is there a way for me to do this?

[Luke 37071]

Hmm, maybe some kind of client-side error in Kodi before the request even goes out?

[quickmic 1347]

2 hours ago, kierankihn said:

debug <general>: EMBY.emby.http: [ ServerUnreachable ] {'url': 'https://emby.kierankihn.com:443/emby/system/info/public', 'timeout': (15, 300), 'verify': True}

It's not a plugin/Kodi issue. The message is quite likely correct. However, I tested here from my site with your url and I passed the initial public info request.

This tells me, your client seems to block the request. Firewall? URL or maybe the complete Kodi app is blocked. Complete app is unlikely, cause you said http works?

What about the nginx redirect, may there is something wrong in the config? Could you try without nginx?

btw: login url is "https://emby.kierankihn.com" and port 443 like in the first screenshot

 

Edited February 6 by quickmic