how to get the port number off of my domain address?

[Mopar 0]

I know this has been asked before, and ive tried (or tried to understand at least) a few things in the past but could never get it to work. i kinda forgot about it for a while but now its bothering me again. So, I have a domain name registered for my server and an ssl cert. remote access is all good on everything with all my users on the apps/emby connect thing all that. everything is smooth. the issue is if im on a pc and want to go to my site on a browser, whether remote or on my lan, i have to put the port number at the end or else it wont load. 

so, www.mydomain.com always comes back nothing. not working. but www.mydomain.com:8096 works and seems to redirect to www.mydomain.com:8920 i just want it to be www.mydomain.com. i tried changing the ports in the emby dashboard from 8096 8920 to 443 which, from what I had come to understand i think was suppose to "fix" it, but it just took my whole server/website down until i reverted to the default ports. then all was good again except with having to go back to adding the port number after the .com. 

So, what am I doing wrong and how do I fix this? explain like im a big dumb idiot cause I guess I am one lol. Ill also note, I was using my isp providers router/modem last  I tried (fiber). I have moved since then to a different state, and again am using my isp's modem but a different isp (cable but at least still gigabit). From what i understand is your isp can actually block you from using the 443 port to send traffic to and they have that locked down for their own use? Again im not sure if i fully understand thats the case or not or if thats even relevant but figured I would mention it just in case. I had also seen about running a reverse proxy to forward it to 443 but couldnt really get it to work. 

[Abobader 3464]

Hello Mopar,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

[seanbuff 1316]

1 hour ago, Mopar said:

www.mydomain.com:8096 works and seems to redirect to www.mydomain.com:8920 i just want it to be www.mydomain.com

Using HTTPS automatically defaults to port 443. If you are running your Emby Server with HTTPS on a different port i.e. 8920, then you will always need to enter it. So in order for you to use your https domain without having to enter a port - you will need to make use of port 443.

A few things you can check:

1. Check with your ISP, do they allow you to use port 443?
2. If so, change the configuration in your routers port forwarding to listen for 443 instead of 8920
3. Then in your Emby Server 'Network' settings, set your Local and Public to 443 (yes they can be different but lets keep it simple to start with)
4. If that works, then happy days.

Alternatively, considering running a reverse proxy to handle this for you (including the cert renewals) - Caddy is a very simple and effective tool

 

[Mopar 0]

1 hour ago, seanbuff said:

Using HTTPS automatically defaults to port 443. If you are running your Emby Server with HTTPS on a different port i.e. 8920, then you will always need to enter it. So in order for you to use your https domain without having to enter a port - you will need to make use of port 443.

A few things you can check:

1. Check with your ISP, do they allow you to use port 443?
2. If so, change the configuration in your routers port forwarding to listen for 443 instead of 8920
3. Then in your Emby Server 'Network' settings, set your Local and Public to 443 (yes they can be different but lets keep it simple to start with)
4. If that works, then happy days.

Alternatively, considering running a reverse proxy to handle this for you (including the cert renewals) - Caddy is a very simple and effective tool

 

thanks that seems to have actually worked pretty easily. Now it makes me think that maybe my last isp was either blocking access to forwarding to 443 or that i may have just done something stupid or overlooked something in the past.