ERROR: Console request failed
Hi My app in production is having this problem, I'm using Vercel and see Vercel use Neon DB but got this error, before my app was working fine, but when I logged into the DB in mylocal, this problem appeared
ERROR: Console request failed
15 Replies
fair-roseā¢2y ago
same... think a "ip_allow" feature just maybe launched causing this hicuup ?
sensitive-blueOPā¢2y ago
Where do you get info about ip_allow? @Chachra
Has the problem you experienced occurred since today?
fair-roseā¢2y ago
blank screen...
fair-roseā¢2y ago
not sure if correlated... but I had a db hicuup as well š¦
sensitive-blueOPā¢2y ago
is that on the Neon DB site?
fair-roseā¢2y ago
yep.
sensitive-blueOPā¢2y ago
Has the problem you experienced occurred since today?
sensitive-blueOPā¢2y ago
Neon Status
Increased console and control plane API latency-Minor - Neon Status
We have identified that this incident has been caused by increased x20 times number of new connections in theĀ us-east-1Ā region. Load is back to normal and all systems work as expected now. During the incident, only Neon public API and new connections latency have been affected. Our engineering team implemented a fix and now working on deploying ...
other-emeraldā¢2y ago
Hey, can you be more specific? Where is this issue occurring? In the Neon console, or the JS application hat is connecting to the database? Can you share a log?
sensitive-blueOPā¢2y ago
I got that error in JS app that is using prisma, i use database URL from Vercel to connect my DB
other-emeraldā¢2y ago
It does sound like it's related to that incident you linked. CC @Daniel can you confirm the error message aligns with the incident earlier? I suspect it does.
sensitive-blueOPā¢2y ago
Invalid
prisma.configuration.findMany() invocation: Error querying the database: db error: ERROR: Console request failedfair-roseā¢2y ago
My db issues just happened at around 2 pm PST.
sensitive-blueā¢2y ago
If you are in the us-east-1Ā region, that would align with the issue today.
other-emeraldā¢2y ago
Thanks for confirming. That also explains why I didnāt see it. I was using the US west region.