403 forbidden

plow · 26th March 2003, 07:54

[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 · 26th March 2003, 08:06

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 · 26th March 2003, 08:08

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 · 26th March 2003, 08:52

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

roby0215 · 26th March 2003, 09:28

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

omega1 · 26th March 2003, 10:17

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 · 26th March 2003, 10:45

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

garethpullen · 26th March 2003, 13:02

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 · 26th March 2003, 13:07

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

DJ_Lee_uk · 26th March 2003, 13:10

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 · 26th March 2003, 13:30

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 · 26th March 2003, 13:38

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 · 26th March 2003, 14:15

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 · 26th March 2003, 14:29

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 · 26th March 2003, 14:33

*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

creepradio · 26th March 2003, 14:50

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:8000 Creep Radio

NashuNatta · 26th March 2003, 14:53

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 · 26th March 2003, 17:55

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

Tom

omega1 · 26th March 2003, 18:02

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 · 26th March 2003, 18:08

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 · 26th March 2003, 22:13

Its working for me now. YES!!!

[yp_add] yp.shoutcast.com added me successfully

Kambriel · 27th March 2003, 11:27

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

klunkung · 27th March 2003, 12:19

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 · 27th March 2003, 12:46

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

klunkung · 27th March 2003, 12:57

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 · 27th March 2003, 13:24

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 · 27th March 2003, 13:24

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 · 27th March 2003, 13:36

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 · 27th March 2003, 13:42

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 · 27th March 2003, 13:52

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 · 27th March 2003, 14:07

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 · 27th March 2003, 14:20

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 · 27th March 2003, 14:27

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

PWRGRRL · 27th March 2003, 14:41

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 · 27th March 2003, 15:25

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 · 27th March 2003, 16:49

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

Anything is better than being in the dark.

Shelby

RadioDruid · 27th March 2003, 18:16

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

djmiked1 · 27th March 2003, 19:35

looks like i am up for the moment

PWRGRRL · 27th March 2003, 19:42

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

Shelby

alanevil · 27th March 2003, 22:25

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

26th March 2003, 07:54	#1
plow Junior Member Join Date: Feb 2003 Posts: 5	403 forbidden [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.

26th March 2003, 08:52	#4
jslmg Member Join Date: Mar 2003 Location: Seoul, Korea Posts: 79	403 Forbidden 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

26th March 2003, 09:28	#5
roby0215 Senior Member Join Date: Apr 2002 Location: Great White North Posts: 263	I have been broadcasting for 18 months now and started getting the message at about 3 AM toronto time Listen Or check out the website

26th March 2003, 10:17	#6
omega1 Registered User Join Date: Apr 2001 Location: Tenerife / Canary Islands Posts: 103	403 forbidden 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,

26th March 2003, 10:45	#7
Jay Moderator Alumni Join Date: May 2000 Location: Next Door Posts: 8,888	it seems as though it's related to certain ip's most likely this is a problem with the directory. -Jay \| Radio Toolbox.com

26th March 2003, 08:06	#2
rkcpi Registered User Join Date: Jun 2001 Posts: 25	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

26th March 2003, 08:08	#3
josephjrr Registered User Join Date: Mar 2003 Posts: 6	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?

26th March 2003, 13:02	#8
garethpullen Junior Member Join Date: Oct 2002 Location: UK Posts: 4	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!

26th March 2003, 13:07	#9
Jay Moderator Alumni Join Date: May 2000 Location: Next Door Posts: 8,888	you cannot fix it, this is something wrong at the directory site. -Jay \| Radio Toolbox.com

26th March 2003, 13:10	#10
DJ_Lee_uk Junior Member Join Date: Mar 2003 Location: Kent Posts: 2	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.

26th March 2003, 13:30	#11
garethpullen Junior Member Join Date: Oct 2002 Location: UK Posts: 4	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!

26th March 2003, 13:38	#12
moontrains Junior Member Join Date: Mar 2003 Location: Louisville Posts: 4	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.

26th March 2003, 14:15	#13
Psikick Member Join Date: Oct 2002 Location: TRANCELVANIA Posts: 50	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...

26th March 2003, 14:29	#14
Jay Moderator Alumni Join Date: May 2000 Location: Next Door Posts: 8,888	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. -Jay \| Radio Toolbox.com

26th March 2003, 14:33	#15
Boomtastic Junior Member Join Date: Aug 2002 Location: Wareham, MA Posts: 3	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

26th March 2003, 14:50	#16
creepradio Junior Member Join Date: Mar 2003 Posts: 1	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:8000 Creep Radio

26th March 2003, 14:53	#17
NashuNatta Junior Member Join Date: Mar 2003 Posts: 5	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.

26th March 2003, 17:55	#18
Tom Moderator Join Date: Apr 2000 Posts: 4,485	I sent an email to Tom Pepper regarding this issue so hopefully it will be resolved soon. Tom

26th March 2003, 18:02	#19
omega1 Registered User Join Date: Apr 2001 Location: Tenerife / Canary Islands Posts: 103	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?

26th March 2003, 18:08	#20
Jay Moderator Alumni Join Date: May 2000 Location: Next Door Posts: 8,888	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. -Jay \| Radio Toolbox.com

26th March 2003, 22:13	#21
josephjrr Registered User Join Date: Mar 2003 Posts: 6	Its working for me now. YES!!! [yp_add] yp.shoutcast.com added me successfully

27th March 2003, 11:27	#22
Kambriel Senior Member Join Date: May 2001 Location: Orlando, FL. Posts: 156	Doing It Again It seems to be giving the 403 messages again this morning and the listings are pretty slim on the Shoutcast site...

27th March 2003, 12:19	#23
klunkung Junior Member Join Date: Jan 2003 Location: Fort Myers, Florida USA Posts: 14	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.

27th March 2003, 12:46	#24
RadioDruid Junior Member Join Date: Mar 2003 Posts: 3	same problem here...what's up with that??

27th March 2003, 12:57	#25
klunkung Junior Member Join Date: Jan 2003 Location: Fort Myers, Florida USA Posts: 14	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.

27th March 2003, 13:24	#26
Kambriel Senior Member Join Date: May 2001 Location: Orlando, FL. Posts: 156	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.

27th March 2003, 13:24	#27
MysticRadio Junior Member Join Date: Mar 2003 Location: El Todo Mundo Posts: 4	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

27th March 2003, 13:36	#28
djmiked1 Junior Member Join Date: Mar 2003 Posts: 4	Yep Me Too 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

27th March 2003, 13:42	#29
MysticRadio Junior Member Join Date: Mar 2003 Location: El Todo Mundo Posts: 4	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?

27th March 2003, 13:52	#30
Kambriel Senior Member Join Date: May 2001 Location: Orlando, FL. Posts: 156	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.

27th March 2003, 14:07	#31
djmiked1 Junior Member Join Date: Mar 2003 Posts: 4	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???

27th March 2003, 14:20	#32
Kambriel Senior Member Join Date: May 2001 Location: Orlando, FL. Posts: 156	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.

27th March 2003, 14:27	#33
Dagan Junior Member Join Date: Mar 2003 Posts: 1	403 forbidden Hey I got it to work. I changed the port # and now [yp_add] yp.shoutcast.com added me successfully. Happy Happy Joy Joy

27th March 2003, 14:41	#34
PWRGRRL Junior Member Join Date: Dec 2002 Posts: 39	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

27th March 2003, 15:25	#35
jslmg Member Join Date: Mar 2003 Location: Seoul, Korea Posts: 79	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.