Submitting login form produces intermittent silent crash

[huevoncito]

This is a strange bug.

I'm running the latest version of Meteor on Ubuntu 16.04 with Phusion Passenger.

The app has been crashing periodically for no obvious reason, and the error log is blank. One thing I've noticed is that logging in using > atLoginForm sometimes triggers this silent crash, and refreshing the window after the app restarts causes the app to crash again, presumably because the resume token is missing or incorrect on account of the crash.

I've rebuilt bcrypt on the server but that hasn't solved the problem.

Ideas? I'm stumped.

Thanks!
Danel

[Wecoboss]

I have the same problem and I can't debug it as there is no information about the crash.

Any update?

[elie222]

I think we have a similar issue.

The buttons on screen just go gray for me.

I see Accounts.loggingIn() is true and never becomes false.

I also see that localstorage is not updated with the login credentials although the server did return the token to the client so the login was successful on the server.

[elie222]

Upon further investigation I see that my issue is with Meteor itself. Running:

Meteor.loginWithPassword({email: 'email@email.com'}, 'password', function(error,res) { error ? console.error(error) : console.log(res) })

I don't get anything logged to the console, but using Meteor Chrome extension I see that my token was returned from the server.

[huevoncito]

I'm pretty sure it's actually a BCRYPT error. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

…

On July 12, 2018 8:14 AM, Elie ***@***.***> wrote: Upon further investigation I see that my issue is with Meteor itself. Running: Meteor . loginWithPassword ({email : ' ***@***.*** ' }, ' password ' , function ( error , res ) { error ? console . error (error) : console . log (res) }) I don't get anything logged to the console, but using Meteor Chrome extension I see that my token was returned from the server. — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub](#758 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AEFcgWF1KuzCYmvEynMIh5DzKR_ZLxkIks5uFz25gaJpZM4TMu4J).

[elie222]

On the server? But I see the login token returned to the client. We may be experiencing different issues. On Thu, 12 Jul 2018, 21:48 Daniel Bernhard, <notifications@github.com> wrote:

…

I'm pretty sure it's actually a BCRYPT error. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On July 12, 2018 8:14 AM, Elie ***@***.***> wrote: > Upon further investigation I see that my issue is with Meteor itself. Running: > > Meteor > > . > > loginWithPassword > > ({email > > : > > ' > > ***@***.*** > > ' > > }, > > ' > > password > > ' > > , > > function > > ( > > error > > , > > res > > ) { error > > ? > > console > > . > > error > > (error) > > : > > console > > . > > log > > (res) }) > > I don't get anything logged to the console, but using Meteor Chrome extension I see that my token was returned from the server. > > — > You are receiving this because you authored the thread. > Reply to this email directly, [view it on GitHub]( #758 (comment)), or [mute the thread]( https://github.com/notifications/unsubscribe-auth/AEFcgWF1KuzCYmvEynMIh5DzKR_ZLxkIks5uFz25gaJpZM4TMu4J). — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#758 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AC8oX5L9OzVluT-uzwNTffNiGaBR_pGhks5uF5oMgaJpZM4TMu4J> .

[huevoncito]

For me it was a silent error. When the server restarted, I was logged in. Downgrading to Node 8.9.4 solved the problem for me. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

…

On July 12, 2018 4:59 PM, Elie ***@***.***> wrote: On the server? But I see the login token returned to the client. We may be experiencing different issues. On Thu, 12 Jul 2018, 21:48 Daniel Bernhard, ***@***.***> wrote: > I'm pretty sure it's actually a BCRYPT error. > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On July 12, 2018 8:14 AM, Elie ***@***.***> wrote: > > > Upon further investigation I see that my issue is with Meteor itself. > Running: > > > > Meteor > > > > . > > > > loginWithPassword > > > > ({email > > > > : > > > > ' > > > > ***@***.*** > > > > ' > > > > }, > > > > ' > > > > password > > > > ' > > > > , > > > > function > > > > ( > > > > error > > > > , > > > > res > > > > ) { error > > > > ? > > > > console > > > > . > > > > error > > > > (error) > > > > : > > > > console > > > > . > > > > log > > > > (res) }) > > > > I don't get anything logged to the console, but using Meteor Chrome > extension I see that my token was returned from the server. > > > > — > > You are receiving this because you authored the thread. > > Reply to this email directly, [view it on GitHub]( > #758 (comment)), > or [mute the thread]( > https://github.com/notifications/unsubscribe-auth/AEFcgWF1KuzCYmvEynMIh5DzKR_ZLxkIks5uFz25gaJpZM4TMu4J). > > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#758 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AC8oX5L9OzVluT-uzwNTffNiGaBR_pGhks5uF5oMgaJpZM4TMu4J> > . > — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub](#758 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AEFcgXMRYIVF7IzsoerpbJbYK3VKWGLnks5uF7iVgaJpZM4TMu4J).