Apache Proxy
This example demonstrates how you can configure Apache to act as a proxy for Open Peer Power.
This is useful if you want to have:
- a subdomain redirecting to your Open Peer Power instance
- several subdomain for several instance
- HTTPS redirection
Subdomain
So you already have a working Apache server available at example.org. Your Open Peer Power is correctly working on this web server and available at http://localhost:8123
Enable mod_proxy_wstunnel
by running if you encounter issues while serving Open Peer Power through your proxy:
To be able to access to your Open Peer Power instance by using https://home.example.org
, add the following file to /etc/httpd/conf/extra/
as opp.conf
and make sure that this file is read by Apache’s main configuration file /etc/httpd/conf/httpd.conf
If you don’t want HTTPS, you can change <VirtualHost *:443>
to <VirtualHost *:80>
or better consider redirecting all HTTP to HTTPS.
Multiple Instance
You already have Open Peer Power running on http://localhost:8123
and available at home.example.org as describe before. The configuration file for this Open Peer Power is available in /home/alice/.openpeerpower/configuration.yaml
You want another instance available at https://countryside.example.org
You can either :
- Create a new user,
bob
, to hold the configuration file in/home/bob/.openpeerpower/configuration.yaml
and run Open Peer Power as this new user - Create another configuration directory in
/home/alice/.homeassistan2/configuration.yaml
and run Open Peer Power usingopp --config /home/alice/.openpeerpower2/
In both solution, change port number used by modifying configuration.yaml
Start Open Peer Power: Now, you have another instance running on http://localhost:8124
To access this instance by using https://countryside.example.org
add to /etc/httpd/conf/extra/opp.conf
HTTP to HTTPS redirection
Add to your /etc/httpd/conf/extra/opp.conf