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

Getting content from browser node to gateway using 0.35 RC #1923

Closed
aphelionz opened this issue Mar 12, 2019 · 3 comments
Closed

Getting content from browser node to gateway using 0.35 RC #1923

aphelionz opened this issue Mar 12, 2019 · 3 comments
Assignees
Labels
exp/wizard Extensive knowledge (implications, ramifications) required kind/bug A bug in existing code (including security flaws) kind/wontfix-migration-available P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked topic/libp2p Topic libp2p

Comments

@aphelionz
Copy link
Contributor

aphelionz commented Mar 12, 2019

  • Version: js-ipfs 0.35 RC
  • Platform: Browser (Chromium)
  • Subsystem: ipfs add / ipfs get

Type: Question

Severity: High

Description:

I'm running a browser node with js-ipfs 0.35 with DHT enabled. I'm adding content via a simple ipfs.add call. I can retrieve the content locally, and via a directly-connected peer via ipfs.get but I can't seem to get a public gateway.

What's odd is that I'm fairly certain I used to be able to do this with previous versions of js-ipfs, but maybe I'm crazy and I'm not remembering correctly.

Steps to reproduce the error:

Here's my IPFS confug on the browser node, let me know if you need any other information.

// js-ipfs version 0.35 RC

new IPFS({                                                         
  preload: { enabled: false },                                                  
  relay: { enabled: true, hop: { enabled: true, active: true } },               
  EXPERIMENTAL: { pubsub: true, dht: true },                                    
  repo: "./ipfs",                                                               
  config: {                                                                     
    Addresses: {                                                                
      Swarm: ['/dns4/ws-star.discovery.libp2p.io/tcp/443/wss/p2p-websocket-star']
    }                                                                           
  }                                                                             
});                                                                             

Adding content to a browser node using this configuration and then trying to load it via a public gateway like https://ipfs.io causes a content timeout.

@alanshaw alanshaw added kind/bug A bug in existing code (including security flaws) exp/wizard Extensive knowledge (implications, ramifications) required status/ready Ready to be worked P1 High: Likely tackled by core team if no one steps up labels Mar 13, 2019
@cryptoquick
Copy link

I think this is related to #1526 and #1942
Definitely feeling the pain on this one, and I'll do my best to investigate, but I'm not seeing anything obvious pop out at me just yet.

@vasco-santos
Copy link
Member

This is related with the usage of the libp2p-kad-dht. FYI We will be working on rewriting the DHT according to the most recently changes on go-libp2p-kad-dhtonce the Spec is done. After that, we should revisit if this is a problem

@jacobheun jacobheun added the topic/libp2p Topic libp2p label Jun 11, 2020
@SgtPooki SgtPooki self-assigned this May 17, 2023
@SgtPooki SgtPooki moved this to 🥞 Todo in js-ipfs deprecation May 17, 2023
@SgtPooki
Copy link
Member

js-ipfs is being deprecated in favor of Helia. You can learn more about this deprecation and read the migration guide.

Please feel to reopen with any comments by 2023-06-02. We will do a final pass on reopened issues afterwards (see #4336).

This issue is most likely resolved in Helia, please try it out!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
exp/wizard Extensive knowledge (implications, ramifications) required kind/bug A bug in existing code (including security flaws) kind/wontfix-migration-available P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked topic/libp2p Topic libp2p
Projects
No open projects
Status: Done
Development

No branches or pull requests

6 participants