ShadowKindjal 19 Posted May 9, 2019 Share Posted May 9, 2019 Hi, I'm currently having an issue connecting to my webserver when I append the https port number after my domain. All of this was working yesterday with no issues so I'm not exactly sure what happened. I'm ablle to connect over HTTPS with a virtual server handled by apache (https://emby.domain.org/) but when I try to connect with the appended port number it never loads (https://emby.domain.org:8920/). The reason this is an issue is because it seems a lot of the apps are unable to connect to my server because my dashboard shows the second web address with the port number as my external access address. Therefore emby connect devices are pointed there and are unable to connect to my server but those who don't use the port number are able to connect just fine. Any help would be appreciated. Link to comment Share on other sites More sharing options...
Luke 36879 Posted May 9, 2019 Share Posted May 9, 2019 Hi, it sounds like you want to change the public https port number to 443, right? Link to comment Share on other sites More sharing options...
ShadowKindjal 19 Posted May 9, 2019 Author Share Posted May 9, 2019 Thank you for the quick reply. No, I'm fine with it being 8920. That's what I've been using this entire time. For some reason I just couldn't connect to it all of a sudden. And now it just started working again randomly. I apologize for wasting your time. If I could recreate the error I would. Link to comment Share on other sites More sharing options...
Luke 36879 Posted May 9, 2019 Share Posted May 9, 2019 But if you're accessing it without a port then how can the public port be anything but 443? 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