Server error: We're verifying your browser - security checkpoint

Help
1

Hello!
Recently we went live with a new website.
We are moving from Wordpress to Nextjs / GraphQL. However our transition is not running smoothly on multiple levels.

  • Our graphql endpoint is causing issues, that we didn’t have in a dev/testing environments.
  • This morning we had a downtime of half an hour because of this Vercel error:
    We're verifying your browser: Vercel Security Checkpoint fra1::xxxxxxxxxx-xxxxxxxxxxxxxx
  • Every request resulted in a HTML page in our Vercel logs, containing this information.
  • We also noticed a random timeout of 60+seconds on the GraphQL route.

image
image657×661 34.9 KB

These are all the same error, not a single user was able to visit these pages at that time.
Example:
Then suddenly the ‘Vercel security checkpoint’ error was gone and everything worked again.
We had 500+ errors in a very short amount of time.
As you can see the request is not blocked by the firewall.

image
image1395×525 152 KB

image
image489×733 42.8 KB

The other errors are like this:
FetchError: request to https://funkey-fhldw4slo-funkey.vercel.app/api/graphql failed, reason: Client network socket disconnected before secure TLS connection was established

FetchError: request to https://funkey-fhldw4slo-funkey.vercel.app/api/graphql failed, reason: Client network socket disconnected before secure TLS connection was established
    at ClientRequest.<anonymous> (/var/task/apps/web/.next/server/chunks/1157.js:3674:11)
    at /var/task/apps/web/.next/server/chunks/6849.js:48359:55
    at AsyncLocalStorage.run (node:async_hooks:338:14)
    at SentryContextManager.with (/var/task/apps/web/.next/server/chunks/6849.js:48661:40)
    at SentryContextManager.with (/var/task/apps/web/.next/server/chunks/6849.js:37649:24)
    at ClientRequest.contextWrapper (/var/task/apps/web/.next/server/chunks/6849.js:48359:32)
    at ClientRequest.emit (node:events:529:35)
    at TLSSocket.socketErrorListener (node:_http_client:501:9)
    at TLSSocket.emit (node:events:517:28)
    at emitErrorNT (node:internal/streams/destroy:151:8) {
  type: 'system',
  errno: 'ECONNRESET',
  code: 'ECONNRESET',
  digest: '3898529144'
}

We didn’t configure any rules that should reflect this behaviour, so we shouldn’t be getting this HTML page at random times.

We can’t reproduce this on the fly, it just happens from time to time, that’s why it’s so concerning.
because this impacts other users on the site as well.

Example: https://funkeyteambuilding.nl/nl-NL/cities/oost-vlaanderen/oombergen
This now works, but didn’t before because of above stated error.

Stack: nextjs / react / graphql /postgresql
Site: funkey.be
Settings

  • We don’t have any firewall rules atm.
  • No ratelimits
  • DDOS mitigation is on.
  • We do have Cloudflare configured on DNS level

I hope someone can help me with this. This is my first big project with NextJS and Vercel and I’m clueless on how to debug this issue. These issues happen during certain periods of time and not constantly.
The issues always go back to the root of the cause: connectivity & security.

1 Like
2

It sounds like DDoS Mitigation challenging potentially malicious requests.

While Vercel’s system-level mitigations (such as DDoS protection) safeguards your websites and applications, it can happen that they block traffic from trusted sources like proxies or shared networks in situations where traffic from these proxies or shared networks was identified as malicious. You can temporarily disable all automatic mitigations for a specific project. This can be useful on business-critical events such as Black Friday.

You can set your project to bypass system-level mitigations to test this hypothesis. Just be aware that bypassing leaves your project vulnerable.

3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.