# Applying SSL to all sites on a Debian Server

**URL:** <https://community.letsencrypt.org/t/applying-ssl-to-all-sites-on-a-debian-server/177926>\
**Category:** Help\
**Created:** [May 17, 2022, 6:53pm UTC](https://community.letsencrypt.org/t/applying-ssl-to-all-sites-on-a-debian-server/177926 "2022-05-17T18:53:22Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![NSpecter](https://avatars.discourse-cdn.com/v4/letter/n/df705f/32.png) [@NSpecter](https://community.letsencrypt.org/u/NSpecter)\
**Post date:** [May 17, 2022, 6:53pm UTC](https://community.letsencrypt.org/t/applying-ssl-to-all-sites-on-a-debian-server/177926/1 "2022-05-17T18:53:22Z")

</div>

Hey All! I am sure this may have been brought up and answered somewhere on the net, but I can't seem to word my question in such a way that yields good Google results. I am running a personal Web server that hosts a turnkeylinux Debian server with Wordpress (using standard ports 80 and 443). I am also running an AzuraCast Radio server instance in docker (port 81 and 444). I tried to create a letsencrypt cert and apply it to the server. This worked for accessing the wordpress site via https but broke the ability to play the radio station from the site as it was still using http. I had to disable the cert to regain access. My question is: how can I apply SSL for everything that runs on my server and not just the Wordpress site on port 80 and 443? Any assistance is appreciated and please forgive any ignorance from my side in advance. I have been IT for 15 years but am fairly new to the web hosting side of things.

My domain is: [classicalone.org](http://classicalone.org)

My web server is (include version): Apache2,Docker

The operating system my web server runs on is (include version): Debian

My hosting provider, if applicable, is: Self Hosted

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [May 17, 2022, 8:36pm UTC](https://community.letsencrypt.org/t/applying-ssl-to-all-sites-on-a-debian-server/177926/2 "2022-05-17T20:36:58Z")

</div>

Welcome @NSpecter

Radio streaming services are sometimes tricky, I don't mean to dismiss you question but you may have better luck at an AzuraCast forum. I believe they have their own github for example.

I saw on their website their docs say that for SSL it requires having its own domain and using only ports 80 and 443. It may be possible to proxy back to the Azura using Apache. That is easily done with "normal" web services but I am not sure if that works with a streaming service like Azura. You should review this post of theirs if you have not yet seen it:

> **[SSL & Let's Encrypt](https://docs.azuracast.com/en/administration/ssl-and-lets-encrypt)**
>
> Securing your AzuraCast installation with SSL / HTTPS

You might also try searching this forum for Azura. It comes up only rarely but perhaps some will help

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [May 17, 2022, 9:08pm UTC](https://community.letsencrypt.org/t/applying-ssl-to-all-sites-on-a-debian-server/177926/3 "2022-05-17T21:08:53Z")

</div>

> [@NSpecter](#):
>
> Wordpress (using standard ports 80 and 443

> [@NSpecter](#):
>
> AzuraCast Radio server instance in docker (port 81 and 444)

If you intend on having the docker container for AzuraCart Radio server system maintain it's own ACME client, **that is going to be a problem** ; As it would have to be reached via the external port 80 [for HTTP authentication].

If you can "share" or somehow "redistribute" the cert to the docker container, you could manage the certs from the main system.

That said, that is only the first part: Obtaining a cert with the name you require.  
The second part: Using a cert within your specific program (AzuraCast Radio) is something that we would have little knowledge of here.

---

<div class="post-metadata">

**Author:** ![NSpecter](https://avatars.discourse-cdn.com/v4/letter/n/df705f/32.png) [@NSpecter](https://community.letsencrypt.org/u/NSpecter)\
**Post date:** [May 18, 2022, 12:59am UTC](https://community.letsencrypt.org/t/applying-ssl-to-all-sites-on-a-debian-server/177926/4 "2022-05-18T00:59:22Z")

</div>

Thanks Mike! I have definitely checked out that doc and have followed it successfully in the past when only running AzuraCast and no other websites/apps. I will look into the proxy piece to see if I can find a potential solution there. Cheers!

---

<div class="post-metadata">

**Author:** ![NSpecter](https://avatars.discourse-cdn.com/v4/letter/n/df705f/32.png) [@NSpecter](https://community.letsencrypt.org/u/NSpecter)\
**Post date:** [May 18, 2022, 1:24am UTC](https://community.letsencrypt.org/t/applying-ssl-to-all-sites-on-a-debian-server/177926/5 "2022-05-18T01:24:03Z")

</div>

Thanks @rg305 I am honestly thinking it might be far easier to migrate the WP site to a webhost and then just host the radio station internally. I would then be able to apply the SSL cert on the web host side to the main domain [classicalone.org](http://classicalone.org). I could then point a subdomain (i.e. [radio.classicalone.org](http://radio.classicalone.org)) to the docker instance and apply a Let'sEncrypt cert to the self hosted server using the guide referenced by Mike above. Is that a feasible solution? Thanks!

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [May 18, 2022, 2:34am UTC](https://community.letsencrypt.org/t/applying-ssl-to-all-sites-on-a-debian-server/177926/6 "2022-05-18T02:34:33Z")

</div>

I think you can do as well by leaving the WP site as by moving it to a dedicated webhosting service.  
That really only reduces a small piece of the puzzle.

Getting a cert shouldn't be too difficult.  
Using the cert is the bigger trick.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [June 17, 2022, 2:34am UTC](https://community.letsencrypt.org/t/applying-ssl-to-all-sites-on-a-debian-server/177926/7 "2022-06-17T02:34:41Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
