-
Notifications
You must be signed in to change notification settings - Fork 68
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
illegal base64 data at input byte 'x' for decoding vapid private key #29
Comments
I'm having the same issue when trying to send notifications. I have generated the key using openssl like:
I think that is throwing an error in the function Thanks! |
@juan88 Is there a reason you are not using the |
Hi! No there was no specific reasong why. I started with a tutorial from the mozilla's blog and I created the keys in the way I posted. Then I created a couple of keys with the function you specified and save them to a file. That is the correct way to handle it right? I mean, the keypair generated is supposed to be reused across all the notifications that you sent. That worked for me. So I think that is an issue with the way that the keys are encoded. If you generate the keys by any other method, the function |
in our organization's fork, we have made a change where we decode vapid keys with this method
which solves this issue for us. |
Hi
I'm experiencing this error while trying to send notifications
My private key has a "+" in the string and the input byte location points to this char. How can I get over this?
My public key also has a "+" in it. Same issue here as well
Any help appreciated
Thank you
The text was updated successfully, but these errors were encountered: