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

Add IPFS service that is peered to https://ipfs.network.thegraph.com/ipfs/ #20

Open
schmidsi opened this issue Jan 11, 2023 · 8 comments

Comments

@schmidsi
Copy link

Currently, there is a single point of failure with https://ipfs.network.thegraph.com/ipfs/. Indexers should run their own node and peer to https://ipfs.network.thegraph.com/ipfs/ to increase resilience.

@trader-payne
Copy link
Member

Hi Simon,
Unfortunately I cannot add an IPFS container as it triggers netscans in datacenters and this will lead to many people having their cloud accounts banned. :)
I haven't seen a solution that works, apart from setting firewall rules on the private network ports, which then disable certain actions from indexers such as graph indexer status command, etc.

@schmidsi
Copy link
Author

Oh, that's bad. Thanks for the update. Shall we leave this issue open to investigate other options at a later point? Otherwise, feel free to close it.

@abarmat
Copy link

abarmat commented Jan 11, 2023

What about this proposed fix? ipfs/kubo#4343 (comment)

@abarmat
Copy link

abarmat commented Jan 11, 2023

That one I shared is temporary (but seems it should work) until this one lands ipfs/kubo#6932

@schmidsi
Copy link
Author

For context here would be the config to setup an IPFS node to peer with The Graph's hosted service IPFS node: https://docs.ipfs.tech/how-to/peering-with-content-providers/#content-provider-list (thanks to Leo)

@leoyvens
Copy link

leoyvens commented Jan 11, 2023

The peer ID of the network IPFS node (not hosted service) is QmUBRCtHivKQCXNykUdtpnhqSCTVuaE6ajLXANFG8Etp7j. This peer id has changed. We can look for the new one but I'd like to see how well things work without explicit peering. IPFS lookup has improved with recent versions of Kubo.

@trader-payne
Copy link
Member

I've seen reports that the flag doesn't stop it from net scanning. I'm willing to try it out but I need someone with a burner account that can afford to have their (baremetal) server (potentially) blocked in case this doesn't work.

@Chomtana
Copy link
Contributor

Chomtana commented Jun 8, 2023

I think flag IPFS_PROFILE: server works as I don't get any hetzner ban after using this flag

  ipfs:
    image: ipfs/kubo:v0.18.1
    container_name: ipfs
    restart: unless-stopped
    environment:
      IPFS_PROFILE: server
    expose:
      - 5001
    volumes:
      - ipfs_data:/data/ipfs
      - ./ipfs-init.sh:/container-init.d/ipfs-init.sh
    networks:
      - monitor-net

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants