The interface fails to be queried，/v1/graphql

[jsnobug]

Version Information

Server Version:
CLI Version (for CLI related issue):

Environment

  - HASURA_GRAPHQL_DATABASE_URL=postgres://postgres:postgres@postgresql:5432/postgres
  - HASURA_GRAPHQL_ENABLE_CONSOLE=true
  - HASURA_GRAPHQL_SERVER_ROOT_PATH:/hasura/home
  - HASURA_GRAPHQL_METADATA_RETRY_INTERVAL=5000 # Wait for 5 seconds before retrying connection
  - HASURA_GRAPHQL_DATABASE_CONNECTION_TIMEOUT=120 # Set connection timeout to 120 seconds

What is the current behaviour?

tap API router

What is the expected behaviour?

Do not request

How to reproduce the issue?

1.tap API router

Screenshots or Screencast

Please provide any traces or logs that could help here.

I find TopNav component has request fetchSchemaRegistryNotificationData, but I don't need schemaRegistry
const fetchSchemaRegistryNotificationData = useGetSchemaRegistryNotificationColor(projectID);

Any possible solutions/workarounds you're aware of?

Keywords

[robertjdominguez]

Hi @jsnobug — this isn't a bug with Hasura, so I've moved this from an Issue » DIscussion.

Thanks for reaching out!

From your description, it seems like the issue you're encountering is not with Hasura itself but rather with how your client application is configured to interact with the /v1/graphql endpoint. Here's why:

1. Client-Side Behavior: The problem you're experiencing might be related to how your client is sending requests. Common causes include:

   • Incorrect headers (e.g., missing or invalid Authorization headers).
   • Network-related issues, such as CORS misconfigurations.
   • Issues with your client-side code or library, like GraphQL client setup or middleware.

2. Debugging Steps: To help diagnose the issue further, you can:

   • Use a tool like Postman or curl to directly query the /v1/graphql endpoint. If it works, the issue is confirmed to be on the client side.
   • Verify that your client application is sending all required headers and request parameters.
   • Check the console logs or network tab in your browser for additional clues about the error.

If you'd like, feel free to share additional details about how your client is configured (e.g., what GraphQL client library you're using, and any relevant snippets of code or configurations). We're happy to help you troubleshoot further!

[robertjdominguez]

@jsnobug — I'm closing this due to inactivity. Please re-open if your issue persists!