connection rejected. Bad icy header string [icy-name:]

[Segaja]

Hi,

I have set up a SHOUTcast 2 server and a user wants to stream into it.

He can't connect and the log says:

connection rejected. Bad icy header string [icy-name:]


I have set the titleformat value in the config which, according to the docs, should be used as icy-name if the client doesn't provide one.

How can I fix this problem?

Best regards
Segaja

[DrO]

the source needs to provide a title as 'titleformat' isn't even considered at stage in the connection. i suppose if there is a value for 'titleformat' then 'icy-name' could be allowed through as an empty key-pair. will make a note to possibly get this changed but you'll be better getting them to ensure there is a title speciifed, even if it's just 'a' or something inane.

-daz

[Segaja]

What is the point of the titleformat setting if it is not taken as default value?

The person who is streaming into the server is not using the DSP 2 but the program butt.
He tells me he can't find a setting in there to set the icy-name value.

[DrO]

it had to be butt that was being used. that thing is what it's name is.

the information can be entered via the 'stream infos' section on the settings dialog (though the layout / naming is easy to miss). however, the v2 DNAS would still reject the stream if just the description in the butt settings is set, since it'll fail on genre and url fields which are required.


all i know is that titleformat was something in the v1 DNAS and so was implemented into the v2 DNAS (before my time of working on the tools) so i don't really know without trying if this is the same behaviour or not as the v1 DNAS exhibits. i do know that the v2 DNAS is generally more strict in it's handling of the SHOUTcast protocols which catches out some incomplete / poorly implemented sources.

i have however logged it as something to work on so that the source connection will be allowed through if icy-name is empty and titleformat is not empty as well as icy-url is empty and urlformat is not empty for the next v2 DNAS release (no eta). i can only apologise for the inconvenience but as few people wanted to use the v2 DNAS when it was in beta, these things do unfortunately slip through but will be resolved.

-daz

[Segaja]

We will try this with the 'stream infos' dialog in butt next week.

I'm not the fan of using betas in a "production system" either, but we had serious problems with DNAS 1.9.8 on our 64bit ubuntu server which are not present with the 64bit version of DNAS 2 so i have no choice.

Thanks for taking this up. So the conclusion is that for now titleformat and urlformat are nothing but relict settings from DNAS v1.

[DrO]

titleformat and urlformat are used on v1 and v2 sources, but only once the source has been allowed to connect which obviously if there's nothing to replace will get it blocked. i don't disagree that it isn't counter intuitive and hence it will be changed.

i've a feeling it was assumed that those values would always have something specified for them (which is a fair assumption) but then i guess butt was never considered.

either way it'll be resolved, just keep an eye on http://forums.winamp.com/showthread.php?t=324877 which is updated when there is a new release (is done a bit quicker than the main site downloads).

-daz

[Segaja]

Ok thanks. I appreciate that you take it up.

Btw. what about other clients like Edcast?

[jaromanda]

Personally, I wouldn't use edcast on DNAS v2, edcast is rubbish

[DrO]

Segaja: what OS version of the v2 DNAS are you running on? need to know so i can provide you the required test build to try out.

-daz

[swissdancenation]

Same problem here! works with the transcoder but not with direct connection to the DNAS.
Windows server sided, OSX on client side...

[DrO]

swissdancenation: will pm you a win32 build of the DNAS shortly.
[edit]
sent the pm now.

-daz

[Segaja]

Segaja: what OS version of the v2 DNAS are you running on? need to know so i can provide you the required test build to try out.

-daz

Linux 64 bit

[DrO]

Segaja: pm sent with a test build, apologies in the delay (really had thought i'd already sent it).

swissdancenation: please can you check my reply to your last pm please - need more information as you seem to have had issues with the prior test build sent (is an older version of what i've just sent Segaja).

-daz

[Segaja]

Hi DrO,

sorry for the delay, but I didn't had much time lately.

We tested the version you send me and now a butt user can stream onto the server, but only if he has no description set. If the butt source sets a description (in our case "bla") he is rejected:

connection rejected. Bad icy header string [bla]


Best regards
Segaja

[DrO]

rightio, will test that out. though might be easier to just ban connections coming from butt (but that'd be evil on my part, heh).

-daz