Error: error:0906D06C:PEM routines:PEM_read_bio:no start line about node-telegram-bot-api HOT 5 CLOSED

Maybe the path is wrong or Windows sucks.

PS: Windows sucks!

from node-telegram-bot-api.

I was having the same problem but on a ubuntu server.
The solution was generate the certificates using the following commands:

openssl req -newkey rsa:2048 -new -nodes -keyout key.pem -out csr.pem
openssl x509 -req -days 365 -in csr.pem -signkey key.pem -out server.crt

found it here : http://stackoverflow.com/questions/22584268/node-js-https-pem-error-routinespem-read-biono-start-line

from node-telegram-bot-api.

I am facing the same issue: PEM routines:PEM_read_bio:no start line

I have generated public key and private key by using ssh-keygen. and I am converting my public key in .pem format by using

ssh-keygen -f my_public_key_file -e -m PEM > my_new_pem_file

And I am getting my public key in PEM format in testCheckPEM file, I am updating this key in database and with the help of this public key i am trying to get encryped text, which i will use to decrypt with private key but that is next part) here is my code for encryption.
I am reading public key from database successfully and calling this function:

module.exports.encryptStringWithRsaPublicKey = (text, publicKey) => new Promise((resolve, reject) => {
try {
const buffer = new Buffer(text);
const options = { key: publicKey, padding: constants.RSA_PKCS1_PADDING };
const encrypted = crypto.publicEncrypt(options, buffer).toString('base64');
return resolve(encrypted);
} catch (ex) {
return reject(ex);
}
});

but always I am getting error 'no start line'
Error: error:0906D06C:PEM routines:PEM_read_bio:no start line

What is wrong here? Any help will be appreciated.

here is my public key in ssh-keygen format:
ssh-rsa [MIKJ........JUIIK]

And here is my public key after PEM conversion :
-----BEGIN RSA PUBLIC KEY-----
[FRTYUH........HHK\HJKK]
-----END RSA PUBLIC KEY-----

from node-telegram-bot-api.

Thanks @pedrostc, that worked for me.

from node-telegram-bot-api.

Added a note on this error in our docs!

from node-telegram-bot-api.