| 14 Jul 2025 |
 @n4ch723hr3r:nope.chat | icecast doesnt support tls, does it? | 14:18:11 |
| @n4ch723hr3r:nope.chat | <listen-socket>
<port>8000</port>
<bind-address>127.0.0.1</bind-address>
</listen-socket>
<listen-socket>
<port>8443</port>
<tls>1</tls>
</listen-socket>
<listen-socket>
<port>8004</port>
<shoutcast-mount>/live.mp3</shoutcast-mount>
</listen-socket>
| 14:20:14 |
| @n4ch723hr3r:nope.chat | so it seems you can split some things apart | 14:20:24 |
 @saiko:knifepoint.net | In reply to @matthewcroughan:defenestrate.it
Only if you have a spare IP to dedicate it to why do you need a spare IP for icecast to work? I used to run it fine without one | 14:24:35 |
| @n4ch723hr3r:nope.chat | the main problem seems to be the inability to put it behind a reverse proxy | 14:25:42 |
 matthewcroughan - nix.zone | Because the only way to run it properly is on port 80/443, if you want a letsencrypt SSL cert, because you can't proxy it | 14:27:24 |
| matthewcroughan - nix.zone | and you have to gen that cert by hand, and it's not automatable and it's awkward | 14:27:45 |
| @saiko:knifepoint.net | In reply to @n4ch723hr3r:nope.chat
the main problem seems to be the inability to put it behind a reverse proxy oh. well, that’s mostly a http specific thing | 14:27:54 |
