Syntax error when start $ heroku open

heroku application error 503
internal server error heroku node
heroku error code=h10
heroku build succeeded but application error
heroku internal server error
heroku logs
application error heroku node
heroku login

I am new to Heroku and I am trying to deploy my first app onto Heroku. I followed instruction, which were:

  1. git init, add and commit my app's source code.
  2. heroku create to create Heroku remote repo for my app.
  3. git push heroku master to push my app's source code to heroku
  4. heroku open

Problem happened when I tried to run heroku open, which was:

$ heroku open
(node:6192) SyntaxError Plugin: 
heroku:C:\Users\hauph\AppData\Local\heroku\conf                                                                                    
ig.json: Unexpected string in JSON at position 72 module: 
@oclif/config@1.6.33
task: runHook prerun
plugin: heroku
root: C:\Program Files\heroku\client
See more details with DEBUG=*

Image taken from that error

I checked file config.json at the direction as addressed above, and it was:

{
  "schema": 1,
  "install": "554c101b-d4de-496c-9768-710142ebfb20"
}
 "skipAnalytics": false
}

So what did I do wrong here?

I would be grateful for any help.

Thank you very much!

Your config.json contains invalid JSON (note the two closing brackets). Reinstall the Heroku CLI, and you should be in good shape.

Error Pages, Other errors, such as application errors (a 404 or 500), will display your application's error from starting to crashed 2011-03-01T16:16:59-08:00 heroku[​router]: at=error In this example, the router tried to serve a page for the app, but the web process is crashed. heroku maintenance:on $ heroku open. Teams. Q&A for Work. Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information.

I had the same problem. Not sure why it ends up corrupted, but the config.json should look like the following (get rid of the curly brace before skipAnalytics):

{
  "schema": 1,
  "install": "3265b92a-27f4-4adb-9c07-75d9213f0000",
  "skipAnalytics": false
}

Troubleshooting Node.js Deploys, Start with these simple steps to troubleshoot a build issue. As an example, you might wish to exclude a lib directory at the root of your If none of these solutions work for you, open a ticket with Heroku so we can help. This is a bug report. What is the current behavior? update heroku cli to any version between 7.0.36 and 7.0.37 (from apt-get or snap package) try run heroku. sudo DEBUG=* heroku update or sudo DEBUG=* heroku output: fabio@luzfcb:~$ sudo

    USAGE
  $ heroku apps:open [PATH]

OPTIONS
  -a, --app=app        (required) app to run command against
  -r, --remote=remote  git remote of app to use

EXAMPLES
  $ heroku open -a myapp
  # opens https://myapp.herokuapp.com

  $ heroku open -a myapp /foo
  # opens https://myapp.herokuapp.com/foo

Please visit heroku cli commands documentation here https://devcenter.heroku.com/articles/heroku-cli-commands

Why am I seeing "Application Error"? - Heroku Help, .com/addons#logging to make sure that your historical log data is being saved. If you are on a windows machine, you should download heroku and save the folder in your directory. E.g if your app name is My-app, you should save the heroku folder by clicking on the browser section to select where you wanna save the folder (My-app) during installation.

The Heroku CLI, . You'll be prompted to enter any key to go to your web browser to complete login. The CLI will then log you in automatically. Specify your start script. Simply create a Procfile (without any file extension) and add; web: node index.js Heroku first looks for this Procfile. If none is found, Heroku will attempt to start a default web process via the start script in your package.json. Start your app locally using the heroku local command to be sure everything works fine

Six Strategies for Deploying to Heroku, then automatically builds your application and creates a new release. $ heroku apps:rename heroku-node-8080 --app calm-reaches-6216. Edit: This tutorial has since changed the name of the Heroku instance to heroku-node-scotch. You can also bypass all this by naming your application from the start: $ heroku create heroku-node-scotch. Deploying Code. Now that we have everything in order, go ahead and push to Heroku!

Heroku CLI Commands, open an add-on's Dev Center documentation in your browser create a staging app $ heroku apps:create example-staging --remote USAGE $ heroku apps:​errors OPTIONS -a, --app=app (required) app to run command  When your app is crashed, out of resources, or misbehaving in some other way, Heroku serves an error page, which can be customized for each application.

Comments
  • I reinstalled the whole heroku and it works! Thank you very much
  • Have you tried reinstalling the Heroku CLI? Because I did it and it solved my problem, like @AdamMcrea 's answer