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 Gateway multiaddrs to bootstrapers #973

Closed
diasdavid opened this Issue Sep 1, 2017 · 18 comments

Comments

Projects
None yet
4 participants
@diasdavid
Member

diasdavid commented Sep 1, 2017

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

@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid

diasdavid Sep 1, 2017

Member

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

Member

diasdavid commented Sep 1, 2017

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

@lgierth

This comment has been minimized.

Show comment
Hide comment
@lgierth

lgierth Sep 1, 2017

Member
  • /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

Member

lgierth 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

@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid

diasdavid Sep 1, 2017

Member

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

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

Member

diasdavid commented Sep 1, 2017

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

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

@JohnAllen

This comment has been minimized.

Show comment
Hide comment
@JohnAllen

JohnAllen Sep 1, 2017

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

JohnAllen commented Sep 1, 2017

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

@konsumer

This comment has been minimized.

Show comment
Hide comment
@konsumer

konsumer 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?

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

This comment has been minimized.

Show comment
Hide comment
@JohnAllen

JohnAllen 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?

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?

@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid

diasdavid Sep 1, 2017

Member

@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=*

Member

diasdavid commented Sep 1, 2017

@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=*

@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid

diasdavid Sep 1, 2017

Member

Tested the example again and seems to work fine

image

Member

diasdavid commented Sep 1, 2017

Tested the example again and seems to work fine

image

@konsumer

This comment has been minimized.

Show comment
Hide comment
@konsumer

konsumer 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 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

This comment has been minimized.

Show comment
Hide comment
@konsumer

konsumer 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.)

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.)

@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid

diasdavid Sep 1, 2017

Member

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

Member

diasdavid commented Sep 1, 2017

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

@konsumer

This comment has been minimized.

Show comment
Hide comment
@konsumer

konsumer 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.

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.

@lgierth

This comment has been minimized.

Show comment
Hide comment
@lgierth

lgierth Sep 1, 2017

Member

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

Member

lgierth commented Sep 1, 2017

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

@konsumer

This comment has been minimized.

Show comment
Hide comment
@konsumer

konsumer 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...

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...

@lgierth

This comment has been minimized.

Show comment
Hide comment
@lgierth

lgierth Sep 1, 2017

Member

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.

Member

lgierth 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

This comment has been minimized.

Show comment
Hide comment
@konsumer

konsumer Oct 31, 2017

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.

konsumer commented Oct 31, 2017

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

This comment has been minimized.

Show comment
Hide comment
@JohnAllen

JohnAllen Oct 31, 2017

JohnAllen commented Oct 31, 2017

@konsumer

This comment has been minimized.

Show comment
Hide comment
@konsumer

konsumer Oct 31, 2017

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

konsumer commented Oct 31, 2017

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment