Remote Access

edited November -1 in General Discussion

This is a great feature of OpenLP. One that I will like to use in our church but I have a concern and it is this.

If OpenLP is configured, for example, to use http:\\192.168.1.1.

The remote control page is set to http:\\192.168.1.1. While the stage view is set to http:\\192.168.1.1\stageview.

Is there anyway to set things up so the remote control page is accessed as, for example, http:\\192.168.1.1\remote or set http:\\192.168.1.1 to be stageview?

Our users are tech-savvy and 'fiddlers'? Once the realise that they can control the software via a phone, strange things may happen. e.g. unwanted alerts. I imagine people are more likely to remember an ip address on its own rather than with the 'stageview' suffix.

 

Hope this makes sense

GloGee

 

Comments

  • edited October 2012

    No, those URLs are hard-coded.

    And it's http:// - http:\\ is not a valid URL.

  • edited October 2012
    It may be a bit of a pain, but you maybe able to use you router to deny or allow certain devices access.
  • edited October 2012

    Or buy another router and put your projection computer on a secure network.

  • edited October 2012

    Well technically you can do it, although with a very big "we don't support this, do at your own risk, we might break it later" disclaimer! It is also really only security by obscurity, if one of your congregation were to play around, look at the source, read this forum or install the OpenLP Android App they may soon workaround it. 

    But if you still really badly want to do it:

    If you're on Windows, go to C:\Program Files\OpenLP\plugins\remotes\html

    Here you can rename index.html to be say remote.html

    Then copy stage.html to index.html 

    From this point on:

    http://localhost:4316/ will be the stageview and http://localhost:4316/files/remote.html will be the remote view.

    However be aware that these changes will be lost if you upgrade OpenLP so you'd have to do them again. 

  • edited October 2012

    Thanks gushie.

    Appreciate that it is security by obscreity but would rather that.

    Any chance that this will this be addressed in a future release? I think that as it is it leaves too much scope for someone to change things inappropriately.

    Anyway off to try your suggestion.

    Will the switched html pages work with the android app? Will I need to set the appropriate details on the android app setup page.

  • edited October 2012

    I haven't tried the Android app with these changes, but as long as you copy the stage.html file (rather than rename), then all should be well. I don't believe the android app uses the index.html page.

    I think in the future we want to provide password protection for different pages, but can't say when it will happen.

  • edited October 2012

    I realise that this would come with an even larger 'if you do this, don't come crying to us if you break OpenLP' warning, but in theory would dropping a .htaccess and .htpasswd file into the 'html' directory give a simple way of passwording the two files?

    Unfortunately, I'm not on a machine with OpenLP on it at the moment to be able to test it for you... just wondering if the theory would work :)

  • edited October 2012

    No. Those files are Apache-specific, they don't work on other web servers like nginx or lighttpd, and they won't work with our built-in web server.

  • edited October 2012

    This would be a nice change to the defaults in the program.  I've started handing out this url but with tech teens etc in church would rather have the control one be an obscured URL and just let anyone have the stage url.  Password protected would be nice as well however that may be quite a bit of extra coding and change on the android app etc.

  • edited October 2012

    I'd use a firewall to block access from all but the ones that should have it.  A Little work ont he part of the tech guys to get set up, but would secure things. 

Sign In or Register to comment.