Error at signup about socify HOT 11 OPEN

@Delano83 Have you run your migrations on heroku? And also can you post in the complete stack trace for this?

from socify.

@sudharti For db migrations, I ran:

heroku run rake db:migrate

Here is the complete stack trace of the error:

2017-01-13T02:02:32.525572+00:00 app[api]: Starting process with command bundle exec rake db:migrate by user ###
2017-01-13T02:02:37.346604+00:00 heroku[run.2184]: Starting process with command bundle exec rake db:migrate
2017-01-13T02:02:37.595872+00:00 heroku[run.2184]: State changed from starting to up
2017-01-13T02:02:37.314586+00:00 heroku[run.2184]: Awaiting client
2017-01-13T02:02:45.655472+00:00 heroku[run.2184]: Process exited with status 0
2017-01-13T02:02:45.682708+00:00 heroku[run.2184]: State changed from up to complete
2017-01-13T02:22:31.185396+00:00 app[api]: Release v12 created by user ###
2017-01-13T02:22:31.185396+00:00 app[api]: Set LOG_LEVEL config vars by user ###
2017-01-13T02:22:31.434796+00:00 heroku[web.1]: Restarting
2017-01-13T02:22:31.435470+00:00 heroku[web.1]: State changed from up to starting
2017-01-13T02:22:32.098521+00:00 app[web.1]: [2017-01-13 02:22:32] FATAL SignalException: SIGTERM
2017-01-13T02:22:32.098533+00:00 app[web.1]: /app/vendor/ruby-2.3.1/lib/ruby/2.3.0/webrick/server.rb:177:in select' 2017-01-13T02:22:32.098535+00:00 app[web.1]: /app/vendor/ruby-2.3.1/lib/ruby/2.3.0/webrick/server.rb:177:in block in start'
2017-01-13T02:22:32.098536+00:00 app[web.1]: /app/vendor/ruby-2.3.1/lib/ruby/2.3.0/webrick/server.rb:33:in start' 2017-01-13T02:22:32.098537+00:00 app[web.1]: /app/vendor/ruby-2.3.1/lib/ruby/2.3.0/webrick/server.rb:164:in start'
2017-01-13T02:22:32.098537+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.1/lib/rack/handler/webrick.rb:34:in run' 2017-01-13T02:22:32.098538+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/rack-2.0.1/lib/rack/server.rb:296:in start'
2017-01-13T02:22:32.098539+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/railties-5.0.0/lib/rails/commands/server.rb:79:in start' 2017-01-13T02:22:32.098540+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/railties-5.0.0/lib/rails/commands/commands_tasks.rb:90:in block in server'
2017-01-13T02:22:32.098541+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/railties-5.0.0/lib/rails/commands/commands_tasks.rb:85:in tap' 2017-01-13T02:22:32.098542+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/railties-5.0.0/lib/rails/commands/commands_tasks.rb:85:in server'
2017-01-13T02:22:32.098542+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/railties-5.0.0/lib/rails/commands/commands_tasks.rb:49:in run_command!' 2017-01-13T02:22:32.098543+00:00 app[web.1]: /app/vendor/bundle/ruby/2.3.0/gems/railties-5.0.0/lib/rails/commands.rb:18:in <top (required)>'
2017-01-13T02:22:32.098544+00:00 app[web.1]: bin/rails:8:in require' 2017-01-13T02:22:32.098545+00:00 app[web.1]: bin/rails:8:in

Welcome [email protected]!

You can confirm your account email through the link below:

Confirm my account

from socify.

@Delano83 From your log I can see that the SMTP authorization fails. This part below:

2017-01-13T02:38:11.249125+00:00 app[web.1]:
2017-01-13T02:38:11.250008+00:00 app[web.1]: Completed 500 Internal Server Error in 730ms (ActiveRecord: 8.5ms)
2017-01-13T02:38:11.253890+00:00 app[web.1]:
2017-01-13T02:38:11.253915+00:00 app[web.1]: Net::SMTPAuthenticationError (535 Authentication failed: The provided authorization grant is invalid, expired, or revoked

from socify.

Thanks @sudharti!
This is what I have for smtp configuration:
config.active_record.dump_schema_after_migration = false

config.action_mailer.default_url_options = { host: 'http://myapp.herokuapp.com' }

ActionMailer::Base.delivery_method = :smtp
ActionMailer::Base.perform_deliveries = true

ActionMailer::Base.smtp_settings = {
:address => 'smtp.sendgrid.net',
:port => '587',
:authentication => :plain,
:user_name => ENV['SENDGRID_USERNAME'],
:password => ENV['SENDGRID_PASSWORD'],
:domain => 'heroku.com',
:enable_starttls_auto => true
}

For my Config Vars in Heroku, I have 'apikey' for username and my key for the password. Does it sound right to you?

from socify.

@Delano83 No I think for sendgrid it's just the username and password of your account. That's what I have set. Just checked my heroku config.

from socify.

@Delano83 Were you able to resolve it?

from socify.

@sudharti Not quite yet...I put my Sendgrid username and password but still get SMTP error. Did you have to do any extra configuration on Sendgrid apart from setting up an SMTP Api Key?

from socify.

@Delano83 Try printing the ENV variable in Log to test if you are able to get the correct values. If that's not the issue then your account might not have been provisioned yet. Check this https://twitter.com/ryandeussing/status/260363641533108225?lang=en

from socify.

@sudharti The authentification is set to 'plain' and the const variables are correctly printed in the console... How long does it take for your account to be provisioned since I just created my account?
I now get a different error:

ArgumentError (SMTP-AUTH requested but missing user name)

Something to do with a missing username?

from socify.

@Delano83 Make sure that the username is not your email id. Because I have set the same and it seems to work. Either that or problem with heroku provisioning 🤔

from socify.

@scaffeinate Still getting the error even afer checking with SendGrid for provisioning... Hopefully it's an isolated issue and we can close this thread.

from socify.