403 forbidden

[plow]

[yp_add] yp.shoutcast.com gave error (HTTP/1.1 403 Forbidden)

keep getting this message...

searched the forums, though the problem wasn't exactly addressed.

not behind a firewall, was streaming fine until an hour ago. nothing changed.

one of the forum kings had previously suggested one might have to wait it out that it was a yp prob.

please help.

[rkcpi]

Yes, I have exactly the same problem from some hours.
Never I had, I'm brodcasting from many time (3 years), nothing is changed in my setting.
I'm sending 3 streams contemporaneously, but only 1 server is receiving this error. The other 2 are ok.
I tried to restart everything, also my machine, several times, but nothing to do.










www.radiokrishna.com

[josephjrr]

I just started getting this error an hour ago. I've been doing this for 2 weeks straight and NEVER before seen it. I tried everything suggested and am still getting it. Is this a system problem? Whats going on?

[jslmg]

I've got it too! Really weird.

The first thing I did was to go to another computer (not the one I'm broadcasting on) and see if my signal was coming through OK, complete with song titles on the Winamp player.

Yes, I'm still broadcasting, with the same 12-14 listeners (puny, huh?) that I had when the problem first occurred. But take a look at the Shoutcast directory! There are only about 900 stations ("servers") listed when there are usually several thousand.

This is a Shoutcast problem, everyone!

Now, where's my sack of tomatoes to throw at 'em ??!!!

I thought about restarting the server, but after reading your comment, I decided it probably wouldn't work anyway.

What gives at Shoutcast, anyway?

Patiently waiting...

John Grimmett:mad:

[roby0215]

I have been broadcasting for 18 months now and started getting the message at about 3 AM toronto time

[omega1]

Hi, I have it two, I have two streams, and it only affects one, my streams are on port 8000 and port 7800...

Does anyone know what could be wrong??

The streams do work OK though, so the problem is only really the annoying messages!

Regards,



Gavin Watson,

[Jay]

it seems as though it's related to certain ip's most likely this is a problem with the directory.

[garethpullen]

yes im having the exact same problem today...
anyone know how to resolve it??

my stream will NOT work when im getting these errors. please help someone!

[Jay]

you cannot fix it, this is something wrong at the directory site.

[DJ_Lee_uk]

Yeah i seem to be gettin this error aswell. ok yesterday and for the past year or so , woke this morning to find the error. glad it aint just me . was getting worried till i came here.

[garethpullen]

at fisrt my broadcast was NOT working . but i have unticked "Make my server public" and it works fine, with no error messages.

hope this helps guys if u want to try that!

[moontrains]

same problem here for:
52media Bash and Pop Radio
Deliciound.net
UnderdogRadio.net
52media Techno
CrackHouseMusic.com
UndergroundLou.com

we use Stream Guys (kiriki rulez). like jay said, its more than likely a shoutcast directory problem. i've noticed the AOLuser network has been sluggish too.

[Psikick]

Same here.......I am getting the error...

If you look @ the Shoutcast directory listing, many are not listed perhaps because they are all getting this error message too...

But it doesn't look as if its interrupting the broadcast...

[Jay]

no this will not affect your ability to broadcast this is strictly a listing problem, and related to the shoutcast.com webserver blocking requests from certain IPs.

[Boomtastic]

*whew!*

Good to know that I'm not the only one getting the 403 error! I thought that the RIAA was up to no good again ... :( Thanks for the update guys!!

Eric, from Boomtastic Racing Radio (http://boomtastic.tzo.com:8000/listen.pls)

[creepradio]

Getting the same problem at Creep Radio. Streeming fine and able to pull the streaming via URL but not listed in directory. The boyz at Shoutcast must have a server down. If you want to experience Creep Radio tune to this...http://12.237.79.221:8000Creep Radio (http://12.237.79.221:8000)

[NashuNatta]

The problem is somone probobly banned an IP and they used a wrong ip mask to ban, so it is banning everyone who has like the # 2 in their ip or anyone who connects with attbi.com or something like that. IRC does it all the time.

[Tom]

I sent an email to Tom Pepper regarding this issue so hopefully it will be resolved soon.

Tom

[omega1]

Hi,

Cant see how it can be related to IP's, more like ports, I have two streams on the same IP, but different ports (7800 & 8000) the one on 7800 gives error, but the one on 8000 works fine... Does this help?

[Jay]

hmm maybe it's a combination cause no matter what I use on my shoutcast for port here at my home connection it successfully lists.

[josephjrr]

Its working for me now. YES!!!

[yp_add] yp.shoutcast.com added me successfully

[Kambriel]

It seems to be giving the 403 messages again this morning and the listings are pretty slim on the Shoutcast site...

[klunkung]

Whew! I'm getting the same problem here with Sure Quality Radio.

Hope this doesn't last too long. I'm gonna instant messenger a friend and see if he can tune in. If he can't I will uncheck make this server public, and try again.

[RadioDruid]

same problem here...what's up with that??

[klunkung]

I unchecked "make this server public" and am not getting any more error messages from the dnas GUI. But, now I'm not getting any updates either. I used to get "shoutcast.com touched" every minute. I haven't been able to reach anyone of my friends with high speed yet, so I have no idea if they can tune in. They should be able to tune in by using http://HOST.DOMAIN.TOPDOMAIN:8000/LISTEN.PLS Hope this works. I don't really care if i am listed publically as I have enough of a listener base as it is and they know how to access the stream and homepage. For a few minutes, I thought that Shoutcast had removed me because of sensitive content. But, I checked the terms of service and they apparently do not censor any stream at all. Well, guys, I guess we'll know more as it goes down. By the way, I work for a large regional ISP, and we suffered a denial of services attack (corrupted database) last week that had our email down for almost a week, I hope this is not what is happening here.

[Kambriel]

Disabling the "public" feature of the DNAS doesn't solve the problem per se. The Shoutcast listing is denying your connection (mine and many others too) for reasons unknown. While this stops the DNAS from shownig the 403 error, it means that you won't be listed on the Shoutcast site until the problem is fixed and the public option is enabled again.

I was hoping for an official statement from one of the talented developers whose DNAS we love so much, but they are probably knocking their brains out trying to find out what the problem is.

[MysticRadio]

Hi There,
Yes, I too have the 403 problem. It started yesterday morning, seemed to be resolved by late yesterday afternoon, and has now returned. So, are you all in the same boat, or is it more selective? I tried unchecking yp directory, but that did not help. What to do?
Is there a place that Shoutcasts posts tech news that is relevant? All of what they have up there is, well, not very timely.
Thanks for the help.
The MysticDJ

[djmiked1]

Same thing happening here for me
started like this:
<03/25/03@02:58:27> [yp_tch] yp.shoutcast.com gave error ()
<03/25/03@05:56:45> [yp_tch] error connecting to yp.shoutcast.com
then went away almost imedatly

Then starting again
<03/25/03@23:07:44> [yp_tch] error connecting to yp.shoutcast.com
<03/26/03@02:49:57> [yp_tch] yp.shoutcast.com gave error (HTTP/1.1 403 Forbidden)

and still continues.

i am running 3 servers

port 8000
port 3590
port 9000


the server running on port 9000 works great
no errors
???? thats all i got for now. an answer to this problem would be helpfull it has been way more than 24 hours now.

Thanks
Mike

http://www.djmiked.com

[MysticRadio]

Its interesting, broadcasting without any knowledge of how many people are listening. Yes the broadcast is up, the yp directory down. However, one interesting side note is that if you go to the server monitor it will show you how many listeners you have. How this is possible, you tell me. Anyway, any word from the Shoutcast techies?

[Kambriel]

The DNAS was designed to be stand-alone or "public", hence the ability to make the server private and not perform yp touches, yet it still is aware of how many users are connected to itself. The service that Shoutcast performs for free is the ability to organize listening statistics for ratings and to make it easier for listeners to find the stations they want.

[djmiked1]

are we sure that tech support has no clue what is going on.
I mean we havent gotten a reply nor has the problem even been aknolaged let alone fixed. Is there a way we can contact someone direct???

[Kambriel]

If you look up a few threads, you'll see one of the moderators of this forum stating that he sent an e-mail to Tom Pepper (the great Shoutcast God) about the problem. Tom Pepper is usually VERY good about responding to issues like these, so I'm surprised that nothing official has been said yet.

[Dagan]

Hey I got it to work. I changed the port # and now [yp_add] yp.shoutcast.com added me successfully. Happy Happy Joy Joy:D :D

[PWRGRRL]

Changing your IP or port is a temporary fix.... we did that and the next day it went 403 again. Hopefully we'll get a fix from a shoutcast tech.

Shelby

[jslmg]

I'm glad I'm not alone in scratching my head over this. I think the best thing to do is just wait. I mean, the Shoutcast folks don't seem like the type to just say "Ah, who cares?" when a problem crops up in their service. Most computer people are real perfectionists, and, like most of us, they get real anxious when things get out of control.

I'm sure their working hard this very moment to sort it all out! RIGHT?

Well, right?

Hang in there, folks! I've still got listeners, because mine are using their links in "favorites" to get the station.

[PWRGRRL]

Can we at least get a progress report from shoutcast techs?

Anything is better than being in the dark.

Shelby

[RadioDruid]

mine was up from 14:04-14:23, but it seems to be down again

[djmiked1]

looks like i am up for the moment

[PWRGRRL]

I'm also listed again..... we'll see for how long

Shelby

[alanevil]

I was pretty scared that this was caused by a hacker attempting to trace back to my computer. This happened today and a couple of days ago (I'd look back but I've got a listener on that stream). I had some really heavy traffic (well, for me since it's over my DSL the fact that all 3 hifi slots were full for many hours was really cool) then and it happened without anyone loosing their connection. It seemed to rectify itself shortly after I noticed. Today I was at work while it happened so I just saw it but this is the second time for me (I repeat myself when I'm under stress, I repeat myself when I'm under stress) which is why I started to research the problem.

I live in a giant bucket.

It's not a hacker, right? It's a problem with the directory, right?

You guys are great...

www.psychicreform.com

[alanevil]

I also noticed that for a lot of you it only happened on one stream at a time. I've got two streams: 3listenersmax 112kbps and 4listenersmax 24kbps going most of the time (especially when I'm not here which is most of the day) and both times this has happened to me the two servers have mirrored each other as far as times, etc. Not that it really matters but it might.

www.psychicreform.com

[RadioDruid]

I assumed it was "The Man" trying to shut me down because most of my programming is pro-peace, anti-fascist, which runs counter to the prevailing doctrine...but I guess not...I'm back up again....

[DJ AmPs]

all of this is just temporary glitches i'm sure will be fixed. there is no conspiracy theories or singling out of any stations...

[peppert]

ok problem is now fixed. upon adding some logic to the directory to deny rogue servers which send add/touch requests at rapid intervals (far less than the programmed rate) I managed to screw up a little chunk of the logic. I was away from a real term for a couple of days and had to issue temporary fixes, which would only resolve the issue for the next 600 touches of a server (10 hours) but managed to find the permanent solution this afternoon.

Apologies to those of you who were affected (anyone who had a server up for more than 10 hours) during the past 36 hours.

For the curious, every day if more than 600 requests are received for adds or touches, if your server has sent them at an average rate of 2 or more per minute, your host and port are marked banned for the remainder of that day. these numbers may change based on what effect the policing of the directory has.

A similar mechanism is in place on the directory itself, so those of you processing the directory every minute or 5 minutes to find out your listener counts will soon be facing a dreaded 403 Forbidden. You should be getting those statistics off of your servers via XML or other tools, not via the directory page.

Basically, the change came about because people are writing tools to parse the entire shoutcast.com directory list via HTML, and then send requests for each tunein link to get playlists. They usually republish this information on other sites. Now they can't.

If you're interested in republishing the directory inside of a product or web service, I can put you in touch with appropriate people for licensing information and costs. Otherwise, enjoy the 403.

Thanking you,
-Tom

[peppert]

i should add for those who get this error after today:

if you continue to receive this error, it is because your server is sending extraneous requests to the database and has been locked out until midnight the following day. the best rectification to this problem is to upgrade to the most recent version of the shoutcast server (DNAS) and wait until tomorrow. you should also check to make sure your station information in the dsp doesn't contain too many odd characters or other silliness, especially the aim, irc, and icq fields (no spaces in these 3 especially)

that's all,
-t

[jslmg]

Hi, Tom. Thanks for finally getting back to all of us.

If I understand you right, you have had to make some changes in the Shoutcast directory system, and it now has more restrictions, is that right?

As a shortcut, let me tell you what my DNAS has been doing the last few weeks, and then perhaps you can tell me if I'm going to be prone to more of the 403 problem:

--Under normal conditions, my DNAS "touches" yp.shoutcast.com every 1 minute and 1 second. Do I need to change this setting? If so, how do I do it?

--At our broadcast peak each day, we average about 30 listeners at one time, with, I guess, about 500 or so listener "hits" each day. Is that too many hits for one day?

--During weekdays, I keep the server running (try to, anyway) 18-19 hours a day, usually between 8 a.m. and 3 a.m. EST. During weekends, I'd like to keep the server running about 60 hours, from Friday morning through Sunday night, without stopping. Is that too long?

--The listener max is set at 50. Does this affect the problem?

Given these conditions, will I need to make adjustments to the server config to keep the 403 notice from coming up?

You mentioned that it's better not to get our listener count from the directory. Can you explain that? I thought the DNAS got its listener count whether it was listed in the Shoutcast directory or not.

I'd like to keep the station listed in the directory even if I have to give up on knowing my listener count.

Keep in mind that at this early stage in the station, we do not yet have a web page. We're just trying to run a regular, reliable 96KB stream that the public can easily get to.

Any advice or reassurance will be most appreciated.

Thank you.

John Grimmett :confused:

[peppert]

The changes to the db are designed such that any current, normally-functioning version of SHOUTcast DNAS will not have to make a single change. The changes are only designed to help alleviate database stress for servers which are pinging too fast (every 10 seconds or faster.) This is limited to old versions of the DNAS which contained a race condition in the yp thread. Anyone running version 1.8.x or newer should not see this problem ever on their server.

Even old versions will not see this error unless something is horribly wrong with the station data or metadata they are submitting.

At any rate, the real fix for anyone seeing this problem is to a) upgrade to a current version of the DNAS (server) and b) make sure their station name, genre, aim name, icq name, and irc channel contain valid data (see the forums for more details on what is valid data).

[DJ MasterP]

Originally posted by KXRM
you cannot fix it, this is something wrong at the directory site.

Im glad it isnt one of my 3 soundcards ive been working on last night :P

[djiss]

<09/09/04@18:41:22> [yp_add] yp.shoutcast.com gave extended error (Cannot see your station/computer (IP: 69.75.188.173:8000) from the Internet, disable Internet Sharing/NAT/firewall/ISP cache (Connection timed out))

the issue seems to be happening again , anyone have an answer??? help

[MavMix]

Yep, seems to be very intermitent. I'm getting it too... again.

[ClassicRox]

Don't worry, I'm getting that same message today, and nothing was changed on my end at all, and I've been running a station for nearly 2 years now.

I guess it's just another glitch that will have to sort itself out over time.

[zbowling]

I am can't get it to work correctly. Its crazy. YP is degrading in its quality.

[sev]

Same firewall message im getting even if i disable them and reboot
frustrating!!

[lidontno1]

Originally posted by peppert
The changes to the db are designed such that any current, normally-functioning version of SHOUTcast DNAS will not have to make a single change. The changes are only designed to help alleviate database stress for servers which are pinging too fast (every 10 seconds or faster.) This is limited to old versions of the DNAS which contained a race condition in the yp thread. Anyone running version 1.8.x or newer should not see this problem ever on their server.

Even old versions will not see this error unless something is horribly wrong with the station data or metadata they are submitting.

At any rate, the real fix for anyone seeing this problem is to a) upgrade to a current version of the DNAS (server) and b) make sure their station name, genre, aim name, icq name, and irc channel contain valid data (see the forums for more details on what is valid data).


In just the normal course of "channel surfing", I have gotten locked out all the time. By channel surfing, I mean manually clicking a link to listen to it every few seconds. There is not a shoutcast server on this public IP. I do have to browse for a few minutes in order to get it to lock me out.

You have inadvertently disallowed (manual) channel surfing. Would it be reasonable for you to either fix it or reduce the ban duration? I can click slower... but HOW SLOW do I have to click to not get banned? I mean... I only clicked about 50 stations before it locks me out!

[Jay]

yea when they started loading up the pls files rather then using direct IP's that made it so you were under the restriction again.

[lidontno1]

Originally posted by KXRM
yea when they started loading up the pls files rather then using direct IP's that made it so you were under the restriction again.

So is there another Shoutcast-like service out there that does allow channel surfing that I can use instead? I mean, I really like shoutcast, but I have no use for it if I can't listen to 50 channels until I find one that I want to listen to...

[Jay]

www.icecast.org www.steamcast.com

all i know of.