-
Notifications
You must be signed in to change notification settings - Fork 968
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
Can't use Infura IPFS with HTTP Basic Auth #3981
Comments
Try configuring the header by using a config file https://github.com/graphprotocol/graph-node/blob/master/docs/config.md#configuring-ethereum-providers |
@leoyvens that's for ethereum providers, I need this for the IPFS ( |
Apologies I misread, I don't believe we have this config for IPFS. |
I know, should I consider this a Bug or a Feature Request ? I can write a better title according to that. |
I don't think this ever worked so I'd consider it a feature request. PRs welcome though! |
Hello, As I have the exact same issue with infura, I had a deeper look at this issue. Basic authentication is actually well supported by The HTTP error 403 raised when trying to access the graph is in fact caused by an unsupported infura HTTP API:
->
According to the Infura documentation, there is indeed no way to retrieve the file size using the I manage to workaround this issue by simply removing this call from graphnode (as this is used only to control file sizes). Here are my patches FYI (I don't open the PR as the 2nd one is still a wa):
Hope this will help. |
@agourdon thank you for the detailed report. I would like to eventually not rely on |
also facing this issue, did anyone discover a solution? |
Any updates on this issue? |
Any updates? |
Graph Node does not use |
graph-node fails when I define ipfs address using HTTP Basic Auth in the URL.
What is the current behavior?
Starting with
graph-cli:0.33.0
, I can add the--headers
parameter to deploy a subgraph using Infura's IPFS.npx graph deploy \ --product hosted-service \ --version-label v1.0.0 \ --headers "{\"Authorization\": \"Basic bXlfdXNlcl9uYW1lOm15X3NlY3JldF9wYXNzd29yZA==\"}" \ --ipfs https://ipfs.infura.io:5001 my-subgraph subgraph.yaml \ --node http://localhost:8020
Configuring graph-node with
--ipfs=https://bXlfdXNlcl9uYW1l:HIDDEN_PASSWORD@ipfs.infura.io:5001/
But when configuring the graph-node to use Infura's IPFS, I get errors.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
--headers
parameterWhat is the expected behavior?
graph-node should be able to get Infura IPFS files
graph-node should support HTTP Basic Auth in the URL, like
https://[user:pass@]host[:port]
The text was updated successfully, but these errors were encountered: