-
Notifications
You must be signed in to change notification settings - Fork 500
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
Unable to remotely pin on Pinata with the WebUI #2096
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. |
Hey @mariaa144 thanks for submitting this issue and your detailed descriptions. I'm sorry you're experiencing an issue with pinning your content. What ipfs version are you connecting the webui to? Kubo recently added support for the It looks like you're using at least Kubo 0.18.0 because of the transport in your provider array containing
For a temporary fix, try one of the following:
I will mark this issue as a bug and investigate some mitigation methods in the meantime. Please let us know if you are able to workaround this successfully, and we will update you when we have more details. |
@mariaa144 I looked into this further, and AFAIK, Kubo should not be falling over on unknown protocols, and I think this is happening in the Pinata API server stack. I believe that Pinata will need to either update to the latest libraries or patch things similar to ipfs-webui/patches/multiaddr+8.1.2.patch Lines 1 to 34 in 1cf2fe7
I reached out to the pinata team internally to discuss this and they will hopefully implement a fix soon. As for webui, the only fix I can think of to resolve this now, and in the future, is to remove protocols conditionally when they fail at the service level, but that should be done on the service side. I think this issue should be closed because:
Please let me know if you feel differently or have been unable to resolve this issue. |
I tried to change the config by removing all the lines with "quic" in them but I still got the error. I edited the |
@mariaa144 can you share your config with me? |
I tried to remove keys. Let me know if I left anything secret in there. I put back the
|
Can you try updating the "Swarm" section in your config to be the following? It's the same as what you get from running "Swarm": {
"AddrFilters": null,
"ConnMgr": {},
"DisableBandwidthMetrics": false,
"DisableNatPortMap": false,
"RelayClient": {},
"RelayService": {},
"ResourceMgr": {},
"Transports": {
"Multiplexers": {},
"Network": {
"WebTransport": false
},
"Security": {}
}
} |
Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days. |
@SgtPooki I tried the changes in my config, I restarted IPFS but I still got the same errors. Do you have any other suggestions for me to try? |
That's the best I can think of until Pinata updates or we solve this error. @lidel do you have any suggestions? |
Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days. |
This issue was closed because it is missing author input. |
why is bot keep closing issues not resolved? I hit this error today, and similar issues got resolved with no real solution. |
Describe the bug
When I try to remote pin using the webui I get an error and the pinning doesn't work. I have to go to Pinata web interface to pin manually. The remote pinning was working but after a recent update I started gettting the following error.
The error is:
Unable to set pinning at Pinata: HTTPError: reason: "INVALID_ORIGINS", details: "provider array entry: /ip4/10.117.144.19/udp/4001/quic-v1/p2p/xxxxx is not a valid peer multiaddr": 400 Bad Request
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The pinning should work and there shouldn't be an error.
Desktop (please complete the following information):
Additional context
I reached out to Pinata but the support person wasn't able to help me. She said if it was a problem with their service due to a new IPFS version then it would likely be fix sometime in the future.
The text was updated successfully, but these errors were encountered: