Meteor-Community-Packages / Meteor-Community-Packages/raix-push
getting error when I send push notifications from production (Error: error:0906D06C:PEM routines:PEM_read_bio:no start line)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 505
- Forks
- 191
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Everytime I send a push notification on production I get this error in the logs and I am not sure what is causing it, any help will be appreciated
/bundle/bundle/programs/server/npm/node_modules/meteor/raix_push/node_modules/apn/node_modules/q/q.js:155
throw e;
[xxx.xxx.xxx.xxx](ip address) ^
Error: error:0906D06C:PEM routines:PEM_read_bio:no start line
at Object.exports.createCredentials (crypto.js:126:17)
at Object.exports.connect (tls.js:1345:27)
at apnSocketLegacy (/bundle/bundle/programs/server/npm/node_modules/meteor/raix_push/node_modules/apn/lib/socket.js:40:19)
at Connection.initialize.spread.fail.terminated (/bundle/bundle/programs/server/npm/node_modules/meteor/raix_push/node_modules/apn/lib/connection.js:175:17)
at /bundle/bundle/programs/server/npm/node_modules/meteor/raix_push/node_modules/apn/node_modules/q/q.js:1229:26
at _fulfilled (/bundle/bundle/programs/server/npm/node_modules/meteor/raix_push/node_modules/apn/node_modules/q/q.js:834:54)
at self.promiseDispatch.done (/bundle/bundle/programs/server/npm/node_modules/meteor/raix_push/node_modules/apn/node_modules/q/q.js:863:30)
at Promise.promise.promiseDispatch (/bundle/bundle/programs/server/npm/node_modules/meteor/raix_push/node_modules/apn/node_modules/q/q.js:796:13)
at /bundle/bundle/programs/server/npm/node_modules/meteor/raix_push/node_modules/apn/node_modules/q/q.js:556:49
at runSingle (/bundle/bundle/programs/server/npm/node_modules/meteor/raix_push/node_modules/apn/node_modules/q/q.js:137:13)
at flush (/bundle/bundle/programs/server/npm/node_modules/meteor/raix_push/node_modules/apn/node_modules/q/q.js:125:13)
at process._tickCallback (node.js:458:13)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the apn/lib/socket.js and apn/lib/connection.js entry points named in the stack trace, then follow the crypto.js and tls.js calls that reach createCredentials. Reproduce the production configuration path and identify which PEM input causes the failure; done means push notifications connect successfully without the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100