NearWinter 1 Posted March 27, 2018 Share Posted March 27, 2018 (edited) My server is setup to require https, however when this option is enabled it appends "93" to the port thus everything fails to work properly. My external http port is 80, https port is 443. Internals are 8096 and 8920. When trying to connect to my domain it fails to connect and the address bar reads domain.com:44396. Example: I checked my system.xml to confirm that my ports are setup correctly, it just appends the "93" when redirecting. EDIT: Further testing this, I changed my internal http port to 8066 and updated it on the router for service port to be 80 and internal to be 8066. Doing the same test trying to access my domain appended "66" to my domain so it was domain.com:44366 Edited March 28, 2018 by NearWinter Link to comment Share on other sites More sharing options...
NearWinter 1 Posted March 28, 2018 Author Share Posted March 28, 2018 Anybody have any ideas for what might be going wrong? I suspect it's a problem with the server itself for it automatically appending parts of my internal port when requiring https to connect. Link to comment Share on other sites More sharing options...
Jdiesel 1113 Posted March 28, 2018 Share Posted March 28, 2018 What are you putting in for your external domain field? Your public https port should be "443" and your external domain "domain.com" Link to comment Share on other sites More sharing options...
NearWinter 1 Posted March 28, 2018 Author Share Posted March 28, 2018 (edited) Yes that is correct and is currently my setup. With require https turned off I can type in my domain name but it connects to the unsecured version. However if I type in https://domain.com it's successfully secured and uses my provided certificate. When I turn require https on, the website doesn't work at all because it keeps redirecting all requests to https://domain.com:44396. Note my domain is using dynamic dns to the WAN IP of my emby server. Edited March 28, 2018 by NearWinter Link to comment Share on other sites More sharing options...
Jdiesel 1113 Posted March 28, 2018 Share Posted March 28, 2018 What browser are you using? Maybe try clearing your browser cache. Link to comment Share on other sites More sharing options...
NearWinter 1 Posted March 28, 2018 Author Share Posted March 28, 2018 (edited) I've cleared browser cache and tried with exact same results on Google Chrome and Edge browsers. I originally suspected it might have been cache related but after changing my internal http port to 8066 to test, when connecting to my domain it then showed up as domain.com:44366 and again failed to connect Here's my port forwarding settings if that'll help any to get this resolved: Edited March 28, 2018 by NearWinter Link to comment Share on other sites More sharing options...
KMBanana 83 Posted March 28, 2018 Share Posted March 28, 2018 What are you running Emby on and what platform are you setting the port forwarding settings up on? Link to comment Share on other sites More sharing options...
NearWinter 1 Posted March 28, 2018 Author Share Posted March 28, 2018 Emby is running on a Windows 10 Professional PC, the port forwarding settings are set up through my tp-link router. Link to comment Share on other sites More sharing options...
Luke 37009 Posted March 29, 2018 Share Posted March 29, 2018 Please try again with the next release, thanks. Link to comment Share on other sites More sharing options...
NearWinter 1 Posted March 29, 2018 Author Share Posted March 29, 2018 Thanks Luke Link to comment Share on other sites More sharing options...
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