port in app should change if user specifies HTTPS

[displayname0504 11]

When a user is connecting their app to a server, if they specify HTTPS, the port should change to 8920. 

Ideally, the user should put in the url, checkbox for http/https, and then port could be changed if not one of the default http/https ports.

[Neminem 1518]

No because I use a different port.

[displayname0504 11]

Right. You can still modify the port, but it default loads the http port. So if you select the https port, it can update to the https port number, still leaving the option to update it

[Neminem 1518]

Well if it should default to something else !!

It should default to its proper SSL / https port : 443

[Luke 42077]

1 hour ago, Neminem said:

Well if it should default to something else !!

It should default to its proper SSL / https port : 443

It makes the most sense to match the server default.

[displayname0504 11]

I agree, but the default ports for emby are 8096 (HTTP) and 8920 (HTTPS), so if we specify https in the app, the port should switch to 8920. (user can still change)

 

[brothom 177]

Personally I would prefer something like this:

http(s) are/should always the same port (with the exception of 443) the only real deviation could be on ip-adress level, so why bother users even showing the field when https://example.com:3306 shouldn't be supported anyway?

Another way would be to have an "advanced" section with a checkbox:

 

I'm willing to bet more than 80% of the server are set up "conventionally", using basics 8080, 80, 443, etc so users shouldn't be bothered by technical terms like port numbers by default. Every user I've had to set up so far got confused to what a port even is.

Edited July 24, 2025 by brothom

[displayname0504 11]

This is exactly what I would love

[ebr 16169]

1 hour ago, brothom said:

Personally I would prefer something like this:

Hi.  These selections don't make sense to me:

Whether you enter an IP address or a domain name, the protocol is still there... Now, one can argue it doesn't make much sense to use https with an IP address, but nothing really precludes it.

1 hour ago, brothom said:

https://example.com:3306 shouldn't be supported anyway?

Why not?

1 hour ago, brothom said:

I'm willing to bet more than 80% of the server are set up "conventionally", using basics 8080, 80, 443,

I believe that would be a bad bet since our defaults are 8096 and 8920.  My bet would me most are setup that way.

[displayname0504 11]

I should have clarified my response as well, I was rushing and didn't have full coffee yet.

http/https as the dropbox. That makes sense.

Then, if they select http, the port should fill in to 8096, if they select https, 8920.  It's still a writable field, so the user can change it. But the defaults fill in. No need for an advanced checkbox, etc.

[brothom 177]

38 minutes ago, ebr said:

I believe that would be a bad bet since our defaults are 8096 and 8920.  My bet would me most are setup that way.

I'm actually really curious about this. The default port is 8096 you're right, but for external access using a domain name is much more convenient.

The application might be running on a local port of 8096, but traffic may also be forwarded to that port (at least that's how I setup my Emby).

[Neminem 1518]

Here is my setup.

Emby server 8096

NPM server input 8096 output 443 with ssl certificate.

Router port forward input 443 output 433 to NPM from internet

In this setup I have no need for 8920.

I would preferer it to default to 443 when user types https://myserver.mydomain.io

Edited July 24, 2025 by Neminem

[ebr 16169]

5 hours ago, brothom said:

The default port is 8096 you're right, but for external access using a domain name is much more convenient.

Yes but many of our users are not necessarily that sophisticated.  I'm sure most of the responses out here will be what you are expecting because it is mostly from the power-users who have things like their own domain names, reverse-proxies, etc.  But the majority of people use products in the simplest way possible - with all default settings. 

[displayname0504 11]

On 7/24/2025 at 3:49 PM, ebr said:

Yes but many of our users are not necessarily that sophisticated.  I'm sure most of the responses out here will be what you are expecting because it is mostly from the power-users who have things like their own domain names, reverse-proxies, etc.  But the majority of people use products in the simplest way possible - with all default settings. 

100% this. I am the admin, but have to walk people through connecting. The fewer clicks and modifications, the better

[ados8000 50]

What about a server side port sync?
Looking to get ride of the custom port and use 443 so I don't have to port translate.
The problem is having to change the devices, some family are not technical.
Could the app sync the port so that existing setups already connected could have their port changed at the server and all the connected apps change to match.

[Luke 42077]

23 hours ago, ados8000 said:

What about a server side port sync?
Looking to get ride of the custom port and use 443 so I don't have to port translate.
The problem is having to change the devices, some family are not technical.
Could the app sync the port so that existing setups already connected could have their port changed at the server and all the connected apps change to match.

Hi, as soon as you change the port on the server, the apps will become disconnected. Therefore, they need to know how to connect to your server after that, meaning, they need to know the new server url.

If you use our Emby Connect feature, it can help with this: Emby Connect

But you will have to take the time to get to know the differences between Emby Connect and locally managed credentials on your server.

My suggestion: Keep doing what you're doing and just deal with the one-time disruption of updating the server connection info. You're probably not going to be changing the port number very often.

[ados8000 50]

I found a workaround but for a cleaner setup it means device reconfiguration.
Unusual port choice for HTTPS as it goes against the industry default .
Migrating over wont be that much of a hassle, should have done it from the beginning over avoiding a port change in setup .

Edited October 26, 2025 by ados8000