That error can be tricky, but let's walk through the most likely fixes step by step:

1. You're using the wrong endpoint for structured queries #

This is probably the biggest issue here. When sending a structuredQuery to Firestore, you need to target the runQuery method endpoint, not the collection's base URL.

Your current URL is:
https://firestore.googleapis.com/v1/projects/typebot/databases/(default)/documents/users

But it should be:
https://firestore.googleapis.com/v1/projects/typebot/databases/(default)/documents:runQuery

The /users endpoint is for listing or getting specific documents, not running structured queries. Using the wrong endpoint can cause the server to respond with unexpected errors that manifest as HTTP/2 framing issues.

2. Check Insomnia's HTTP/2 configuration #

Sometimes Insomnia's HTTP/2 implementation can clash with certain APIs. Try forcing the request to use HTTP/1.1 instead:

• Open your request in Insomnia
• Go to the Settings tab (the gear icon)
• Under HTTP, change the Protocol dropdown to HTTP/1.1
• Re-send the request

3. Verify authentication is set up correctly #

Firestore won't process your query without proper auth, and an invalid/missing auth token can cause abrupt connection closures (which trigger framing errors):

• Make sure you're either:
  • Adding an API key as a query parameter: ?key=YOUR_FIREBASE_API_KEY to the end of the URL
  • Including an Authorization: Bearer YOUR_ACCESS_TOKEN header (for service accounts or user auth)
• Double-check that your API key/token has the necessary permissions to read the users collection

4. Rule out Insomnia-specific glitches #

Occasionally, Insomnia can get into a weird state. Try these quick fixes:

• Restart Insomnia entirely
• Create a brand new request from scratch (don't edit the old one)
• Clear Insomnia's cache (go to Preferences > Data > Clear Cache)

5. Check for network interference #

HTTP/2 framing errors can also stem from network issues:

• Disable any VPN, proxy, or firewall that might be intercepting the request
• Try switching to a different network (like mobile data if you're on Wi-Fi)

Once you fix the endpoint URL, that should resolve the issue in most cases. If not, work through the other steps to narrow down the problem.

内容的提问来源于stack exchange，提问作者Baptiste Arnaud