It is possible to operate audio and video services across multiple domain names with SSL support.
The below configuration steps will allow services to be accessed directly on either domain1.com or domain2.net, for example a Shoutcast or Icecast service could be accessed on both domain1.com:8000/stream or domain2.net:8000/stream.
Please note that it is not possible to access the MediaCP panel itself from the additional domains without further manual configuration.
Firstly, ensure AutoSSL is already installed for domain1.com then run the following in SSH ensuring to first replace domain1.com with the MediaCP domain and domain2.net with the second domain.
/usr/local/mediacp/certbot/certbot certonly \
--register-unsafely-without-email -d domain1.com -d domain2.net \
--agree-tos --standalone \
--preferred-challenges http-01 \
--config-dir /usr/local/mediacp/letsencrypt \
--non-interactive \
--keep-until-expiring \
--agree-tos \
--pre-hook=/usr/local/mediacp/certbot/pre.sh \
--post-hook=/usr/local/mediacp/certbot/post.sh \
--deploy-hook /usr/local/mediacp/certbot/deploy_wrapper.sh \
--expand;
Up to 100 additional domain names can be configured with AutoSSL (powered by LetsEncrypt) by adding additional "-d domainname.tld" to the command
If you are using the port 80/443 proxy feature, the new domains will not work on port 80/443 withouth manually setting up symbolic links for the proxy to use. Once you have the intial domain setup above create the symbolic links for the additional domains by following these steps:
1. CD into the certificate directory:
cd /usr/local/mediacp/content/certs/
2. Create symbolic links for the key and certificate:
ln -s /usr/local/mediacp/letsencrypt/live/domain1.com/fullchain.pem ./domain2.com.crt
ln -s /usr/local/mediacp/letsencrypt/live/domain1.com/privkey.pem ./domain2.com.key
