I also get these occasionally while questing, been getting them for... hm, at least a week now?
I just got it right now while trying to start one of Quentin's quests. :/ Reloading the page solves it and starts the quest normally.
I quest at just about the same time every day and today is the first I've seen that problem. It happened off and on for most quest givers, including item hunt. Also, reloading didn't do anything for me, it didn't even look like it refreshed at all. I had to go back to my subeta bookmark and navigate back to page manually. But that could be my browser or something. Using firefox.
I'm also using Firefox. Firefox Quantum 57.0 in my case. Just got the error again. It doesn't look like it's a thing that happens on a set schedule, today I'm questing later than I usually do and I still got it.
It only happens when starting a new quest.
I either haven't gotten it, or haven't noticed it while buying from main shops while questing. I'll pay more attention while questing tomorrow because I'm just wrapping it up tonight.
[edit] Spoke too soon! Just got the error while trying to buy an item (Green Tea) from Get Mugged via shop search. :/
Is everyone who has gotten this using Firefox Quantum? (Side note- please include browser info when reporting bugs :) )
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
I have the same as ! Firefox Quantum, 57.0 (64-bit) with Windows 7.
I'll ask a friend if he's still been getting the error when he gets online, I believe he's using Chrome.
I use Chrome for all my Subeta stuff and I haven't encountered this issue at all, so yeah IDK but it could be a browser thing with Firefox.
Given that Firefox Quantum is such a new browser, and it seems to be happening randomly and go away with a page reload, I don't think this is an error on Subeta's end. I would wait to see if it's fixed in the next update of Firefox. If the error persists, I might get in touch with some Mozilla engineers to see if we can get any insight on what the problem is. But tl;dr this is a wontfix for now.
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
Alright, thank you for explaining and looking into this! :D I'll make a memo to keep an eye on things after Firefox gets an update.
I've been getting lots of lag, half loaded pages, and those:
Error 504 Ray ID: 3ca0f045c8924439 • 2017-12-08 16:01:30 UTC Gateway time-out
Error 504 Ray ID: 3ca0f40acc8f4439 • 2017-12-08 16:04:11 UTC Gateway time-out
Well, Firefox got updated to 57.0.2, and now I got the 400 Bad Request error while trying to scratch a scratchcard. I guess it's a step up from quests and main shops? ;P
[edit] And another while trying to start a Wizard quest. Looks like the Firefox update didn't do much. D:
Hmm okay. I have to ask, is there any pattern to it at all, that you notice, as to what pages or types of pages it occurs on? Does it ever happen when you are submitting forms, or only when you are navigating to a new page. And when you get the 400 error, does it just say "400 Bad Request" or is there anything else? (Maybe provide a screenshot?)
Oh, more important questions, I think these will help a lot.
Next time you get this error, could you please provide for me the exact URL of the page you get the error on?
Can you make sure that you are using HTTPS and not HTTP? I am wondering if it might be related to HTTP (since Firefox seems to have issues automatically correcting it to HTTPS) and if the error might only occur on HTTP.
As for the status code - Anything in the 400s is a "client error" meaning that there was something wrong with what the browser sent to the server (rather than something wrong with how the server responded) Usually 400 Bad Request means that the request had a syntax error, and the most common reason for it is a broken link or a link that has invalid characters. So I hope seeing the exact URL will help in case it's a URL problem, if not we can look at debugging the exact headers to see what is going on.
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
When this started happening to me, it would happen frequently when starting any type of quest (main, item hunt, battle) - but didn't happen EVERY time you start a quest - and when you try to buy from an NPC shop from the shop search (while doing a quest). IE. Sometimes you click start quest - or buy - and it's a blank page that only says 400 Bad Request cloudflare-nginx
It was happening so frequently - but still random enough to not happen every single time I did these things - that I actually started questing on my phone because tragically enough, mobile was faster than battling it on my desktop.
And I have experienced this error since firefox updated again.
However.
Funnily, today I quested on desktop for the sole purpose of trying to replicate it and it didn't happen even once. For anything, the entire time. So, whatever that means. I'll definitely be keeping an eye out for it if it ever happens again. @ Bug
I've noticed it happening occasionally when I go click the "Start Quest" button, when buying from main NPC shops via shop search (hitting the "buy" button on SS, but I've only noticed it popping up with main shops, not user shops), and when clicking "Scratch" after picking a scratchcard from the dropdown on the Scratchard game page.
It's not guaranteed to pop up, which is curious. It either happens, or doesn't.
@ Bug https://subeta.net/shop.php?shopid=29
The 404 Bad Request happened while I was trying to start a quest. It happened to me a couple of times while doing Wiz quests.
Like a good neighbor, stay over there!

Thanks. So far I notice reports have only been on these pages:
Please include your browser info when making reports!
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
@ Bug No problem! All those are it so far, specifically from buying from an NPC shop via shop search. I'm not a restocker, so I don't know if the error occurs while regularly buying from main shops, or if it's tied only to shop search. :'| I can try to test it, but given how random the error seems to be now (and that 504s are popping up today instead), I'm not sure if I'll have much success.
I'll keep an eye on it, though, and I'll post if I spot anything!