PDA

View Full Version : [yp_add] yp.shoutcast.com gave error (HTTP/1.1 400 Bad Request)


eth1k
15th September 2002, 18:17
I'm running a shoutcast server behind NO firewall, under Windows98se. The server worked 2 days ago. I downloaded the newest version of the DNAS server and reinstalled winamp 2.80. I set up everything correctly - port 8000 and 8001, port 80, and everything else I left configured how it was when it was working before. I have have no idea why I am getting this error in the server log: [yp_add] yp.shoutcast.com gave error (HTTP/1.1 400 Bad Request)
It is not adding me to the shoutcast server list on the main website and on my personal shoutcast website it does not show the song titles - even though I have that set as "auto update titles/songs". Please Help. Thanks

Tom
16th September 2002, 04:11
What are your entries for ICQ, IRC and AIM in the Yellowpages section of the DSP?

Tom

eth1k
16th September 2002, 05:14
AIM=SFLuke03 , IRC= #eth1K - irc.gamesnet.net ICQ=no entry

Sawg
16th September 2002, 19:19
No spaces. Have to get rid of them in the IRC field.

eth1k
16th September 2002, 20:40
I fixed the IRC thing - no spaces in any box now. I still get the same error, after restarting the winamp, shoutcast, and shoutcast server. The server works fine - its just not adding me to the main site and it gives that error every second in the log. Please Help.

TheAttackktycal
3rd November 2003, 04:50
i got the same problem

DJHotIce
3rd November 2003, 12:04
:igor:

Check out the results from a SHOUTcast forum search (http://forums.winamp.com/search.php) on '400 bad request'.

Look for the post by eth1k titled:
[yp_add] yp.shoutcast.com gave error (HTTP/1.1 400 Bad Request)

FesterHead
3rd November 2003, 14:42
Warning!

Infinite loop detected.

Shout B.R.A.T.T
3rd November 2003, 16:10
If you have try everything (like i did) so reinstall winamp and shoutcast. It worked for me.

Omnious
9th November 2003, 19:56
Here's my Try at this:

I 've just Installed the Shoutcast Server, and I went through everything they said.

Try these:
-Change the IP Port Connection from 8000 to 6777 (Or any port you may want to go under, 8000's fine, but sometimes other programs may be using that port sometimes i.e. Mirc or something. I chose 6777 because I usually see other servers connect using this port, as well as sites.)

-Getting rid of Spaces in the Yellowpages. This is what was preventing me from connecting, because I had a space in my AIM Name. Be sure to check all of the boxes before finishing the Yellowpages.It should work then.

These were more in-depth in helping you. I hope it does. (BTW, I'm on a Cable Modem, so it should work.)

isaiah
15th November 2003, 01:31
still nothing for me

FesterHead
15th November 2003, 01:55
Please post a DNAS startup log snippet.

MegaRock
16th December 2003, 16:32
My solution to this problem was quite simple.

1. Shut down DNAS
2. Delete ALL files (except anything in CONTENT). Since I had nothing in there I deleted the whole directory.
3. Download DNAS
4. Reinstall DNAS
5. Changed port.

Everything came up perfectly, connected to YP fine and there have been no problems or errors.

Only thing I can think of is a few days ago I was messing with setting up a second DNAS on the same server (seperate port of course) for private testing, however the YP errors didn't start until yesterday.

Is is possible a config file or running the second server caused this problem (my thoughts are no, but the timing is odd).

Anyway it seemed to fix my problem but to be honest I still have no idea why this happened in the first place. If you'll excuse me I gotta go back to my book "Windows For Complete Freaking Idiots". :)

FesterHead
16th December 2003, 17:07
FYI: The yp has been experiencing some problems on and off for the past couple days.
That may explain the yp errors.

***************

Did you read the FAQ for setting up multiple DNASs?

MegaRock
16th December 2003, 19:55
I noticed the same thing....the connection was dying out on AOL's transit network - this could have caused the problem but since replacing the files the error hasn't happened (so far) since then and yp is still having connection issues.

FesterHead
16th December 2003, 20:21
Sometimes the yp goes nuts.
Probably compounded by the release of Winamp5, too.

Here's my personal fix:
Apply coffee algorithm (http://forums.winamp.com/showthread.php?postid=1107138#post1107138)