Understanding Emby connect

[leshkraven 2]

Hi

 

I have always understood Ec to allow the users I add to access my server.

They do not have admin privileges, I do. So when they sign in they should see the server name "emby" only right but not the IP and port 

 

In the photo one of my emby connect users chooses change server and the IP is showing, why ?

[Luke 42078]

Hi, shouldn't a user be able to know where they're going to connect to?

[leshkraven 2]

Hi

 

So what is the point of EC if they can just get the IP and port and just choose manual server instead for every time after ?

[Luke 42078]

20 minutes ago, leshkraven said:

Hi

 

So what is the point of EC if they can just get the IP and port and just choose manual server instead for every time after ?

I guess that is a side effect of displaying it, but there's another equally important reason for it. It's to make it clear that you're connecting to a server owned by someone else and not Emby. And that the owner of the server is providing the content, and not Emby. This is something that comes up all the time where let's say a server is being used to host pirated content, previously it would just appear as if the content was coming from Emby, and we've had our apps pulled from the stores on multiple occasions due to confusion over this. Now it's a little more clear to the appropriate people to go after the server owner and not us.

[leshkraven 2]

Ok that makes sense.

I have another issue atm, I have re added my EC user and they linked through the email they received.

The server showed but without IP this time, when they click it it just says unavailable  

 

What is causing this ?

[ebr 16182]

39 minutes ago, leshkraven said:

So what is the point of EC if they can just get the IP and port

Hi.  The point of Connect is not to hide anything.  Its just to make it easier because the end user doesn't have to know or type in an IP address.

[Luke 42078]

15 minutes ago, leshkraven said:

Ok that makes sense.

I have another issue atm, I have re added my EC user and they linked through the email they received.

The server showed but without IP this time, when they click it it just says unavailable  

 

What is causing this ?

Does a manual connection work for them? Does your server dashboard display the correct remote address?

[leshkraven 2]

Emby Theatre - Login manually IP+port works

Emby Threatre - Login Emby connect unable to connect

Login through Swizzin Suite Server side on browser Manually or any Emby connect account works everytime

 

Emby connect users are unable to connect to server even after their credentials are correct and accepted. They are unable to connect to server emby all lower case like in photo.

 

We all just recently reinstalled emby which was a newer version of the app. Could there be an issue with it ?

 

[Luke 42078]

Does your server dashboard display the correct remote address?

[leshkraven 2]

The server dashboard displays the correct IP but the port is different to the port I must enter when setting up manually in Em theatre.

 

I enter remote IP from the server dashboard fine, but I have to change the port to another that my server admin gave me to get access manually in em theatre

Edited May 2, 2025 by leshkraven

[Luke 42078]

That's the reason for Emby Connect not working. It is going to give the clients the addresses displayed on your server dashboard, so those need to be accurate.

It sounds like you need to configure your public facing router port in server network settings.

[leshkraven 2]

Hey

 

So local  http 8096 https 8920

public http 9940 https 9939 

 

9939 is the same showing as my admin sign in server side and theatre. 9939 is what I use to manually setup emby

 

Added user - My friend  gets the email and accepts. Signs into connect, sees server emby no IP or PORT no. clicks it and gets unable message

Edited May 2, 2025 by leshkraven

[leshkraven 2]

UPDATE:

 

I sudo remove the app on the server and reinstalled, it gave new network settings that I left this time.

 

Everything seems to work ok now. Very strange that it was working for some and not others before with the network settings.

 

Anyway seems to be ok now so must have been port related I think