When I logged on this morning I was hoping it would be better but it's worse. Haven't even tried to battle. Tired of having to keep my finger on the refresh button to refresh over and over just playing games or doing anything. And wardrobe and autopricer are still broken. I don't have time to hand price over 1000 items since I have to go to work. Maybe when I get home tonight something will be working? No use even trying to battle. :(
CWs for Sale or Trade https://subeta.net/user_shops.php/shop/24266
The lag was bad this morning. I couldn't get onto Subeta because I kept getting
This page isn’t working. Subeta.net is currently unable to handle this request. HTTP ERROR 500
THIS. Constant blank pages. The site is unplayable and I can't battle. I'm trying and getting nowhere.
I'm also getting a lot of: This page isn’t working. Subeta.net is currently unable to handle this request. HTTP ERROR 500
How are we supposed to enjoy the site? Users are quitting like crazy
The page error is really bad today. No lag, just 500 page not working error. At this rate it's impossible to get things done, like questing the battling.
I would like to see them extend the battle through the weekend and just delay vesnali since it doesn't have a specific start date. I stopped battling at 2 million and there's no way I could even get close to 15 by Thursday. Questing last night was like torture refreshing constantly.
CWs for Sale or Trade https://subeta.net/user_shops.php/shop/24266
I keep accidentally buying multiples of quest items because I'm refreshing on the purchase page when it doesn't go through.
Still nothing but blank white pages today, refreshing and refreshing to get anywhere. I guess I will forego questing to try to meet my hydragellos goal of yesterday's and today's. The gelly war could have been started a week earlier with no threat of "overlapping with vesnali". :(
the 500 errors were so bad getting through quests was a nightmare
then when i go to buy an item sometimes it will say error
and autopricer is not working i get this message Problem connecting to the server; please reload the page and try again.
Beanie Baby Pricing PM me for information and cost. https://www.facebook.com/groups/538582170337230/
Hi, I'd like to confirm that the problem persists: "This page isn’t workingsubeta.net is currently unable to handle this request. HTTP ERROR 500"
Keeps loading every few clicks on the site. I have severe difficulty completing a quest... but I need sp to heal with healer to continue loosing to hydra. I have a t12 pet and it took several hours to get 1m damage. How on earth can we manage 15m damage in just a few days? I don't have a core & I'd like one. However, with the site acting up it's very challenging.
Moreover, I have a disability that makes flashing images an issue... I'm being bombarded by "flashes" of error screens, which is not good.
PS: I am using Chrome, on a laptop with Windows 10.
"This page isn’t workingsubeta.net is currently unable to handle this request. HTTP ERROR 500"
I got this when I clicked the link to this very forum 🤣
I can't battle because of the page errors so the next page load goes on forever and I have to refresh a few times to get it to work.
Not even gonna try to play today. I just did Shinwa and Bathhouse because I'm working to get their respective achievements. I'll come back tomorrow. Sucks to be wasting my gold acc perks like this.
Welp nothing works properly yet I gather? Still cannot log into New Subeta. Blank pages every other click. Guess I’m watching Netflix for the next few days. Not gonna bother checking back here because it’s futile atm.
this is a good point ... i try to be as patient as possible, and i understand that these things just happen i guess, but some of us are subscribers ... : (
yo mistuh white
It is back to 504 instead of blank page now. Idk if this is better or not...
[IMG]https://img.pokemondb.net/sprites/black-white/anim/normal/staraptor-f.gif[/IMG][flower=EagleWing]
👋 Good morning everyone!
Just pushing out some infrastructure changes that should hopefully keep the site moving quickly, and coming here to give an update and a little bit more information.
The problems that face the site right now are cascading, which means that one single failure point can bring the rest of the site down. In this case, the boss battle added an extreme amount of stress on our caching layer (Redis), which everything else relies on now.
asked me the excellent question of "why now" in our internal chat, and the reason is honestly 🤷♂️. We have a lot more pages that rely on Redis and caching, we have a lot more information going through those places, and it's really hard to debug the battle code, most of which hasn't been touched in 10 years.
We have charts that show us the relative usage across the site, and roughly where load is coming from. In our newer areas of the site (wardrobe in particular) we can see down to the line of code that is causing problems, and unfortunately we can't see that level of feedback or detail in the old code. It would take weeks (at least) to rig up the old code to have that kind of visibility, and that is time and resources we just don't have.
So the solution for something like this is "quickly try to find the cause, and if not, throw more money at the problem". In this case, that meant spinning up additional "legacy" servers (what powers "old" subeta), and a new, more powerful Redis instance. These things take time to come up, and cost a significant amount of money on start up / shut down. For example, the next tier of Redis means an additional $500 (bi-weekly) and requires some hand holding to downgrade after an event. We do these things proactively (we were already running the largest Redis instance we've ever needed) and sometimes the duct tape still fails to hold things together.
So: We are not going to extend the boss fight. The nature of this is the case where if we extended, we'd just be doing the same thing (fire fighting in the background and hoping the site won't keep crashing) and promising to extend, and then again, and then again. I'm going to chat with galaxia, cranberry and jason about how we can do something that isn't extending this fight for everyone, or a way that we can at least give y'all SOMETHING for hitting the button over and over when the site is barely up.
Thank you for being patient with us, we want the site to work as well as you do (probably better, none of you get paged at 3am when the site goes down, a pager I've now carried for.... 15 years?) and are working on some exciting updates to get us in that direction, that we aren't quite ready to talk about publicly yet. I want to spend way less time fire fighting and way more time working on new things... ;)
💖 ✨ 🤗
Thanks . That's a great explanation. I appreciate your time and effort.
And an image for illustration:

You can see a MASSIVE redis spike happen, which then throws the whole site into disarray, because everything is trying to grab from, and write to, the cache at once. And then people are refreshing to get the site to load, which is trying to grab more from the cache, and then the cron gets put into a queue, etc.
💖 ✨ 🤗
Thank you for the explanation/update! Appreciate all you do
Hey! I really appreciate all you do and I think it's super cute you have a Subeta pager.
I wanted to just ask a few questions, and I understand if some of this information might be privileged but I ask because I'd like to help anyway I can,
Are you using Elasticache (or whatever Azure runs)? If you do have you tried caching locally to the server itself? Also are we caching a lot of volatile data? because something like that would overload the caching rather quickly.
this is my first year here playing with full focus and daily, so I don't know exactly how the staff handles battledome wars, but couldn't the gelatins wait a bit? it had to be done now? from the explanations (btw, thanks for the detailed explanation!) it seems the boss is causing all this trouble, so that is why i'm asking.
[sup]forum image by [/sup]