Open jdannenberg opened 2 years ago
@LowEntropyBody @ziboilihua @mmyyrroonn is there a better support channel for this?
Looks like the network connection failed
Looks like the network connection failed
Can I debug that somehow? Container has internet readily available (and fast enough).
I'm having a similar issue with the IPFS pinning interface against the public endpoint. Pins stay in status "queued" and sometime "pinning" but then requests for status fail with a HTTP 502 and file is not pinned:
> ipfs pin remote add Qmad5fXcex6QaKLT3WSE2eRWzUsDVrSsnqU48tDE1XusxL --service=crust2
Error: failed to check pin status for requestid="225dbc51-aa58-4d29-b63d-376b2b81be98-1666587645285" due to error: reason: "", details: "": 502 Bad Gateway
Same thing happens in code when I use the nodeJS ipfs-http client.
Looks like the network connection failed
Can I debug that somehow? Container has internet readily available (and fast enough).
Looks like "CRUST_SEED" you config in envs not match crust wallet key(Maybe contains space code at the end of seed string). you can command echo $CRUST_SEED
in your ipfs-pinning-crust container.
I'm also having the same issue, just a year later. My seed phrase wasn't incorrect as I just used the got library and used the key provided on crust files on the public one
I am trying to use this service but
ipfs pin remote add ...
does not terminate, respectively pins are stuck on statusqueued
.My envs:
My compose:
Adding remote pinning service via ipfs is successful:
ipfs pin remote service add crustpinner http://ipfs-pinning-crust:3000/psa <base64(sub-PubKey:SignedMsg)>
However,
ipfs pin remote add --service crustpinner --name test bafkreigppg5u55luhghpaumhjfvczr2c5pveuwp4t5nzhtww7vnuftls5e
does not terminate.The log shows:
and then:
My goal is to pin about 3 TB (3 million CIDs / pins), but the example used here is a very small text file.
Your help is very much appreciated!