Figuring how Emby Connect works, but...

[Cphusion 3]

8 minutes ago, Happy2Play said:

Can you connect to your server with only this address?

Yes I can connect with that because I specifically opened that port to test it. What I want is my webserver port(443) to be advertised in Emby Connect because what is currently also working is connecting from https://emby.mydomain.com .  Currently Emby Connect times out, when trying to connect to my server and looking at Firefox dev tools console it seems be wanting to connect to my LAN address instead of my WAN address

 

Edited May 23, 2024 by Cphusion

[Happy2Play 9780]

Devs will have to comment or someone else who has done this as I would expect dashboard would have to be configure 443 also.

But I really don't see the point of using Connect if you have a Domain though.

[Cphusion 3]

So I think this is the problem, for some reason Emby Connect is trying to connect to my lan adress and port 8096 instead of my wan adress.

 

I see this in Firefox dev tools: http://172.30.5.5:8096/emby/system/info/public

When I use my wan adres for that I get the information that Emby Connect seems  to be looking for and when I go to my reverse proxied connection for emby: https://emby.example.com/system/info/public I get my Emby server information as well.

So now I guess the thing I still have to figure out is how to get Emby to display the WAN adress to Emby Connect instead of the LAN adress?

 

 

[Cphusion 3]

1 minute ago, Happy2Play said:

But I really don't see the point of using Connect if you have a Domain though.

The point is to make it easy for computer illiterate users, that I  don't have to explain to them how to add a custom server each time they add a new device.

[Cphusion 3]

7 hours ago, ebr said:

Why isn't it going to work?   Those values are there specifically for you to tell the server how to advertise its address/port.

You were right, this works. I wasn't seeing you train of thought. Since I am running Emby in a container I was thinking in container context when it comes to port and not specific to Emby, so I missed why that that should work when you first mentioned it. Greatly appreciated!

I changed two things.

1.  Public https port number: 443

2. External Domain: emby.mydomain.com

That caused the WAN address to show up as: https://emby.mydomain.com, when I now connect through Emby Connect I am instantly able to connect to the server. This also seems to have solved my authentication problem and my understanding of how Emby Connect works. The only thing that doesn't work is retrieving the server info. Another problem for another day.

Thanks for your help! And thanks to everyone who took the time to respond!

Edited May 23, 2024 by Cphusion