TCEmby1 8 Posted May 19, 2020 Posted May 19, 2020 (edited) I finally got 'https://mydomain.com'to work -- it automatically goes to port 443 so that's not needed. BUT why is 'https://' necessary? In the settings I have emby 'prefer but not require' secure connection... is there something else? 'mydomain.com' does not work and 'www.mydomain.com' does not work (unless i put :8096 after it) Edited May 19, 2020 by TCEmby1
TCEmby1 8 Posted May 19, 2020 Author Posted May 19, 2020 it ends up going to 'https://mydomain.com/web/index.html#!/home'
Luke 42077 Posted May 19, 2020 Posted May 19, 2020 And how does that differ from entering the full address?
TCEmby1 8 Posted May 19, 2020 Author Posted May 19, 2020 I edited my first post--basically 'mydomain.com' and 'www.mydomain.com' fail to connect. Only 'https://mydomain.com'and 'mydomain.com:8096' (unsecure) work.
TCEmby1 8 Posted May 19, 2020 Author Posted May 19, 2020 the connection times out. 'server has taken too long to respond'
rbjtech 5284 Posted May 19, 2020 Posted May 19, 2020 (edited) It would do - by not specifying https - it will default to http - port 80. It does not know your service is running on port 8096 unless you tell it with the :8096 .. You can either fix it by doing a PAT (Port Address Translation) on the router - ie your router accepts the Port 80 and translates it into Port 8096 before forwarding to emby. Or you can setup your Emby server to just use Port 80 instead of 8096 and modify your port forward. Then you can just use http:\\myserver.com and it will work. I do however strongly suggest you get SSL/https working and only allow that for external connections. Edited May 19, 2020 by rbjtech
darkassassin07 652 Posted May 19, 2020 Posted May 19, 2020 By default your web browser will attempt to connect using http and port 80 when given a web address that does not have https://, normally a web server would accept that connection on port 80 and return a redirect telling the browser to try the same request using https/443. From there you'd receive an http header telling the browser to always use https for this hostname. From then on giving the browser that hostname it will automatically redirect to https before attempting to connect. Emby does not do this on it's own (I imagine because it normally runs on non-standard http(s) ports). You can add this functionality yourself with cloudflare or a reverse proxy, or you can just remember to type https:// when connecting.
TCEmby1 8 Posted May 19, 2020 Author Posted May 19, 2020 I don't get it--It is defaulting to port 443 automatically, but only when specifying https:// if I specify http:// it times out
rbjtech 5284 Posted May 19, 2020 Posted May 19, 2020 I don't get it--It is defaulting to port 443 automatically, but only when specifying https:// if I specify http:// it times out See #8 above ..
TCEmby1 8 Posted May 19, 2020 Author Posted May 19, 2020 I think I get it now. I do have SSL set up and want to use it, but I don't want it to time out on people if other people try to log in and don't know to use 'https://' Defaulting back to SSL is preferred
rbjtech 5284 Posted May 19, 2020 Posted May 19, 2020 Normally you would get the web server to simply redirect you to https automatically, but I'm not sure if emby does this (I've never opened up http). Worth a try and see what it does
pwhodges 2012 Posted May 19, 2020 Posted May 19, 2020 Emby doesn't redirect http/port80 to https/port443 itself. Any reverse proxy can be set up to do that, and so is a specific reason for using one. I use Caddy because it does that completely automatically without needing to be configured (it was one of the things Caddy was created for!). Paul 1
TCEmby1 8 Posted May 19, 2020 Author Posted May 19, 2020 Thank you--Im so new at all of this.. I'll check caddy out!
pwhodges 2012 Posted May 19, 2020 Posted May 19, 2020 You might find my post here helpful. When I say "no configuration" (meaning "very little", of course!), that's only for Caddy. You will still need to forward ports 80 and 443 through the router. I would suggest running Caddy on those default ports, and having Emby on its default port of 8096 (you don't enable SSL in Emby if a proxy is doing it for you). You do have to remember with this setup that the ports you use outside your network and inside are different. But if your router will loop back (some people say "hairpin") requests made to the external address from inside, then you can use that everywhere - but not all routers do that. That's the way I run it, though. Paul.
TCEmby1 8 Posted May 20, 2020 Author Posted May 20, 2020 Thanks for all the input -- I'm learning a lot and loving Emby!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now