Invalid IP address while running IPFS.create() command in NodeJS file

[Shreyash1601]

I have made an expressJS server to handle http requests to store and retrieve data from IPFS. Most of the time the swarm connectivity fails and throws an error "not a valid IP address. Please guide me on this. It's an importatnt element of my project

[welcome[bot]]

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.

[achingbrain]

Do you have a minimal reproduction that we can run to see the problem?

[Shreyash1601]

Kindly clone the repository https://github.com/Shreyash1601/IPFS-server.git Run the following commands npm install nodemon ipfs1.js

[github-actions[bot]]

Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days.

[achingbrain]

I have observed something very similar in CI on Windows only, then recently again on Mac OS. It seems the regular expressions used by is-ip may get optimised at runtime to an invalid state.

We've removed is-ip from @multiformats/multiaddr in favour of @chainsafe/is-ip which doesn't use regex.

It's an in-range semver update so could you please try removing any lockfiles and reinstalling the deps?

If it still happens can you please paste the output of npm ls is-ip in your project root?

[github-actions[bot]]

Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days.

[Shreyash1601]

I have provided all the necessary information which I could. Kindly clone the code which I have mentioned in earlier mail and please resolve it

On Thu, 10 Nov, 2022, 5:57 am github-actions[bot], @.***> wrote:

Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days.

— Reply to this email directly, view it on GitHub https://github.com/ipfs/js-ipfs/issues/4213#issuecomment-1309583024, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOEHFZQPZCTDR33N2CTWVSLWHQ6OVANCNFSM6AAAAAAQQC42FY . You are receiving this because you authored the thread.Message ID: @.***>

[Shreyash1601]

Sir the issue is resolved. But it has initiated a new issue and that is "it's not able to generate a unique Hash ID each time a new data is stored. It's giving same Hash ID everytime"

On Thu, 3 Nov 2022 at 21:43, Alex Potsides @.***> wrote:

I have observed something very similar in CI on Windows only, then recently again on Mac OS. It seems the regular expressions used by is-ip https://www.npmjs.com/package/is-ip may get optimised at runtime to an invalid state.

We've removed https://github.com/multiformats/js-multiaddr/pull/280 is-ip from @multiformats/multiaddr in favour of @chainsafe/is-ip which doesn't use regex.

It's an in-range semver update so could you please try removing any lockfiles and reinstalling the deps?

If it still happens can you please paste the output of npm ls is-ip in your project root?

— Reply to this email directly, view it on GitHub https://github.com/ipfs/js-ipfs/issues/4213#issuecomment-1302344149, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOEHFZTPX5K7LLBUCLLNNZ3WGPQB5ANCNFSM6AAAAAAQQC42FY . You are receiving this because you authored the thread.Message ID: @.***>

[github-actions[bot]]

Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days.

[github-actions[bot]]

This issue was closed because it is missing author input.