Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No backend match. Environment variables missing for: aws.js, mega.js #8

Open
enlighter opened this issue May 5, 2016 · 2 comments
Open

Comments

@enlighter
Copy link

enlighter commented May 5, 2016

After I deploy the current master at Heroku free Dyno, App page shows this:
Application Error An error occurred in the application and your page could not be served. Please try again in a few moments. If you are the application owner, check your logs for details.

And this is the output of heroku logs:
2016-05-05T01:18:00.616224+00:00 heroku[api]: Release v2 created by [email protected] 2016-05-05T01:18:00.616224+00:00 heroku[api]: Enable Logplex by [email protected] 2016-05-05T01:19:24.496990+00:00 heroku[api]: Deploy 35c516f by [email protected] 2016-05-05T01:19:24.496990+00:00 heroku[api]: Release v3 created by [email protected] 2016-05-05T01:19:24.496245+00:00 heroku[api]: Scale to web=1 by [email protected] 2016-05-05T01:19:24.962341+00:00 heroku[slug-compiler]: Slug compilation started 2016-05-05T01:19:24.962346+00:00 heroku[slug-compiler]: Slug compilation finished 2016-05-05T01:19:26.916202+00:00 heroku[web.1]: Starting process with commandnode server.js 2016-05-05T01:19:30.554267+00:00 app[web.1]: No backend match. Environment variables missing for: aws.js, mega.js 2016-05-05T01:19:31.638131+00:00 heroku[web.1]: State changed from starting to crashed 2016-05-05T01:19:31.639385+00:00 heroku[web.1]: State changed from crashed to starting 2016-05-05T01:19:31.630398+00:00 heroku[web.1]: Process exited with status 1 2016-05-05T01:19:33.047734+00:00 heroku[web.1]: Starting process with commandnode server.js2016-05-05T01:19:35.259335+00:00 app[web.1]: No backend match. Environment variables missing for: aws.js, mega.js 2016-05-05T01:19:35.968360+00:00 heroku[web.1]: Process exited with status 1 2016-05-05T01:19:35.948261+00:00 heroku[web.1]: State changed from starting to crashed 2016-05-05T01:20:02.174098+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=powerful-woodland-25592.herokuapp.com request_id=d74de48d-8a97-4fc1-b056-c3f806ed09f3 fwd="203.110.242.20" dyno= connect= service= status=503 bytes= 2016-05-05T01:20:03.829016+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=powerful-woodland-25592.herokuapp.com request_id=1a1d3e25-3b7e-45ff-aed5-58a050ebaa06 fwd="203.110.242.20" dyno= connect= service= status=503 bytes= 2016-05-05T01:20:04.873119+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=powerful-woodland-25592.herokuapp.com request_id=2c04d26b-95c0-43fa-9f3f-61fe97f0f478 fwd="203.110.242.20" dyno= connect= service= status=503 bytes=
How to solve this?

@enlighter
Copy link
Author

Focused:
2016-05-05T01:19:33.047734+00:00 heroku[web.1]: Starting process with commandnode server.js2016-05-05T01:19:35.259335+00:00 app[web.1]: No backend match. Environment variables missing for: aws.js, mega.js 2016-05-05T01:19:35.968360+00:00 heroku[web.1]: Process exited with status 1 2016-05-05T01:19:35.948261+00:00 heroku[web.1]: State changed from starting to crashed

@electron0zero
Copy link

you have to set env variables for AWS or Mega while deploying, after deployment if you want to change those go to app>>settings>>revel config vars >> add mega credentials or AWS credentials.
it is all already mentioned in readme

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants