@neralex - the relay* values are whatever the defaults are. it's not an issue i care very much about because i can work around it. it's just not working the way it's supposed to.

my relay dnas relays 5 remote dnas servers. i don't need all 5 all the time and i have automation that bring them up and down based on remote demand, ie at a certain number of users on the remote, i'll bring the relay for that remote dnas online... at the same time my websites will change urls to send listeners to the relay... now that's cool.. what does not work (but always worked with dnas v2.5.1 and earlier) is the stop relay command...

i work around it with a v2.5.1 or v2.4.7... otherwise the v2.5.5 is perfect.

commenting out streamrelayurl_n=, pushing the changed config file via ftp to the server, and doing a soft config reload will do the trick, but too much trouble when v2.5.1 works right. then if i need to start the relay... the steps have to be repeated.

We are waiting already from many years to make this servers to work with SSL certificate (https), why this is so ignored? IceCast support certificate from long time ago. Do you have any plan to enable / add this option and to be compatible with Let's Encrypt?

We are waiting already from many years to make this servers to work with SSL certificate (https), why this is so ignored? IceCast support certificate from long time ago. Do you have any plan to enable / add this option and to be compatible with Let's Encrypt?

Thanks

What's preventing you from setting up an HTTPS reverse proxy to the DNAS?