No More Posting New Topics!

If you have a question or an issue, please start a thread in our Github Discussions Forum.
This forum is closed for new threads/ topics.

Navigation

    Quasar Framework

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    [v1] Got Error 500 I Internal Server Error @deployment

    Framework
    3
    8
    1329
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F
      folami last edited by

      Successfully Built a SSR web app that runs well on my local machine but got Got Error 500 I Internal Server Error @deployment
      My steps:

      • run ‘quasar build -m ssr’ ---------successful
      • npm install --------successful
      • upload to heroku--------successful
        but I still got Error 500 I Internal Server Error
        I dont know if there is anything else I need to do ?
      1 Reply Last reply Reply Quote 0
      • wcomnisky
        wcomnisky last edited by

        Could you please provide some logs?

        How are you serving your app?

        Have you checked the following link?
        https://v1.quasar-framework.org/quasar-cli/developing-ssr/deploying#Introduction

        F 1 Reply Last reply Reply Quote 0
        • F
          folami last edited by

          if run npm start in the dist folder on my local machine…i will get an app running on port 3000 with no error
          works fine
          on hosting the app i get no error on log console either but when opened give Error 500 I Internal Server Error

          1 Reply Last reply Reply Quote 0
          • F
            folami @wcomnisky last edited by

            @wcomnisky I got this log from Heroku log console:

             at=info method=GET path="/" host=ineed4u.herokuapp.com request_id=fd9c5698-9ce9-4f7d-b05c-eceea64682d5 fwd="105.112.112.214" dyno=web.1 connect=1ms service=165ms status=500 bytes=337 protocol=https
            
            wcomnisky 1 Reply Last reply Reply Quote 0
            • wcomnisky
              wcomnisky @folami last edited by

              @folami Not much helpful logline

              Try to get a bigger stack trace with:
              heroku logs -n 200

              Also check this: heroku logs -n 200

              F 2 Replies Last reply Reply Quote 0
              • F
                folami @wcomnisky last edited by folami

                @wcomnisky
                this from heroku log view

                2019-04-30T10:38:32.000000+00:00 app[api]: Build started by user ineedng2017@gmail.com
                2019-04-30T10:39:09.999288+00:00 app[api]: Release v28 created by user ineedng2017@gmail.com
                2019-04-30T10:39:09.999288+00:00 app[api]: Deploy cd309f27 by user ineedng2017@gmail.com
                2019-04-30T10:39:10.611658+00:00 heroku[web.1]: Restarting
                2019-04-30T10:39:10.614679+00:00 heroku[web.1]: State changed from up to starting
                2019-04-30T10:39:11.485757+00:00 heroku[web.1]: Stopping all processes with SIGTERM
                2019-04-30T10:39:11.597512+00:00 heroku[web.1]: Process exited with status 143
                2019-04-30T10:39:12.000000+00:00 app[api]: Build succeeded
                2019-04-30T10:39:15.886585+00:00 heroku[web.1]: Starting process with command `npm start`
                2019-04-30T10:39:18.221699+00:00 app[web.1]: 
                2019-04-30T10:39:18.221719+00:00 app[web.1]: > ineed@0.0.1 start /app
                2019-04-30T10:39:18.221721+00:00 app[web.1]: > node index.js
                2019-04-30T10:39:18.221723+00:00 app[web.1]: 
                2019-04-30T10:39:19.177739+00:00 heroku[web.1]: State changed from starting to up
                2019-04-30T10:39:19.149569+00:00 app[web.1]: Server listening at port 45919
                2019-04-30T10:39:19.230825+00:00 app[web.1]: connection succesful
                2019-04-30T11:02:37.237526+00:00 heroku[web.1]: State changed from starting to up
                

                and the log view shows this when I try to view the app @https://ineed4u.herokuapp.com/:

                2019-04-30T10:34:04.052697+00:00 heroku[router]: at=info method=GET path="/" host=ineeds.herokuapp.com request_id=e9cbbbdf-ad64-4c17-ac08-767e2c9a8223 fwd="105.112.112.214" dyno=web.1 connect=1ms service=22ms status=404 bytes=442 protocol=https
                2019-04-30T10:34:05.006946+00:00 heroku[router]: at=info method=GET path="/favicon.ico" host=ineeds.herokuapp.com request_id=f3b9f550-ad61-473c-8859-cb2cf92cb0cf fwd="105.112.112.214" dyno=web.1 connect=1ms service=6ms status=404 bytes=452 protocol=https
                
                1 Reply Last reply Reply Quote 0
                • F
                  folami @wcomnisky last edited by

                  @wcomnisky thanks for your response i got it fixed…it was one of my boot files that caused the error

                  1 Reply Last reply Reply Quote 0
                  • asceta hedonista
                    asceta hedonista last edited by

                    I have right now exactly the same issue, so I try a test.

                    1.- I create a new quasar project: quasar create heroku_test
                    2.- I buil it with: quasar buil -m ssr
                    3.- I add a Procfile with the text: web: node dist/ssr/index.js
                    4.- I run the command on local and localhost:3000/ works fine
                    5.- I even remove the dist directory from .gitignore

                    When I do the push to heroku everithing works fine, but when open the page it’s only displays: “500 | Internal Server Error”

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post