Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fails with 400 bad request #539

Closed
sgentile opened this issue May 14, 2021 · 2 comments · Fixed by #574
Closed

Fails with 400 bad request #539

sgentile opened this issue May 14, 2021 · 2 comments · Fixed by #574
Labels
Milestone

Comments

@sgentile
Copy link

I have my graphql server running on http://localhost:9000/api

(confirmed running)

this call:
npx @apollo/rover subgraph introspect http://localhost:9000/api

error[E004]: HTTP status client error (404 Not Found) for url (http://localhost:9000/)
              This error was unexpected! Please submit an issue with any relevant details about what you were trying to do: https://github.com/apollographql/rover/issues/new/choose
@sgentile sgentile added bug 🐞 triage issues and PRs that need to be triaged labels May 14, 2021
@lrlna
Copy link
Member

lrlna commented May 14, 2021

Thanks for the report @sgentile!

Could you run your command with --log debug, so npx @apollo/rover subgraph introspect http://localhost:9000/api --log trace, and let me know if you get starting with, let's say TRACE rover_client::blocking::client:.

Another thing to double-check, is whether your endpoint is federated. subgraph introspect only works for federated endpoints. So for example, given that my server is running on http://localhost:9000, and my subgraphs reside at http://localhost:9001 and http://localhost:9002, I can run only run subgraph introspect on 9001 and 9002. 9000 requires a graph introspect command, and subgraph introspect would error.

@lrlna
Copy link
Member

lrlna commented May 14, 2021

As point of comparison, here is what it looks like for me when I run subgraph introspect with --log=trace on the server (rather than a subgraph server):

image

@EverlastingBugstopper EverlastingBugstopper added this to the May 27 milestone May 27, 2021
@abernix abernix removed the triage issues and PRs that need to be triaged label Jun 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants