Streaming Service with Icecast - Revision history

320x200: /* TLS/SSL Support */

2024-07-17T22:03:44Z

TLS/SSL Support

← Older revision		Revision as of 22:03, 17 July 2024
Line 114:		Line 114:
	=== TLS/SSL Support ===		=== TLS/SSL Support ===
	It's possible to use existing X.509 certificates to provide HTTPS access to both listeners and sources. For this to work the server and intermediate certificates with the private key.		It's possible to use existing X.509 certificates to provide HTTPS access to both listeners and sources. For this to work the server and intermediate certificates with the private key.
	* merge <code>fullchain.pem</code> with <code>privkey.pem</code> ~~(example with Let's Encrypt certs)~~		* merge <code>fullchain.pem</code> with <code>privkey.pem</code>
			# official acme client
	cat /etc/letsencrypt/live/domain.tld/fullchain.pem > /usr/local/share/icecast/icecast.pem		cat /etc/letsencrypt/live/domain.tld/fullchain.pem > /usr/local/share/icecast/icecast.pem
	cat /etc/letsencrypt/live/domain.tld/privkey.pem >> /usr/local/share/icecast/icecast.pem		cat /etc/letsencrypt/live/domain.tld/privkey.pem >> /usr/local/share/icecast/icecast.pem
			# acme.sh
			cat /root/.acme.sh/domain.tld/fullchain.cer > /usr/local/share/icecast/icecast.pem
			cat /root/.acme.sh/domain.tld/domain.tld.key >> /usr/local/share/icecast/icecast.pem
	* Adjust <code>icecast.xml</code> config file with <code><ssl-certificate></code> and <code><ssl-allowed-ciphers></code>:		* Adjust <code>icecast.xml</code> config file with <code><ssl-certificate></code> and <code><ssl-allowed-ciphers></code>:
	<pre>		<pre>

2021-03-16T00:13:41Z

TLS/SSL Support

← Older revision		Revision as of 00:13, 16 March 2021
Line 114:		Line 114:
	=== TLS/SSL Support ===		=== TLS/SSL Support ===
	It's possible to use existing X.509 certificates to provide HTTPS access to both listeners and sources. For this to work the server and intermediate certificates with the private key.		It's possible to use existing X.509 certificates to provide HTTPS access to both listeners and sources. For this to work the server and intermediate certificates with the private key.
	* merge <code>fullchain.pem<code> with <code>privkey.pem</code> (example with Let's Encrypt certs)		* merge <code>fullchain.pem</code> with <code>privkey.pem</code> (example with Let's Encrypt certs)
	cat /etc/letsencrypt/live/domain.tld/fullchain.pem > /usr/local/share/icecast/icecast.pem		cat /etc/letsencrypt/live/domain.tld/fullchain.pem > /usr/local/share/icecast/icecast.pem
	cat /etc/letsencrypt/live/domain.tld/privkey.pem >> /usr/local/share/icecast/icecast.pem		cat /etc/letsencrypt/live/domain.tld/privkey.pem >> /usr/local/share/icecast/icecast.pem

2019-12-17T14:49:42Z

NGINX Reverse Proxy

← Older revision		Revision as of 14:49, 17 December 2019
Line 110:		Line 110:

	=== NGINX Reverse Proxy ===		=== NGINX Reverse Proxy ===
			At time of writing, reverse proxying for icecast is not really worth it. Will explain a bit more eventually.

	=== TLS/SSL Support ===		=== TLS/SSL Support ===

2019-12-17T14:31:03Z

Relaying an External Stream

← Older revision		Revision as of 14:31, 17 December 2019
Line 141:		Line 141:
	<workers>4</workers>		<workers>4</workers>

	=== Relaying an External Stream ===		=== Relaying an External Stream (the lazy way) ===
			This can be done simply by just pointing to the stream you want to relay. Careful though, you need to point to the remote server IP, not the domain. If you add <code><on-demand></code>, the stream will be relayed only if it is requested.
			<pre>
			<relay>
			<server>10.10.10.10</server>
			<port>1234</port>
			<mount>/blabla.mp3</mount>
			<local-mount>/blabla.mp3</local-mount>
			<on-demand>1</on-demand>
			<relay-shoutcast-metadata>0</relay-shoutcast-metadata>
			</relay>
			</pre>

	[[Category: Streaming]]		[[Category: Streaming]]

2019-12-17T13:46:17Z

Moar Cores!

← Older revision		Revision as of 13:46, 17 December 2019
Line 138:		Line 138:

	=== Moar Cores! ===		=== Moar Cores! ===
			In <code>icecast-kh</code> it's possible to choose how many threads to use for processing clients. This should be based on the number of CPUs or cores. This can be adjusted in <code>icecast.xml</code> with the following line inside <code><limits></code>:
			<workers>4</workers>

	=== Relaying an External Stream ===		=== Relaying an External Stream ===

2019-12-17T13:35:11Z

MOAR Configuration

← Older revision		Revision as of 13:35, 17 December 2019
Line 129:		Line 129:
	</pre>		</pre>

	'''Note:''' If you have used the config file of this documentation, then icecast will be reachable both on http://stream.domain.tld:8000 and https://stream.domain.tld:port. You may want to keep it like that as some clients (both for listening and emitting) do not support TLS/SSL. If you want enforce TLS/SSL, you can adjust your config file so that:		'''Note:''' If you have used the config file of this documentation, then icecast will be reachable both on <code>http://stream.domain.tld:8000</code> and <code>https://stream.domain.tld:port</code>. You may want to keep it like that as some clients (both for listening and emitting) do not support TLS/SSL. If you want enforce TLS/SSL, you can adjust your config file so that:
	<pre>		<pre>
	<listen-socket>		<listen-socket>
Line 136:		Line 136:
	</listen-socket>		</listen-socket>
	</pre>		</pre>

			=== Moar Cores! ===


	=== Relaying an External Stream ===		=== Relaying an External Stream ===

2019-12-17T13:33:49Z

Basic Configuration

← Older revision		Revision as of 13:33, 17 December 2019
Line 51:		Line 51:
	</authentication>		</authentication>

	<hostname>~~echo~~.~~lurk~~.~~org~~</hostname>		<hostname>stream.domain.tld</hostname>

	<listen-socket>		<listen-socket>

2019-12-17T13:32:58Z

← Older revision		Revision as of 13:32, 17 December 2019
Line 128:		Line 128:
	</paths>		</paths>
	</pre>		</pre>

			'''Note:''' If you have used the config file of this documentation, then icecast will be reachable both on http://stream.domain.tld:8000 and https://stream.domain.tld:port. You may want to keep it like that as some clients (both for listening and emitting) do not support TLS/SSL. If you want enforce TLS/SSL, you can adjust your config file so that:
			<pre>
			<listen-socket>
			<port>999</port>
			<ssl>1</ssl>
			</listen-socket>
			</pre>

	=== Relaying an External Stream ===		=== Relaying an External Stream ===


	[[Category: Streaming]]		[[Category: Streaming]]

2019-12-17T13:29:01Z

MOAR Configuration

← Older revision		Revision as of 13:29, 17 December 2019
Line 116:		Line 116:
	cat /etc/letsencrypt/live/domain.tld/fullchain.pem > /usr/local/share/icecast/icecast.pem		cat /etc/letsencrypt/live/domain.tld/fullchain.pem > /usr/local/share/icecast/icecast.pem
	cat /etc/letsencrypt/live/domain.tld/privkey.pem >> /usr/local/share/icecast/icecast.pem		cat /etc/letsencrypt/live/domain.tld/privkey.pem >> /usr/local/share/icecast/icecast.pem
	* Adjust <code>icecast.xml<code> config file with <code><ssl-certificate></code> and <code><ssl-allowed-ciphers></code>:		* Adjust <code>icecast.xml</code> config file with <code><ssl-certificate></code> and <code><ssl-allowed-ciphers></code>:
	<pre>		<pre>
	<paths>		<paths>

2019-12-17T13:28:39Z

MOAR Configuration

@@ Line 111: / Line 111: @@
 === NGINX Reverse Proxy ===
 === Relaying an External Stream ===
 [[Category: Streaming]]