Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Email quickstart resulting in error 534-5.7.14

See original GitHub issue

Turned on Google auth, deployed app: https://functionstest-c1518.firebaseapp.com/

When logging in, I get the following error in the Function log:

Error: Invalid login: 534-5.7.14 <https://accounts.google.com/signin/continue?sarp=1&scc=1&plt=AKgnsbs7
534-5.7.14 UF7mumzUwFIZrMDWiiimSdrlEvZIp8kRC3QRkzqwfOM94wkvVFys_Yjllj6KGuBubi6SwF
534-5.7.14 BDIHCpQgETRmmgkyJXfYN4Ne3uG3tnsVJk7oGR4Z5fvgeIkuOJOKkvRA8cLWFN67ya4r28
534-5.7.14 u-eBDds9bTTh1poYtxXWk1x80iaSn_2VlJHWJnB0Yql6r_-A2lDE8nt00lWP7eoUpkzVih
534-5.7.14 x1DeI0bGyNqNHRRUuucw0k95Ph-CY> Please log in via your web browser and
534-5.7.14 then try again.
534-5.7.14  Learn more at
534 5.7.14  https://support.google.com/mail/answer/78754 100sm8943270iot.39 - gsmtp
    at SMTPConnection._formatError (/user_code/node_modules/nodemailer/node_modules/smtp-connection/lib/smtp-connection.js:528:15)
    at SMTPConnection._actionAUTHComplete (/user_code/node_modules/nodemailer/node_modules/smtp-connection/lib/smtp-connection.js:1231:30)
    at SMTPConnection.<anonymous> (/user_code/node_modules/nodemailer/node_modules/smtp-connection/lib/smtp-connection.js:319:22)
    at SMTPConnection._processResponse (/user_code/node_modules/nodemailer/node_modules/smtp-connection/lib/smtp-connection.js:669:16)
    at SMTPConnection._onData (/user_code/node_modules/nodemailer/node_modules/smtp-connection/lib/smtp-connection.js:493:10)
    at emitOne (events.js:96:13)
    at TLSSocket.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:176:18)
    at TLSSocket.Readable.push (_stream_readable.js:134:10)
    at TLSWrap.onread (net.js:548:20)

Issue Analytics

State:
Created 7 years ago
Comments:6 (4 by maintainers)

Top GitHub Comments

1reaction

markgohocommented, Mar 14, 2017

From the support article in the error code, I enabled access for less secure apps here: https://www.google.com/settings/security/lesssecureapps and also allowed access to DisplayUnlockCaptcha here: https://accounts.google.com/DisplayUnlockCaptcha

Welcome and Bye emails are both working now!

0reactions

carlosdelamoracommented, Aug 14, 2018

I have already enabled both // 1. https://www.google.com/settings/security/lesssecureapps // 2. https://accounts.google.com/DisplayUnlockCaptcha and everything works just fine but after a few hours I start getting an error: “Invalid login: 534-5.7.14 <https://accounts.google.com/signin/continue?sarp=1&scc=1&plt=AKgnsbvz” then I have to enable https://accounts.google.com/DisplayUnlockCaptcha again. Is there any way to prevent doing this manually every few hours.

Top Results From Across the Web

how to fix "send-mail: Authorization failed 534 5.7.14 "

Go to https://support.google.com/accounts/answer/6009563 (Titled: "Password incorrect error"). This page says "There are several reasons why you might see a “ ...

Invalid login: 534-5.7.9 Application-specific password required.

If you are receiving this error, it indicates that you have 2 factor authentication enabled under the inbox you are attempting to connect,...

Resolve errors | Gmail - Google Developers

This guide provides instructions on how to resolve specific API errors. Resolve a 400 error: Bad request. This error might result from these...

SMTP authentication error 534- Quick Fix!! - Bobcares

The SMTP authentication error 534 occurs when Google blocks the sign-in attempts from some insecure applications or devices.

Error testing Zap: You can only send emails to yourself when ...

The error indicates that when testing you can only send emails to your Zapier account email address. Better to use an email address...