403 error when pushing Slicemachine changes

Developing with Prismic
1

Hi guys, hope you're doing well.

Recently when pushing changes in slicemachine I started getting this error.

An error happened while pushing your changes
{
  status: 403,
  message: `Unable to parse raw limit from {"message":"Invalid key=value pair (missing equal-sign) in Authorization header (hashed with SHA-256 and encoded with Base64): 'XXXX (here goes the value)'."}`
}

Please let me know if you can help me with this!
Thanks

1 Like
2

Describe your question/issue in detail

I am trying to push a change to a custom type to our staging environment but it just shows the loading icon forever.

The terminal is returning a 403 error (pasted below). I don't want to try pushing the change to production to see if it would work yet and I know maintenance work was done on staging environments this morning; could it be related?

Impacted feature

Slice machine

What steps have you taken to resolve this issue already?

Had my colleague test and he came to the same result, so it's not my set-up.
Searched the forum and it wasn't asked about yet?

Errors

This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
{ status: 403, message: Unable to parse raw limit from {"message":"Invalid key=value pair (missing equal-sign) in Authorization header (hashed with SHA-256 and encoded with Base64): '[token string]'."} }

Your Role

Software engineer

Hosting provider

Package.json file

Steps to reproduce

  1. Change a custom type
  2. Try to push changes to staging
1 Like
3

I think we created our tickets at the same time-ish! (Slicemachine changes 403-ing)

Glad to know it's not just me :+1:

1 Like
4

Probably a duplicate of 403 error when pushing Slicemachine changes, created at a similar time.

1 Like
6

Experiencing same issue as well.

1 Like
7

Hi @fhuneeus1, @dev52 and @r.cantin,

Thank you for flagging this, we're aware of an ongoing issue and are currently investigating. I hope to have an update for you soon :slight_smile:

I have merged the two topics to keep all the information in one thread!

8

Hi all,

An update for you: this issue is related to using older versions of the slice machine, a way to resolve this is for you is to update it to the latest version if you can. This will solve the issue entirely, but we're still working on fixing the core problem for those who can't update the slice machine for whatever reason.

I’ll keep you updated when the error code is gone and this is officially fixed!

9

Hi guys,

@Ezekiel it worked well, I could push the changes in slicemachine.
Thanks!!

1 Like
10

Hi again everyone,

Just to keep you in the loop, the issue with the error code is slightly deeper than we thought so it will take us a bit more time to resolve it. For the time being, we strictly recommend you update your slice machine to the latest version. This is the best and safest way to resolve this issue, as pushing despite the error might cause unwanted or unexpected behavior. We’ll let you know when we have a complete resolution if for any reason you can’t update your slice machine.

I've edited my message above to reflect the fact we recommend updating the slice machine. Thanks everyone for your patience with this :slight_smile:

11

All resolved now! We managed to fix it, so you should all be good to go with every version of slice machine :slightly_smiling_face:

Thanks for bearing with us!

1 Like