-
Notifications
You must be signed in to change notification settings - Fork 10
Open
Description
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
Metadata
Metadata
Assignees
Labels
No labels