[Feature Request] Emby in Org - Allow for reverse proxy URLs that have custom ports #569
Comments
Merged
causefx
added a commit
that referenced
this issue
Oct 6, 2017
Fixed #186 - Added CouchPotato to Homepage Fixed #316 - Added Weather ticker to Org User menu Fixed #366 - Fixed Calendar Save on Edge Fixed #373 #863 - Fixed LDAP Binding with new option Fixed #441 - Added Open in New Window for Mobile Fixed #490 - Added Media Popups for all media Fixed #567 - Added Email section to email users Fixed #569 #620 - Added Emby URL to links Fixed #618 - Media Popups respect language now Fixed #644 - Added JSON to check Fixed #646 - Settings margins fixed Added Ping for each tab Added Splash screen Added LayerCake Theme Selection Added SpeedTest History Added Built-In Chat Added New Settings Page Added New Top Bar Menu Added Mass Email Added CouchPotato to Homepage Added Weather Ticker Fixed LDAP And More...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey @causefx -
We've talked at length about this over the previous month or so in Gitter, but I wanted to get it out as a tracked request, so that others can supply inputs/opinions. Let's get some more Emby love! ;)
Basically, I currently reverse proxy emby with the following URL:
https://emby.domainname.com:10443
(Port 10443 is needed to reverse proxy through a VPN layer that I always have on).
What I'd love to see is for the recently added emby media links on the Organizr homepage to resolve to my custom reverse proxied URL. Currently, the recently added media links will go to 'app.emby.media'.
Depending on what other uses want, maybe this could be a toggle setting inside the Emby settings tab? Something where an Org user could choose between 'Use reverse proxy URL' or 'Use default app.emby.media' as a resolver for all Emby links inside Org.
Thoughts?
The text was updated successfully, but these errors were encountered: