Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

Add Gateway multiaddrs to bootstrapers #973

Closed
daviddias opened this issue Sep 1, 2017 · 18 comments
Closed

Add Gateway multiaddrs to bootstrapers #973

daviddias opened this issue Sep 1, 2017 · 18 comments

Comments

@daviddias
Copy link
Member

@lgierth as soon as possible could, could you please provide the correct multiaddrs for the Gateways to be added to the bootstrapers list?

@daviddias daviddias assigned ghost Sep 1, 2017
@daviddias
Copy link
Member Author

@lgierth think we can do this today so that I can release a patch version and make users happy?

@ghost
Copy link

ghost commented Sep 1, 2017

  • /dns4/wss0.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmZMxNdpMkewiVZLMRxaNxUeZpDUb34pWjZ1kZvsd16Zic
  • /dns4/wss1.bootstrap.libp2p.io/tcp/443/wss/ipfs/Qmbut9Ywz9YEDrz8ySBSgWyJk41Uvm2QJPhwDJzJyGFsD6

Double check and let me know in case they don't work

@daviddias
Copy link
Member Author

@lgierth tested and it works, pushing on #975 (now fixing another issue caused by another PR)

Thank you so much! ❤️❤️❤️❤️

@JohnAllen
Copy link

Thanks for making this a priority @diasdavid & @lgierth!

@konsumer
Copy link

konsumer commented Sep 1, 2017

That config doesn't seem to work for me. I still get "DHT is not available". Do I need to do something differently?

@JohnAllen
Copy link

JohnAllen commented Sep 1, 2017

Probably, not sure what though. Your example doesn't not throw "DHT is not available" for me. Clear your cache? Added a couple of more bootstrap servers to your example. Does that also throw that?

@daviddias
Copy link
Member Author

@konsumer DHT not available is supposed to happen because in fact DHT is not available unless you activate it, see https://github.com/ipfs/js-ipfs#project-status and https://github.com/ipfs/js-ipfs#advanced-options-when-creating-an-ipfs-node

@konsumer you also see that log because if you have the logs to DEBUG=*

@daviddias
Copy link
Member Author

Tested the example again and seems to work fine

image

@konsumer
Copy link

konsumer commented Sep 1, 2017

In incognito (no cache, no indexdb) I don't see the errors, but the ipfs gateway link still doesn't work, which is the point of the demo.

@konsumer
Copy link

konsumer commented Sep 1, 2017

I was using chrome Version 60.0.3112.78 (Official Build) (OSX 64-bit) but updated to Version 60.0.3112.113 (Official Build) (OSX 64-bit) and it still doesn't work in incognito (or otherwise.)

@daviddias
Copy link
Member Author

@konsumer did you try @JohnAllen's version on #973 (comment) ?

@konsumer
Copy link

konsumer commented Sep 1, 2017

Yep, I tried JohnAllen's and it worked!

Did a diff:

diff konsumer.js JohnAllen.js 
28c28,30
<       '/dns4/nyc-2.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmSoLV4Bbm51jM9C4gDYZQ9Cy3U6aXMJDAbzgu2fzaDs64'
---
>       '/dns4/nyc-2.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmSoLV4Bbm51jM9C4gDYZQ9Cy3U6aXMJDAbzgu2fzaDs64',
>       '/dns4/wss0.bootstrap.libp2p.io/tcp/443/wss/ipfs/QmZMxNdpMkewiVZLMRxaNxUeZpDUb34pWjZ1kZvsd16Zic',
>       '/dns4/wss1.bootstrap.libp2p.io/tcp/443/wss/ipfs/Qmbut9Ywz9YEDrz8ySBSgWyJk41Uvm2QJPhwDJzJyGFsD6'

looks like the latest version of that config has the wss addresses which were added a couple hours ago

Awesome! Thanks for the help.

@ghost
Copy link

ghost commented Sep 1, 2017

You can remove all the bootstrap nodes with PeerIDs starting in QmSoL

@konsumer
Copy link

konsumer commented Sep 1, 2017

will do. maybe we could keep a list of working ones on ipfs (updated via ipns) and make the client grab it? Just an idea, but it might be really neat...

@ghost
Copy link

ghost commented Sep 1, 2017

Yes, we'll have TXT records a la _dnsaddr.bootstrap.libp2p.io dnsaddr=/dns4/and/so/on/ipfs/QmFoo, which can be used in multiaddrs as /dnsaddr/bootstrap.libp2p.io/ipfs/QmFoo -- your node will resolve that address before dialing. You could view this as a form of peer routing, where we consult a DNS domain name for an address of a certain peer.

Browser nodes can't do DNS lookups though, so this lookup task will have to be deferred to different node.

@konsumer
Copy link

Having more issues. Not sure if it's related, but in both pens I get Uncaught Error: no protocol with name: libp2p-webrtc-star, now.

@JohnAllen
Copy link

JohnAllen commented Oct 31, 2017 via email

@konsumer
Copy link

I am seeing it on orbit.chat, as well.

MicrowaveDev pushed a commit to galtproject/js-ipfs that referenced this issue May 22, 2020
* chore: update dependencies

License: MIT
Signed-off-by: Alan Shaw <alan.shaw@protocol.ai>

* chore: pin to 0.4.19 temporarily
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants