This area is subject to updates in the future, it's not fully up to date with AzuraCast version 16.1.
If you use the recommended Docker installation method for AzuraCast, you can configure your installation to sit behind a nginx proxy that can also handle other web sites on the same host. This allows you to host, for example, your station's web site on the same server as your AzuraCast installation.
Follow the steps below to configure your installation for multisite support.
Most users prefer to use a proxy manager that includes a GUI for easier management of the proxy. There are a lot of different tools for this one of which is the Nginx Proxy Manager which uses NGINX and includes an easy to use GUI and automatic Let's Encrypt SSL which should be sufficient for most users.
Connect to your server via SSH and change to the base directory where your AzuraCast installation is located. If you followed the recommended installation instructions (or used a prebuilt image) you can run:
cd /var/azuracast
While you're making these configuration changes, your Docker containers should be turned off. Turn off your existing Docker containers by running:
docker-compose down
This will disconnect your listeners and stop your station from broadcasting. You will not lose any data or statistics during the upgrade.
The first step is to prevent AzuraCast's own web container from trying to listen on ports 80 and 443, as a proxy will now be doing that job instead.
There is a file in the AzuraCast installation directory named .env which has two values set by default:
AZURACAST_HTTP_PORT=80
AZURACAST_HTTPS_PORT=443
Edit the .env file in your editor of choice to change those values to an unused public-facing port. A good option would be the examples below:
AZURACAST_HTTP_PORT=10080
AZURACAST_HTTPS_PORT=10443
Save your changes and return to the shell.
Turn the Docker AzuraCast containers back on to resume broadcasting with the new setup:
docker-compose up -d
Create a new directory for the Nginx Proxy Manager and enter it via the following commands:
mkdir /var/proxy_manager
cd /var/proxy_manager
Then create a file with the name docker-compose.yml in this directory (for example with nano) like this:
nano docker-compose.yml
Now follow the Quick Setup for the Nginx Proxy Manager starting with step 2.
When you have successfully setup the Nginx Proxy Manager and have access to the GUI you can start creating a proxy for AzuraCast via the Proxy Hosts page.
Click on the Create Proxy Host button, enter a domain that points to the server in the Domain Names field.
For the Forward Hostname / IP enter either the domain name or IP address of the server and in the Forward Port enter the port that you previously set in the AZURACAST_HTTP_PORT environment variable.
Enable the Websockets Support option.
Switch to the SSL tab and select Request a new SSL Certificate in the SSL Certificate dropdown.
Enable the Force SSL as well as the HTTP/2 Support options, enter your e-mail address, aggree to the Let's Encrypt Terms of Service and click on the Save button.
In versions before 0.15.0 AzuraCast included it's own NGINX based reverse proxy that we provided to enable users to run their own containers on the same server and expose them through this proxy on port 80 / 443 making it possible to use the Let's Encrypt SSL integration of AzuraCast for those too.
We have removed this built-in multisite configuration in favor of a simpler default installation with fewer containers starting with 0.15.0 though. If you want to re-enable this feature for your AzuraCast installation follow the steps below.
Connect to your server via SSH and change to the base directory where your AzuraCast installation is located. If you followed the recommended installation instructions (or used a prebuilt image) you can run:
cd /var/azuracast
While you're making these configuration changes, your Docker containers should be turned off. Turn off your existing Docker containers by running:
docker-compose down
This will disconnect your listeners and stop your station from broadcasting. You will not lose any data or statistics during the upgrade.
The first step is to prevent AzuraCast's own web container from trying to listen on ports 80 and 443, as a proxy will now be doing that job instead.
There is a file in the AzuraCast installation directory named .env which has two values set by default:
AZURACAST_HTTP_PORT=80
AZURACAST_HTTPS_PORT=443
Edit the .env file in your editor of choice to change those values to an unused public-facing port. A good option would be the examples below:
AZURACAST_HTTP_PORT=10080
AZURACAST_HTTPS_PORT=10443
Save your changes and return to the shell.
We have set up a custom override file that configures both the nginx proxy and its own automated LetsEncrypt support (which is slightly different from our own).
You can download our custom override file by running the command below:
cp docker-compose.override.yml docker-compose.override.bak.yml
curl -fsSL https://raw.githubusercontent.com/AzuraCast/AzuraCast/master/docker-compose.multisite.yml > docker-compose.override.yml
Note that if you've already set up an override file with other modifications, you should make sure to apply the same changes that are now located in docker-compose.override.bak.yml to the newly downloaded docker-compose.override.yml file. Also, if you are using "Rolling-Release", you may need to remove "nginx_proxy" and "nginx_proxy_letsencrypt" service from docker-compose.override.yml to avoid errors during next steps.
You can enable LetsEncrypt on the multisite setup the same way as normal LetsEncrypt setup:
./docker.sh letsencrypt-create
If these values are configured and the domain name you specify resolves to your server, LetsEncrypt will automatically set up your SSL certificates and keep them renewed behind the scenes.
Turn the Docker AzuraCast containers back on to resume broadcasting with the new setup:
docker-compose up -d
Once you've set up the nginx proxy container, any other Docker container that is spun up on the server and has the VIRTUAL_HOST environment variable set will be served by the same proxy service.
For more information, you can visit the nginx-proxy repository documentation.
A common scenario our users encounter is wanting to host their station's homepage on the same server as their AzuraCast instance. This example will walk you through one way of accomplishing this using the official Wordpress Docker image.
You should begin by creating a new directory that's separate from the main AzuraCast directory. In our example, we're using /var/wordpress for ease of explanation.
mkdir -p /var/wordpress
cd /var/wordpress
docker-compose.yml FileInside the new directory, create a new file named docker-compose.yml based on the format below. Note the areas highlighted with comments, which indicate things you should change:
services:
wordpress:
image: wordpress:latest
depends_on:
- db
networks:
- azuracast_frontend
- backend
restart: always
ports:
# Set any desired port for your wp service
- "8081:80"
environment:
# Change this to the domain your Wordpress site should be served on.
VIRTUAL_HOST: wordpress.example.com
# If you want to use LetsEncrypt on this domain, uncomment these and update them.
# LETSENCRYPT_HOST: wordpress.example.com
# LETSENCRYPT_EMAIL: [email protected]
WORDPRESS_DB_HOST: db:3306
# If you customize these values, make sure to customize them below also.
WORDPRESS_DB_USER: wordpress_user
WORDPRESS_DB_PASSWORD: wordpress_pass
WORDPRESS_DB_NAME: wordpress_db
db:
image: mysql:8.0
volumes:
- db_data:/var/lib/mysql
networks:
- backend
restart: always
environment:
# If you customize these values, make sure to customize them above also.
MYSQL_ROOT_PASSWORD: somewordpress
MYSQL_DATABASE: wordpress_db
MYSQL_USER: wordpress_user
MYSQL_PASSWORD: wordpress_pass
networks:
azuracast_frontend:
external: true
backend:
driver: bridge
volumes:
db_data: {}
(Note, you might also need to change azuracast_frontend network to azuracast_default in newer Azuracast versions)
Once created and saved, you can spin up the new service by running docker-compose up -d in the same directory, and then in Nginx Proxy Manager map the example port 8081 to your sub/domain.