Over the last few days my acssess to fanfction.net has been hit and miss with it frequently throwing odd errors.
has anyone else been having the same problems?
----
E: "Did they... did they just endorse the combination of the JSDF and US Army by showing them as two lesbian lolicons moving in together and holding hands and talking about how 'intimate' they were?"
B: "Have you forgotten so soon? They're phasing out Don't Ask, Don't Tell."
It's gotta be the ads. Their ad providers have some HORRENDOUSLY gimmicky ads.
''We don't just borrow words; on occasion, English has pursued other languages down alleyways to beat
them unconscious and rifle their pockets for new vocabulary.''
-- James Nicoll
I've been adblocking the place for years. And scriptblocking. And I still get the same blecherous errors recently.
There've been reports that those ad's have also been serving up malware to some users. And the flash ones were horrendously annoying... as soon as you moused over them "HEELLLOOOO!!"... which would be fine, except you had to mouse over them to use the site's controls, or your browser. Okay, so it wouldn't be fine at all
________________________________
--m(^0^)m-- Wot, no sig?
The mobile site seems to be working fine. So if it's giving you trouble, try changing the www. to m.
-Morgan. Or you can try yelling at the site like it were a mule, but that's less likely to work...
Same here. I hope they get this fixed soon. Changing it to the mobile site is working for me, but I'm not a huge fan of the font or layout when its on a computer screen. It's better than nothing though.
-----
Stand between the Silver Crystal and the Golden Sea.
"Youngsters these days just have no appreciation for the magnificence of the legendary cucumber." --Krityan Elder, Tales of Vesperia.
same problem here. every link is throwing weird failure pages- randomly
Well to be more specific - any page may send an error page at any time and then be perfectly fine a few minutes later - this includes ones that you may have been able to view a minute or so previously
It works about 1/3 of the time for me.
-----
Stand between the Silver Crystal and the Golden Sea.
"Youngsters these days just have no appreciation for the magnificence of the legendary cucumber." --Krityan Elder, Tales of Vesperia.
Huh. I'm not seeing any of this. But I'm using Seamonkey with NoScript and a few other tools-o-paranoia, so maybe I've got it locked down enough not to be affected.
-- Bob
---------
Then the horns kicked in...
...and my shoes began to squeak.
Nope not even the mobile version is working. It still reports something is wrong on port 119, at a random residential IP address. i would almost think it their database being wonky but it is a random residential IP address.
it would seem to be on their end since it is an internal server error.
E: "Did they... did they just endorse the combination of the JSDF and US Army by showing them as two lesbian lolicons moving in together and holding hands and talking about how 'intimate' they were?"
B: "Have you forgotten so soon? They're phasing out Don't Ask, Don't Tell."
Port 119 is NNTP, isn't it? A random residential IP would be somewhere on their own network. A wonky database would go looking for the actual story content at that IP location... and find that it wasn't where it was supposed to be, so throw an error.
________________________________
--m(^0^)m-- Wot, no sig?
i've been getting [random residential ip]:116 as well
someone screwed the pooch somewhere.
-Terry
-----
"so listen up boy, or pornography starring your mother will be the second worst thing to happen to you today"
TF2: Spy
Revising my comments of earlier: I'm still having no problem visiting the site or reading stories, but search crashes on me.
-- Bob
---------
Then the horns kicked in...
...and my shoes began to squeak.
I've just got a few errors on port 117, which is the UUCP (Unix-to-Unix Copy) Path service according to IANA and Wikipedia. This actually makes some sense compared to NNTP (119) and ANSA REX Notify (116), whatever that last is.
Update:
It seems the guys/galls at ff.net have got a handle on things. I left a error page alone for about 2 mins and refreshed to get the real page.
I've just checked the tab I have with an error message on, and they definitely say that it's on port 117.
Just a thought. We are assuming that the 116-119 numbers are ports. It might be something entirely different (perhaps an instance number or other local I'd to that ip). Just because we have ip:number doesn't mean that number is the classic port identification
-Terry
-----
"so listen up boy, or pornography starring your mother will be the second worst thing to happen to you today"
TF2: Spy
Hmm. I haven't been getting any "port XYZ" messages, but yesterday evening I got a very definite and repeatable weird error page when trying to visit the author page for ShaperV (author of Indomitable and Time Braid, the latter recently linked in the updates thread); everything else seemed to work, but that one page threw errors.
It was working again this morning, though...
Hm. Now I'm occasionally getting things like this:
Quote:FanFiction.Net Error
An error has occurred while processing your request.
Please email this error message to via support@fanfiction.com.
All errors are logged for administrative and security purposes.
190.204.73.143:116
/s/4340385/4/
-- Bob
---------
Then the horns kicked in...
...and my shoes began to squeak.
Yes, that's the error I got yesterday - barring exact IP address and the /s/IDnumber/chapter/ part - and I'm getting it again now. (I do now see the IP and port, I just hadn't noticed them before.)
Edit: I am actually now getting this for all story pages AFAICT, including one which I had successfully loaded just seconds before I first saw the error today. The IP addresses are all different, though.
Edit the second: ...and now it's working again. This has been a fairly whiplash ten minutes or so; we will see how long the current state lasts.
FWIW, I'm reasonably sure FF.net had developed into a geographically diverse server farms. At least 2, from what I've seen on this thread and other complaint threads, as the IP addresses throwing the complaints are in a couple ranges.
Based on these and other ecent issues, it sounds like either their replication processes are getting too big to handle, or they need some maintenance (read, a bounce). They may need to expand their BW again.
Is anyone else getting 503 and 502 errors on FF.net right now, or is it only me?
Edit: 408 errors too.
-----
Stand between the Silver Crystal and the Golden Sea.
"Youngsters these days just have no appreciation for the magnificence of the legendary cucumber." --Krityan Elder, Tales of Vesperia.
Quote: Is anyone else getting 503 and 502 errors on FF.net right now, or is it only me?
I'm getting those at the moment. (10/10/10 10:52pm CDT)
"Don't cry because it's over. Smile because it happened."
--Dr. Seuss
yup, look like something happened to the backed
-Terry
-----
"so listen up boy, or pornography starring your mother will be the second worst thing to happen to you today"
TF2: Spy