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

Unable to connect browser ipfs node with ipfs-cluster running in local #4348

Closed
logesh2496 opened this issue May 16, 2023 · 3 comments
Closed

Comments

@logesh2496
Copy link

logesh2496 commented May 16, 2023

  • Version:
    js-ipfs/0.16.1

  • Platform:
    Chrome Version 113.0.5672.92 (Official Build) (arm64)

  • Subsystem:

Severity:

High

Description:

  • I tried to connect to ipfs-cluster running in my local from the browser ipfs node examples.

await create({
repo: 'ipfs-' + Math.random(),
config: {
Addresses: {
Swarm: [
'/dns4/wrtc-star1.par.dwebops.pub/tcp/443/wss/p2p-webrtc-star'
]
}
},
})

After successfully connected to swarm address

const peerID = peerIdFromString('peerID here'); // import { peerIdFromString } from '@libp2p/peer-id
await ipfs.swarm.connect(peerID); // This throws error

  • Unable to connect to the local cluster,
    Error: The dial request has no valid addresses
  • I am trying to connect the browser ipfs nodes to the cluster

Steps to reproduce the error:

  1. Create a ipfs node on browser with /dns4/wrtc-star1.par.dwebops.pub/tcp/443/wss/p2p-webrtc-star as swarm
  2. Console will print "Swarm Listening: /dns4/wrtc-star1.par.dwebops.pub/tcp/443/wss/p2p-webrtc-star/p2p/peerid which is correct
  3. Now do ipfs.swarm.connect(peerID)
  4. This produces error: The dial request has no valid addresses
@logesh2496 logesh2496 added the need/triage Needs initial labeling and prioritization label May 16, 2023
@welcome
Copy link

welcome bot commented May 16, 2023

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

  • "Priority" labels will show how urgent this is for the team.
  • "Status" labels will show if this is ready to be worked on, blocked, or in progress.
  • "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

@SgtPooki SgtPooki added kind/resolved-in-helia and removed need/triage Needs initial labeling and prioritization labels May 16, 2023
@SgtPooki
Copy link
Member

SgtPooki commented May 16, 2023

Hello @logesh2496,

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

This current bug or feature request will not be addressed in js-ipfs due to its deprecation. We believe the issue has been resolved in Helia though 😊

As a result, we are going to close this issue. If you think we have done this in error, please feel to reopen with any comments in the next week as we will circle back on the reopened issues.

We hope you will consider Helia for your IPFS in JS needs. We look forward to engaging with you more there.

Thanks,
@ipfs/helia-dev

@SgtPooki SgtPooki self-assigned this May 17, 2023
@logesh2496
Copy link
Author

Thanks @SgtPooki

Can you point me to these documentation resources:

  1. Pinning files (similar to https://github.com/ipfs/js-ipfs/blob/master/docs/core-api/PIN.md#ipfspinaddipfspath-options)
  2. Connecting to a cluster

on helia? I have been exploring but couldn't find any.

Thanks again.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Status: Done
Development

No branches or pull requests

2 participants