Unable to remotely pin on Pinata with the WebUI

[mariaa144]

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:

1. Setup remote pinning with Pinata
2. Try to pin a file
3. Notice error at the bottom of the webui

Expected behavior
The pinning should work and there shouldn't be an error.

Desktop (please complete the following information):

• OS: Arch Linux (Garuda Linux)
• Browser: Firedragon
• Version: Revision 546fb5a

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.

[welcome]

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]

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 quic transport, which may not be supported by some services, but the webui should be able to handle this via graceful degradation of some sort. (we don't right now, which is why this is a bug in webui)

It looks like you're using at least Kubo 0.18.0 because of the transport in your provider array containing quic-v1. You can read more about the quic protocol changes at https://github.com/ipfs/kubo/releases/tag/v0.18.0

QUICv1 and WebTransport config migration
To support QUICv1 and WebTransport by default a new config migration (v13) is run which automatically adds entries in addresses-related fields:

Replace all /quic/webtransport to /quic-v1/webtransport.
For all /quic listeners, keep the Draft-29 listener, and on the same ip and port, add /quic-v1 and /quic-v1/webtransport listeners.

For a temporary fix, try one of the following:

1. Disable webtransport/quic when talking to pinata (you need to modify ~/.ipfs/config, more descriptions about how this is enabled described at https://github.com/ipfs/kubo/releases/tag/v0.16.0#-webtransport-new-experimental-transport)
2. use kubo 0.17 or other ipfs daemon that doesn't have webtransport/quic enabled by default until Pinata does.
   • This may require also updating your config, depending on how you're running the backing ipfs daemon for your webui instance.

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.