Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change application URL for front-end when using reverse proxy #342

Open
Clock1932 opened this issue Mar 4, 2015 · 7 comments
Open

Change application URL for front-end when using reverse proxy #342

Clock1932 opened this issue Mar 4, 2015 · 7 comments

Comments

@Clock1932
Copy link

Hi there!

I installed HTPC-Manager last week - great stuff! There is however one thing I havn't figured out yet, and I'm not sure if this is possible in the current version.

From a usability and security perspective I have placed all applications (including HTPC-M) behind a Apache reverse proxy with SSL encryption and authorisation. Therefore, the specified hostnames in the HTPC-M configuration do not match the actual URL of the application (for the end-user). Therefore I would to have the opportunity to specify the front-end link to each application in the configuration.

Example:
Current SabNZBd link in HTPC-M front-end: http://127.0.0.1:8080/sabnzbd/
Desired SabNZBd link in HTPC-M front-end: https://domain.nl/sabnzbd/

Regards!

@Clock1932 Clock1932 changed the title Change link to back-end applications when using reverse proxy Change application URL for front-end when using reverse proxy Mar 4, 2015
@Hellowlol
Copy link
Contributor

That would be a nice improvement, in the meantime you can add those links in "other link"

@Clock1932
Copy link
Author

Clock1932 commented Mar 4, 2015 via email

@Hellowlol
Copy link
Contributor

Just remember you would have to redo them on each update.

@l-t-k
Copy link

l-t-k commented Mar 17, 2015

I'm running the same setup as you do, but not experiencing any problems. I have just point the build in apps to localhost like this:
1
2

And for the others links, just follow @Hellowlol

And of course, with this setup you should always use HTPC from your specified external domain name, but that is just what you want right? Make use of your easy to use and remember domain name.

@Clock1932
Copy link
Author

The apps / htpc UI is working correctly using the settings identical to
yours, only the UI link to the actual backend application (e.g. 'download'
title in the HTPC UI pointing towards the actual SABnzbd application) isn't
working properly due to the different front-end URL.
Op 17 mrt. 2015 20:56 schreef "kooimens" [email protected]:

I'm running the same setup as you do, but not experiencing any problems. I
have just point the build in apps to localhost like this:
[image: 1]
https://cloud.githubusercontent.com/assets/3150962/6696189/d0048cb8-cce7-11e4-96f5-0901f17c22a6.jpg
[image: 2]
https://cloud.githubusercontent.com/assets/3150962/6696190/d00540b8-cce7-11e4-8577-7d4a968f32d8.jpg

And for the others links, just follow @Hellowlol
https://github.com/Hellowlol


Reply to this email directly or view it on GitHub
#342 (comment).

@l-t-k
Copy link

l-t-k commented Mar 18, 2015

Hmm I think it's some of the issues hellowlol fixed in his version of HTPC. Try his fork! It's better in many ways.

@Hellowlol
Copy link
Contributor

@kooimens I have fixed other issues regarding ssl.
I'll add support for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants