-
Notifications
You must be signed in to change notification settings - Fork 10
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
Pinning request returns 401 error #36
Comments
I'm not getting that error. Maybe try using Crust Wallet? Even if that doesn't work for you, I'm getting "status": "queued" in my response rather than "status": "pinning". I have said on the discord server, however that only seems to get around 1 message/day, if not less, non of which being the admins. |
Hey, try this token: |
I was successfully pinning content previously with an access token that no longer seems to be working.
I am able to validate that i see the same token at https://crustfiles.io/setting/, but the token is now returning an HTTP 401 error:
{"error":{"reason":"UNAUTHORIZED","details":"Invalid Signature"}}
.You can also see these errors at https://ipfs-shipyard.github.io/pinning-service-compliance/pin.crustcode.com.html#response-2
I'm wondering if someone can help me generate a new token, or figure out why my token is no longer considered valid.
references
The text was updated successfully, but these errors were encountered: