Google search console blocked

Noext commented 7 months ago

Preliminary Checks

[X] I have reviewed the documentation: https://clerk.com/docs
[X] I have searched for existing issues: https://github.com/clerk/javascript/issues
[X] I have not already reached out to Clerk support via email or Discord (if you have, no need to open an issue here)
[X] This issue is not a question, general help request, or anything other than a bug report directly related to Clerk. Please ask questions in our Discord community: https://clerk.com/discord.

Reproduction / Replay Link

https://github.com/t3-oss/create-t3-app

Publishable key

pk_test_c2ltcGxlLWhvdW5kLTkyLmNsZXJrLmFjY291bnRzLmRldiQ

Description

When you ask google search console to test your url , clerk is throwing a 401 with this message in the debug


 authenticateRequest state is interstitial, {
    "status": "interstitial",
    "reason": "uat-missing",
    "message": "",
    "frontendApi": "simple-hound-92.clerk.accounts.dev",
    "publishableKey": "pk_test_c2ltcGxlLWhvdW5kLTkyLmNsZXJrLmFjY291bnRzLmRldiQ",
    "isSatellite": false,
    "domain": "",
    "proxyUrl": "",
    "signInUrl": "",
    "isSignedIn": false,
    "isInterstitial": true,
    "isUnknown": false,
    "token": null
  }

i can reproduce this error in postman with the nextjs dev server with this request ( user agent of google search console )

curl --location 'http://localhost:3000' \
--header 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:122.0) Gecko/20100101 Firefox/122.0'

removing the useragent or putting anything without Mozilla/5.0 inside is working ( ie: Chrome/13.0.782.112 Safari/535.1 )

Environment

System:
    OS: macOS 12.6.5
    CPU: (4) x64 Intel(R) Core(TM) i5-5250U CPU @ 1.60GHz
    Memory: 450.73 MB / 8.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 21.6.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.4 - /usr/local/bin/npm
    pnpm: 8.7.1 - /usr/local/bin/pnpm
    bun: 1.0.25 - ~/.bun/bin/bun
  Browsers:
    Chrome: 121.0.6167.139
    Safari: 16.4.1
  npmPackages:
    @clerk/nextjs: 4.29.3 => 4.29.3
    @radix-ui/react-slot: ^1.0.2 => 1.0.2
    @t3-oss/env-nextjs: ^0.7.1 => 0.7.3
    @tanstack/react-query: ^4.36.1 => 4.36.1
    @trpc/client: ^10.43.6 => 10.45.0
    @trpc/next: ^10.43.6 => 10.45.0
    @trpc/react-query: ^10.43.6 => 10.45.0
    @trpc/server: ^10.43.6 => 10.45.0
    @types/eslint: ^8.44.7 => 8.56.2
    @types/node: ^18.17.0 => 18.19.14
    @types/react: ^18.2.37 => 18.2.52
    @types/react-dom: ^18.2.15 => 18.2.18
    @typescript-eslint/eslint-plugin: ^6.11.0 => 6.20.0
    @typescript-eslint/parser: ^6.11.0 => 6.20.0
    @xixixao/uploadstuff: ^0.0.5 => 0.0.5
    autoprefixer: ^10.4.14 => 10.4.17
    class-variance-authority: ^0.7.0 => 0.7.0
    clsx: ^2.1.0 => 2.1.0
    convex: ^1.8.0 => 1.8.0
    eslint: ^8.54.0 => 8.56.0
    eslint-config-next: ^14.0.4 => 14.1.0
    fast-xml-parser: ^4.3.3 => 4.3.4
    google-auth-library: ^9.6.0 => 9.6.2
    googleapis: ^131.0.0 => 131.0.0
    jose: ^5.2.0 => 5.2.1
    lucide-react: ^0.320.0 => 0.320.0
    next: ^14.0.4 => 14.1.0
    postcss: ^8.4.31 => 8.4.33
    prettier: ^3.1.0 => 3.2.5
    prettier-plugin-tailwindcss: ^0.5.7 => 0.5.11
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    server-only: ^0.0.1 => 0.0.1
    superjson: ^2.2.1 => 2.2.1
    tailwind-merge: ^2.2.1 => 2.2.1
    tailwindcss: ^3.3.5 => 3.4.1
    tailwindcss-animate: ^1.0.7 => 1.0.7
    typescript: ^5.1.6 => 5.3.3
    zod: ^3.22.4 => 3.22.4

LekoArts commented 7 months ago

Hi, thanks for the issue!

You need to create and use a production instance for your deployed app. The behavior you're describing is expected when you use development instances.

Noext commented 7 months ago

very thanks

it possible to add this info in the debug log ?

clerk / javascript