Thanks for the tip, but it does not like enhance --no-redirect.
Redirect is available, according to --help, but not no-redirect.
#certbot enhance --no-redirect
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Please specify one or more enhancement types to configure. To list the available enhancement types, run:
certbot --help enhance
No enhancements requested, exiting.
I thought, yes! Of course I can do that! I know that...
But because it being an Icecast server, and not a "regular" webserver, I cannot find it, so I cannot edit it.
And a search query only finds so much before eventually timing out...
Certbot cannot add a HTTP to HTTPS redirect on IceCast servers, so I have absolutely no clue on where that redirect might have came from.
Even better: Certbot can't even install the certificate on an IceCast server at all! So please could you explain to use a little bit better what the actual setup is? Just Icecast? Or also a nginx or Apache webserver?
It can. It did. With certbot certonly, I just now remembered while checking the history.
During running certbot I do remember having to tell it where the folder with html/php files for the outside world is located, I think.
And then I got the question (not verbatim) "Would you like to:"
The installation was months ago, and only now I realised I need to remove the forced redirect. I'm browsing through history, but that's a bit of a mess, as I was experimenting on how to get it to work, so not all commands in there would have actually done something.
At this point I'm not even sure if I ran sudo certbot certonly --webroot or sudo certbot certonly --standalone (which I both found in history).
So that doesn't really make it any clearer
But at one point it did give me the question:
Would you like to:
do not redirect all
Where I chose 1, and now wish I didn't.
I do really appreciate everyone's help here though! Many thanks!