-
Notifications
You must be signed in to change notification settings - Fork 489
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
[ipfs-geoip] failed to get and parse Data via ipfs.object.get('Qm*******') #1992
Comments
Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
Finally, remember to use https://discuss.ipfs.io if you just need general support. |
@SmarticoApps which version of ipfs-webui are you using (it should be listed in bottom left corner)? geoip database was updated in #1958 and was released in v2.16.0 |
@SmarticoApps thank you. This version did not ship with ipfs-desktop / Kubo yet, so the number of people who have updated geoip dataset (#1958) may explain why you have trouble finding some of its blocks. I am closing this, as this should improve after more people start co-hosting the dataset, and filled ipfs-shipyard/ipfs-geoip#91 for tracking upstream fix. As a workaround, you may want to preload entire geoip database via |
Thanks. I'm on a private IPFS network; is that why it doesnt sync from the co-hosted dataset? |
When I run that command, the command line remains blank for several hours with no feedback
|
Ah, yes. If you are in a private IPFS network, your node won't be able to fetch data from the public one. You can work around by doing |
From a public IPFS Node
|
As the error mentions your node is offline, run the daemon and try again |
Compiled latest repo of IPFS WebUI
https://github.com/ipfs/ipfs-webui/
Ubuntu 20.04.4 LTS
Node version 16.12.0
NPM version 8.1.0
WebUI works on remote IPFS Node; connecting to Private IPFS swarm.
Adds files successfully via the WebUI and they appear on all IPFS nodes.
http://5.161.121.x:3000/#/peers
shows all 7 peers; but location for all nodes is UNKNOWNError in console:
It repeats this error 7 times for all 7 peers
No custom modifications made to any source code.
The text was updated successfully, but these errors were encountered: