joepol 0 Posted November 29, 2021 Posted November 29, 2021 I have an Emby server behind a reverse-proxy at a non-root path on my domain. For example, https://mydomain.com/x/. On app.emby.media, if I try to connect to the server it will attempt to connect to https://mydomain.com/x:443/emby/system/info/public which is the incorrect path due to the ":443" being added. The solution is to just leave the port blank and Emby will then correct go to https://mydomain.com/x/emby/system/info/public. The Roku app, however, does not let you use an empty port. This makes it impossible to connect to any server behind a non-root path. As far as I can tell there's no workaround here that can be done from my end. The app would either need to allow an empty port or use some simple logic to place the port in the correct place.
Solution KMBanana 116 Posted November 29, 2021 Solution Posted November 29, 2021 Have you tried putting 00000 into roku? I think I remember that working as a workaround years ago, but have since switched to using a subdomain which is less prone to weird issues like this. 2
Happy2Play 9780 Posted November 29, 2021 Posted November 29, 2021 Yes, that would appear to be the workaround.
joepol 0 Posted November 29, 2021 Author Posted November 29, 2021 2 hours ago, KMBanana said: Have you tried putting 00000 into roku? I think I remember that working as a workaround years ago, but have since switched to using a subdomain which is less prone to weird issues like this. Thank you! Putting in all zeros worked!
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