Skip to content

Pinning request returns 401 error #36

@SgtPooki

Description

@SgtPooki

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

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions