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!

[david-ourlegup]

Schema Registry Feature in CE Mode Causes Console Errors

Issue Summary

When running Hasura Community Edition in Docker, the console attempts to make Schema Registry API calls despite Schema Registry being an Enterprise/Cloud-only feature. This happens because:

1. The SchemaRegistry component in the console frontend unconditionally attempts to call the schema registry API
2. In CE mode, schemaRegistryHost is set to an empty string ('') in Globals.ts
3. The API call fails with networking errors as it tries to make requests to an invalid endpoint

This affects users of Hasura CE who are seeing console errors when the frontend tries to use Schema Registry features not available in Community Edition.

Proposed Solutions

1. Conditional API Calls: Modify hooks like useGetSchemaRegistryNotificationColor to check both:

   • If schemaRegistryHost is properly configured
   • If running in CE mode (consoleType === 'oss')

2. Empty Mock for CE: Create a mock implementation of the schema registry client that returns empty data for CE users

3. Environment Variable for Disabling: Add a configuration option to completely disable Schema Registry UI features in CE mode

Impact

This issue only impacts Hasura Community Edition users running the console locally. It doesn't affect functionality but does cause console errors and failed network requests that might degrade the user experience.

A proper fix would improve the console experience for CE users while maintaining full functionality for Enterprise/Cloud users without requiring code changes when upgrading.

[david-ourlegup]

Proposed fix: david-ourlegup@7c819d9

[robertjdominguez]

Ah, this makes much more sense now. I missed in the original issue that this was due to fetchSchemaRegistryNotificationData.

Let me pass this onto the console team, @david-ourlegup — thanks for the PR!

[robertjdominguez]

Actually, @david-ourlegup — I see you just shared a commit. Would you like to open a PR against hasura/graphql-engine and we'll get this triaged?