Emby Connect does not find my server via automatic IP detection

[toooo 8]

@ebr starting a separate topic to troubleshoot Emby Connect.

Using the automatic server IP detection - instead of entering a domain name on the network settings page - Emby Connect is unable to find my server.

Summarized below are configuration and testing combinations. The underlined bits are the ones that do not behave as expected, but are a main purpose of Emby Connect, as I understand it. I am not concerned with the certificate issue yet, as I am intending to use letsencrypt's newly available "short-term" certificates that are IP-based rather than domain-name-based.

A. Using server's automatic IP detection (no domain entered on server):

1. With only my secure port exposed externally
   1. Emby Connect does not connect (using https://IP:8920)
   2. Navigating directly to http://IP:8196 does not connect (expected)
   3. Navigating directly to https://IP:8920 connects, but certificate does not match domain (expected)
   4. Navigating to http://domain:8196 does not connect (expected)
   5. Navigating to https://domain:8920 connects, certificate is good
2. With both ports exposed externally
   1. Emby Connect does not connect (using https://IP:8920)
   2. Navigating directly to http://IP:8196 redirects to https://IP:8920
   3. Navigating directly to https://IP:8920 connects, but certificate does not match domain (expected)
   4. Navigating to http://domain:8196 redirects to https://IP:8920
   5. Navigating to https://domain:8920 connects, certificate is good

B. Using domain entered into my server:

1. With only my secure port exposed externally
   1. Emby Connect connects (using https://domain:8920)
   2. Navigating directly to http://IP:8196 does not connect (expected)
   3. Navigating directly to https://IP:8920 connects, but certificate does not match domain (expected)
   4. Navigating to http://domain:8196 does not connect (expected)
   5. Navigating to https://domain:8920 connects, certificate is good
2. With both ports exposed externally
   1. Emby Connect connects (using https://domain:8920)
   2. Navigating directly to http://IP:8196 redirects to https://IP:8920
   3. Navigating directly to https://IP:8920 connects, but certificate does not match domain (expected)
   4. Navigating to http://domain:8196 redirects to https://IP:8920
   5. Navigating to https://domain:8920 connects, certificate is good

 

---- Router config

8920 @modem -> 8920 @router -> 8920 @server ; UDP & TCP

8196 @modem -> 8196 @router -> 8196 @server ; UDP & TCP ; insecure port (this forwarding is turned ON/OFF during troubleshooting)

 

---- Server config (entering or clearing the domain name is the only troubleshooting I do in the server settings)

 

---- Using Emby Connect (https://IP:8920), server does not connect.

 

---- Navigating to https://IP:8920 directly (same as Emby Connect), server connects, but the certificate does not match since it is associated with my domain and not my IP.

 

[ebr 16330]

Hi.  Let's re-evaluate once you correct the cert problem.

There is no "magic" in Connect.  It is nothing but a lookup service so that you don't have to know the IP address.