![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
Another day Another Error Message
Feb. 16th, 2012 07:24 am![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
marzydotes2011.livejournal.com
I tried to check out my stats on FF.net last night (forget Fiction Press, they haven't worked there in months) and got the following error message.
We are unable to process your request right now to the Login area and we apologize for this brief inconvenience.
If the problem persists, please contact support at support@fanfiction.com.
Thank you. - Site Staff
The next minute I logged in but then this morning, again, the error message shows up at both FF.net and the far more neglected sister site, Fiction Press.
I'm guessing they figured the doors to their cages might be ripped out if they resorted to the same old error messages from last weekend so they came up with a new one. At any rate, it seems like this site has become more unstable than ever. I posted four updates on FP and two on FF.net before the latest crash and burn and was starting to get reviews. But now the site's down for the count again.
I'll email support but like others have said, it's the bottomless pit or the black hole. I think the site is pretty much gone, so I'm starting to move my FF.net content to a blog and my Fiction Press stories to Booksie (which at least posts on a facebook page when it's down rather than leaving people in the dark) and hopefully some FF.net people out there can come up with some sites for even those outside of the most popular fandoms.
As always I wait....
UPDATE: I did send an email to them, after all they asked in their latest error message and I did advise them to consider hiring a better IT person or a first one. Their sites are both doomed unless they do this. I also signed up for Archives of Our Own and am like 2600 on the waiting list so I might be approved sometime near the end of March. Alas, my fandom is popular among its set but is not on that site.
So, I'll have to export my FFs to a blog and if FF.net comes up long enough to update my profile, I'll have to leave the new destination site in code. And move FP content (as upon reviewing my email I discovered I reported that site's problems last September and they're still unfixed) to other sites that manage to stay up most of the time (and post on a facebook page when they're down) like Booksie.com and CafeWriter.org. I get fewer hits at these sites but more reviews b/c hey, you need the accounts part of the site to stay up long enough for people to login and write reviews.
I'm taking a pragmatic approach as a writer. To simply store my stories where the site's up so I can like add more updates. That's clearly becoming less likely at FF.net which on its site says it's adding all these bells and whistles but what's the point if whenever they touch their server it crashes? Fix it first then add bells and whistles.
UPDATE: Apparently about an hour or so before this latest outages, stories started to not show up as being on the site after being uploaded or chapters being updated. Apparently this was "fixed" not long after but not long before the whole accounts storage server went kablooey. Are these problems related, can't answer that as FF.Net's not talking.
But then again, that site never has anything much to say about its numerous crises.
We are unable to process your request right now to the Login area and we apologize for this brief inconvenience.
If the problem persists, please contact support at support@fanfiction.com.
Thank you. - Site Staff
The next minute I logged in but then this morning, again, the error message shows up at both FF.net and the far more neglected sister site, Fiction Press.
I'm guessing they figured the doors to their cages might be ripped out if they resorted to the same old error messages from last weekend so they came up with a new one. At any rate, it seems like this site has become more unstable than ever. I posted four updates on FP and two on FF.net before the latest crash and burn and was starting to get reviews. But now the site's down for the count again.
I'll email support but like others have said, it's the bottomless pit or the black hole. I think the site is pretty much gone, so I'm starting to move my FF.net content to a blog and my Fiction Press stories to Booksie (which at least posts on a facebook page when it's down rather than leaving people in the dark) and hopefully some FF.net people out there can come up with some sites for even those outside of the most popular fandoms.
As always I wait....
UPDATE: I did send an email to them, after all they asked in their latest error message and I did advise them to consider hiring a better IT person or a first one. Their sites are both doomed unless they do this. I also signed up for Archives of Our Own and am like 2600 on the waiting list so I might be approved sometime near the end of March. Alas, my fandom is popular among its set but is not on that site.
So, I'll have to export my FFs to a blog and if FF.net comes up long enough to update my profile, I'll have to leave the new destination site in code. And move FP content (as upon reviewing my email I discovered I reported that site's problems last September and they're still unfixed) to other sites that manage to stay up most of the time (and post on a facebook page when they're down) like Booksie.com and CafeWriter.org. I get fewer hits at these sites but more reviews b/c hey, you need the accounts part of the site to stay up long enough for people to login and write reviews.
I'm taking a pragmatic approach as a writer. To simply store my stories where the site's up so I can like add more updates. That's clearly becoming less likely at FF.net which on its site says it's adding all these bells and whistles but what's the point if whenever they touch their server it crashes? Fix it first then add bells and whistles.
UPDATE: Apparently about an hour or so before this latest outages, stories started to not show up as being on the site after being uploaded or chapters being updated. Apparently this was "fixed" not long after but not long before the whole accounts storage server went kablooey. Are these problems related, can't answer that as FF.Net's not talking.
But then again, that site never has anything much to say about its numerous crises.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}