Heroku App crashes error H10 but build succeeds [duplicate] - heroku

This question already has answers here:
error cannot import name 'cached_property' from 'werkzeug' when importing [ `from werkzeug.utils import cached_property` ]
(1 answer)
Python3 'Cannot import name 'cached_property'
(6 answers)
Closed 4 months ago.
Hi been looking for a solution for this for hours, need a fresh set of eyes. When deploying my app to heroku the logs have it crashing showing that a worker failed to boot and an import error shortly before that.
Now the current import error is from werkzueg but before I updated flask I was getting an import error from Jninja for 'escape'.
I've also seen that an improper procfile may cause this but I'm pretty sure my procfile is correct.
I'm not setting any ports in either my front/backend and have set the endpoint on the frontend to the url heroku gives me for the build with my specified endpoint.
tldr I don't know what is causing this error
Link to the github for more detailed code https://github.com/Jmumford45/Heart_Prediction_ML
directory outline
app.py is inside Backend
Procfile: web: gunicorn --chdir Backend app:app
error msg:
2022-10-28T23:58:23.563836+00:00 app[web.1]: from werkzeug import cached_property
2022-10-28T23:58:23.563836+00:00 app[web.1]: ImportError: cannot import name 'cached_property' from 'werkzeug' (/app/.heroku/python/lib/python3.10/site-packages/werkzeug/__init__.py)
2022-10-28T23:58:23.563946+00:00 app[web.1]: [2022-10-28 23:58:23 +0000] [9] [INFO] Worker exiting (pid: 9)
2022-10-28T23:58:24.168158+00:00 heroku[web.1]: Process exited with status 3
2022-10-28T23:58:24.234294+00:00 heroku[web.1]: State changed from up to crashed
2022-10-28T23:58:23.897642+00:00 app[web.1]: [2022-10-28 23:58:23 +0000] [4] [WARNING] Worker with pid 9 was terminated due to signal 15
2022-10-28T23:58:23.995629+00:00 app[web.1]: [2022-10-28 23:58:23 +0000] [4] [INFO] Shutting down: Master
2022-10-28T23:58:23.995660+00:00 app[web.1]: [2022-10-28 23:58:23 +0000] [4] [INFO] Reason: Worker failed to boot.
2022-10-28T23:58:47.000000+00:00 app[api]: Build succeeded
2022-10-28T23:58:54.059490+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=heartprediction-app.herokuapp.com request_id=ef722647-4325-4aae-8385-b0ba969c3aa7 fwd="72.111.98.148" dyno= connect= service= status=503 bytes= protocol=https
2022-10-28T23:58:53.791791+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=heartprediction-app.herokuapp.com request_id=fde1ae30-50f0-46d3-b27c-6cd2494ad4d5 fwd="72.111.98.148" dyno= connect= service= status=503 bytes= protocol=https

Related

Heroku deployment with nest js project

I have github account which is connnected with my heroku account. I am trying to deploy code through heroku and my project is also connected with heroku pipeline. Build is getting succeeded. But getting error while accessing app
Heroku logs
2022-09-07T10:08:37.346556+00:00 heroku[web.1]: Starting process with command `npm start`
2022-09-07T10:08:41.005367+00:00 app[web.1]:
2022-09-07T10:08:41.005458+00:00 app[web.1]: > food-court#0.0.1 start
2022-09-07T10:08:41.005458+00:00 app[web.1]: > nest start
2022-09-07T10:08:41.005459+00:00 app[web.1]:
2022-09-07T10:08:41.020373+00:00 app[web.1]: /tmp/start-7b018378.sh: 1: nest: not found
2022-09-07T10:08:41.187916+00:00 heroku[web.1]: Process exited with status 127
2022-09-07T10:08:41.284101+00:00 heroku[web.1]: State changed from starting to crashed
2022-09-07T10:13:07.218759+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=food-court-be-dev.herokuapp.com request_id=52c79661-a554-4c2b-b412-c24429d538c5 fwd="103.181.100.29" dyno= connect= service= status=503 bytes= protocol=https
2022-09-07T10:13:07.784604+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=food-court-be-dev.herokuapp.com request_id=f1a47ec4-6160-47d2-80ef-a0db2569d7bf fwd="103.181.100.29" dyno= connect= service= status=503 bytes= protocol=https
Thanks in advance
resolved issue by changing "start": "nest start", to "start": "node dist/main.js" in package.json

Why Heroku + voila ipynb app fail to deploy with `failed to bind to $PORT within 60 seconds of launch`

I followed the different pages to deploy a voila ipynb app on heroku:
https://pythonforundergradengineers.com/deploy-jupyter-notebook-voila-heroku.html
https://medium.com/analytics-vidhya/deploying-jupyter-notebook-as-a-web-app-with-heroku-d157b68bcccc
https://github.com/voila-dashboards/voila-heroku
Unfoprtunately, it seems that there is a persisting bug this last month (saw here for instance https://forums.fast.ai/t/heroku-app-wont-deploy/92875/4)
You can find the github repo I am trying to deploy here:
https://github.com/vpicouet/fireball2-etc
The app is base on this Procfile
web: voila --port=$PORT --no-browser --enable_nbextensions=True notebooks/ETC.ipynb
Unfortunately I get this error
2022-03-27T15:17:49.880973+00:00 app[web.1]: [Voila] Using /tmp to store connection files
2022-03-27T15:17:49.881302+00:00 app[web.1]: [Voila] Storing connection files in /tmp/voila_yih2j7ic.
2022-03-27T15:17:49.881356+00:00 app[web.1]: [Voila] Serving static files from /app/.heroku/python/lib/python3.8/site-packages/voila/static.
2022-03-27T15:17:49.890735+00:00 app[web.1]: [Voila] Voilà is running at:
2022-03-27T15:17:49.890737+00:00 app[web.1]: http://localhost:7758/
2022-03-27T15:17:58.000000+00:00 app[api]: Build succeeded
2022-03-27T15:18:48.015586+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2022-03-27T15:18:48.055996+00:00 heroku[web.1]: Stopping process with SIGKILL
2022-03-27T15:18:48.227953+00:00 heroku[web.1]: Process exited with status 137
2022-03-27T15:18:48.274554+00:00 heroku[web.1]: State changed from starting to crashed
2022-03-27T15:24:44.773897+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fireball2-etc-2022.herokuapp.com request_id=0b0c1707-d6ae-449a-9059-f2d1d3f8c652 fwd="74.105.154.225" dyno= connect= service= status=503 bytes= protocol=https
2022-03-27T15:39:30.626492+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=fireball2-etc-2022.herokuapp.com request_id=af5c3e4a-019f-47c3-a047-e5115ebd5fc7 fwd="74.105.154.225" dyno= connect= service= status=503 bytes= protocol=https
Do you know fow to solve this?
Thanks a lot!
I already tried some ideas on the web:
change
web: voila --port=$PORT --no-browser --enable_nbextensions=True notebooks/ETC.ipynb
by
worker: voila --port=$PORT --no-browser --enable_nbextensions=True notebooks/ETC.ipynb
The answer can be found here: issue 1047
From 0.3.0, Voila will not listen on all interfaces by default (#926) for security reasons. In the case of Heroku, you need to add --Voila.ip=0.0.0.0 to your command in the Procfile to make it work.
See also: https://github.com/voila-dashboards/voila-heroku

heroku voila app error Process exited with status 1

I need some help deploying Voila app on Heroku. I'm using a free Heroku account.
The GitHub repository can be found here https://github.com/ostasis/One-dimensional-heroku
The notebook runs fine locally using Voila and runs on
Not sure if it helps but its currently at https://nameless-coast-24689.herokuapp.com/
heroku logs --tail
Shows the following
2020-06-28T05:51:24.602001+00:00 heroku[web.1]: State changed from crashed to starting
2020-06-28T05:51:36.982425+00:00 app[web.1]: Traceback (most recent call last):
2020-06-28T05:51:36.982443+00:00 app[web.1]: File "/app/.heroku/python/bin/voila", line 8, in <module>
2020-06-28T05:51:36.982603+00:00 app[web.1]: sys.exit(main())
2020-06-28T05:51:36.982619+00:00 app[web.1]: File "/app/.heroku/python/lib/python3.7/site-packages/traitlets/config/application.py", line 663, in launch_instance
2020-06-28T05:51:36.982943+00:00 app[web.1]: app.initialize(argv)
2020-06-28T05:51:36.982944+00:00 app[web.1]: File "/app/.heroku/python/lib/python3.7/site-packages/voila/app.py", line 342, in initialize
2020-06-28T05:51:36.983141+00:00 app[web.1]: raise ValueError('provided more than 1 argument: %r' % self.extra_args)
2020-06-28T05:51:36.983159+00:00 app[web.1]: ValueError: provided more than 1 argument: ['—-port=47763', 'one-dimensional-bin-packing.ipynb']
2020-06-28T05:51:37.090291+00:00 heroku[web.1]: Process exited with status 1
2020-06-28T05:51:37.569126+00:00 heroku[web.1]: State changed from starting to crashed
2020-06-28T05:51:51.000000+00:00 app[api]: Build succeeded
2020-06-28T05:53:26.592423+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=nameless-coast-24689.herokuapp.com request_id=8f3e8daa-5127-48cf-a1d0-c819a4e3a820 fwd="203.57.213.219" dyno= connect= service= status=503 bytes= protocol=https
2020-06-28T05:53:27.219010+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=nameless-coast-24689.herokuapp.com request_id=3587c11e-08bc-4d88-a715-43534a9e7169 fwd="203.57.213.219" dyno= connect= service= status=503 bytes= protocol=https
On mybinder.org I've used environment.yml below
name: python 3.7.4
channels:
- conda-forge
dependencies:
- python=3.7.4
- appmode=0.7.0
- pandas=0.25.1
- matplotlib=3.1.1
- pip=19.2.3
- pip:
- mip==1.8.2
and on Heruko I've have the following requirements.txt
appmode
matplotlib
mip
pandas
voila
Is there an issue with requirements.txt?
Procfile below
web: voila —-port=$PORT --no-browser one-dimensional-bin-packing.ipynb
runtime.txt below
python-3.7.6
I had the same problem. Managed to fix it by adding the --enable_nbextensions=True option to the voila command in Procfile, so it becomes in your case:
web: voila —-port=$PORT --no-browser --enable_nbextensions=True one-dimensional-bin-packing.ipynb
Found this fix in this example repo: https://github.com/voila-dashboards/voila-heroku

Module not found by Heroku despite being in the requirements

I deployed a Python Flask app on Heroku but it failed to build because not finding the specified module : flask which was in the requirements though. The error is :
ModuleNotFoundError: No module named 'flask'
I checked Raja Simon's answer and used the $pip freeze > requirements.txt command. It gave logs quite longer but with the similar error at the end.
Here are the logs :
(MyFlaskAppEnv) mike#mike-thinks:~/Programing/Rasa/myflaskapp$ heroku run pip freeze
2018-06-27T11:42:34.000000+00:00 app[api]: Build started by user antoine.compagnie#gmail.com
2018-06-27T11:43:13.411707+00:00 heroku[web.1]: Starting process with command `python app.py 21178`
2018-06-27T11:43:15.837860+00:00 heroku[web.1]: Process exited with status 1
2018-06-27T11:43:15.856692+00:00 heroku[web.1]: State changed from starting to crashed
2018-06-27T11:43:15.772353+00:00 app[web.1]: Traceback (most recent call last):
2018-06-27T11:43:15.772387+00:00 app[web.1]: File "app.py", line 1, in <module>
2018-06-27T11:43:15.772516+00:00 app[web.1]: from flask import Flask, render_template, flash, redirect, url_for, session, request, logging, jsonify
2018-06-27T11:43:15.772564+00:00 app[web.1]: ModuleNotFoundError: No module named 'flask'
2018-06-27T11:43:15.858551+00:00 heroku[web.1]: State changed from crashed to starting
2018-06-27T11:43:09.193489+00:00 app[api]: Deploy 25f77237 by user antoine.compagnie#gmail.com
2018-06-27T11:43:09.193489+00:00 app[api]: Release v4 created by user antoine.compagnie#gmail.com
2018-06-27T11:43:09.000000+00:00 app[api]: Build succeeded
2018-06-27T11:43:09.215426+00:00 app[api]: Scaled to web#1:Free by user antoine.compagnie#gmail.com
2018-06-27T11:43:21.161561+00:00 heroku[web.1]: Starting process with command `python app.py 59367`
2018-06-27T11:43:23.924087+00:00 heroku[web.1]: Process exited with status 1
2018-06-27T11:43:23.940890+00:00 heroku[web.1]: State changed from starting to crashed
2018-06-27T11:43:23.841663+00:00 app[web.1]: Traceback (most recent call last):
2018-06-27T11:43:23.841688+00:00 app[web.1]: File "app.py", line 1, in <module>
2018-06-27T11:43:23.841917+00:00 app[web.1]: from flask import Flask, render_template, flash, redirect, url_for, session, request, logging, jsonify
2018-06-27T11:43:23.841923+00:00 app[web.1]: ModuleNotFoundError: No module named 'flask'
2018-06-27T11:54:43.888837+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=rosenberg-moodbot.herokuapp.com request_id=e4428bfb-012c-43dc-a7b4-a67e257a7853 fwd="82.1.184.42" dyno= connect= service= status=503 bytes= protocol=https
2018-06-27T11:54:44.411389+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=rosenberg-moodbot.herokuapp.com request_id=936933c2-d48d-4106-8607-f5e2a45f430a fwd="82.1.184.42" dyno= connect= service= status=503 bytes= protocol=https
2018-06-27T11:54:44.411939+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=rosenberg-moodbot.herokuapp.com request_id=7f49a28a-778b-47aa-9205-92d56a56c73c fwd="82.1.184.42" dyno= connect= service= status=503 bytes= protocol=https
2018-06-27T11:55:07.458967+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=rosenberg-moodbot.herokuapp.com request_id=f2d7e020-b654-42da-83f3-631c8a116442 fwd="82.1.184.42" dyno= connect= service= status=503 bytes= protocol=https
2018-06-27T12:03:38.241868+00:00 heroku[web.1]: State changed from crashed to starting
2018-06-27T12:03:42.317464+00:00 heroku[web.1]: Starting process with command `python app.py 28610`
2018-06-27T12:03:44.695629+00:00 heroku[web.1]: Process exited with status 1
2018-06-27T12:03:44.625237+00:00 app[web.1]: Traceback (most recent call last):
2018-06-27T12:03:44.625272+00:00 app[web.1]: File "app.py", line 1, in <module>
2018-06-27T12:03:44.625441+00:00 app[web.1]: from flask import Flask, render_template, flash, redirect, url_for, session, request, logging, jsonify
2018-06-27T12:03:44.625492+00:00 app[web.1]: ModuleNotFoundError: No module named 'flask'
2018-06-27T12:03:44.791879+00:00 heroku[web.1]: State changed from starting to crashed
2018-06-27T12:09:07.960949+00:00 app[api]: Starting process with command `pip freeze` by user antoine.compagnie#gmail.com
2018-06-27T12:09:14.153229+00:00 heroku[run.8725]: State changed from up to complete
2018-06-27T12:09:14.083206+00:00 heroku[run.8725]: Awaiting client
2018-06-27T12:09:14.134697+00:00 heroku[run.8725]: State changed from starting to up
2018-06-27T12:09:14.121827+00:00 heroku[run.8725]: Error R13 (Attach error) -> Failed to attach to process
2018-06-27T12:09:14.127236+00:00 heroku[run.8725]: Process exited with status 128
2018-06-27T12:09:18.023627+00:00 app[api]: Starting process with command `pip freeze` by user antoine.compagnie#gmail.com
2018-06-27T12:09:22.543943+00:00 heroku[run.7995]: Awaiting client
2018-06-27T12:09:22.572262+00:00 heroku[run.7995]: Starting process with command `pip freeze`
2018-06-27T12:09:22.714123+00:00 heroku[run.7995]: State changed from starting to up
2018-06-27T12:09:27.866504+00:00 heroku[run.7995]: Process exited with status 0
2018-06-27T12:09:27.884656+00:00 heroku[run.7995]: State changed from up to complete
2018-06-27T12:10:47.411648+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=rosenberg-moodbot.herokuapp.com request_id=865fbea1-bf7b-43a7-82e1-aaa3be505e7b fwd="82.1.184.42" dyno= connect= service= status=503 bytes= protocol=https
2018-06-27T12:11:43.794922+00:00 heroku[run.1331]: Awaiting client
2018-06-27T12:11:43.833108+00:00 heroku[run.1331]: Starting process with command `pip freeze`
2018-06-27T12:11:43.925237+00:00 heroku[run.1331]: State changed from starting to up
2018-06-27T12:11:39.579643+00:00 app[api]: Starting process with command `pip freeze` by user antoine.compagnie#gmail.com
2018-06-27T12:11:48.939978+00:00 heroku[run.1331]: Process exited with status 0
2018-06-27T12:11:48.960226+00:00 heroku[run.1331]: State changed from up to complete
2018-06-27T12:12:30.000000+00:00 app[api]: Build started by user antoine.compagnie#gmail.com
2018-06-27T12:12:49.441456+00:00 app[api]: Deploy 55bbe098 by user antoine.compagnie#gmail.com
2018-06-27T12:12:49.441456+00:00 app[api]: Release v5 created by user antoine.compagnie#gmail.com
2018-06-27T12:12:49.910214+00:00 heroku[web.1]: State changed from crashed to starting
2018-06-27T12:12:49.000000+00:00 app[api]: Build succeeded
2018-06-27T12:12:53.359381+00:00 heroku[web.1]: Starting process with command `python app.py 21411`
2018-06-27T12:12:54.939693+00:00 heroku[web.1]: Process exited with status 1
2018-06-27T12:12:54.900467+00:00 app[web.1]: Traceback (most recent call last):
2018-06-27T12:12:54.900502+00:00 app[web.1]: File "app.py", line 1, in <module>
2018-06-27T12:12:54.900600+00:00 app[web.1]: from flask import Flask, render_template, flash, redirect, url_for, session, request, logging, jsonify
2018-06-27T12:12:54.900606+00:00 app[web.1]: ModuleNotFoundError: No module named 'flask'
2018-06-27T12:12:54.954666+00:00 heroku[web.1]: State changed from starting to crashed
2018-06-27T12:13:01.350585+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=rosenberg-moodbot.herokuapp.com request_id=8a3ae221-135d-4704-bfb3-92cf9339d766 fwd="82.1.184.42" dyno= connect= service= status=503 bytes= protocol=https
And here are my requirements.txt which includes flask==1.0.2
And here is the output of $heroku run pip freeze which shows flask doesn't seem to be part of it.
(MyFlaskAppEnv) mike#mike-thinks:~/Programing/Rasa/myflaskapp$ heroku run pip freeze
Running pip freeze on ⬢ rosenberg-moodbot... up, run.9642 (Free)
certifi==2018.4.16
chardet==3.0.4
idna==2.7
pipenv==11.8.2
PySocks==1.6.8
requests==2.19.1
urllib3==1.23
virtualenv==16.0.0
virtualenv-clone==0.3.0
You are using pip version 9.0.2, however version 10.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Here is the output of heroku run echo $PATH
mike#mike-thinks:~/Programing/Rasa/myflaskapp$ heroku run echo $PATH
Running echo /home/mike/bin:/home/mike/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/bin:/usr/lib/jvm/java-version/bin:/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java/bin:/usr/local/hadoop/bin on ⬢ rosenberg-moodbot... up, run.2949 (Free)
/home/mike/bin:/home/mike/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/lib/jvm/java-8-oracle/bin:/usr/lib/jvm/java-8-oracle/db/bin:/usr/lib/jvm/java-8-oracle/jre/bin:/usr/lib/jvm/java-version/bin:/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java/bin:/usr/local/hadoop/bin

Dashing on Heroku giving "config.ru" error

So, I am just trying to get a simple Heroku server running Dashing up. So far, I have the dashing and gemlock committed to heroku. Whenever I open the site, I get an error. My logs give me this:
2015-03-14T04:05:37.617789+00:00 heroku[api]: Deploy 2447a74 by #gmail.com
2015-03-14T04:05:37.617789+00:00 heroku[api]: Release v8 created by #gmail.com
2015-03-14T04:05:38.099916+00:00 heroku[web.1]: State changed from crashed to starting
2015-03-14T04:05:41.184158+00:00 heroku[web.1]: Starting process with command bundle exec thin start -R config.ru -e pr
oduction -p 12627
2015-03-14T04:05:43.367997+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.3/lib/rack/adapter/loader.rb:32
:in read': No such file or directory - config.ru (Errno::ENOENT)
2015-03-14T04:05:43.368046+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.3/lib/rack/adapter/load
er.rb:32:inload'
2015-03-14T04:05:43.368055+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.3/lib/thin/runner.rb:20
0:in run_command'
2015-03-14T04:05:43.368051+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.3/lib/thin/controllers/
controller.rb:182:inload_rackup_config'
2015-03-14T04:05:43.368053+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.3/lib/thin/controllers/
controller.rb:72:in start'
2015-03-14T04:05:43.368064+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.3/bin/thin:6:in'
2015-03-14T04:05:43.368066+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/bin/thin:23:in load'
2015-03-14T04:05:43.368062+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/gems/thin-1.6.3/lib/thin/runner.rb:15
6:inrun!'
2015-03-14T04:05:43.368069+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.0.0/bin/thin:23:in `'
2015-03-14T04:05:44.164461+00:00 heroku[web.1]: State changed from starting to crashed
2015-03-14T04:05:44.157004+00:00 heroku[web.1]: Process exited with status 1
2015-03-14T04:06:01.687293+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=pacific-d
awn-3700.herokuapp.com request_id=902320e9-1789-4099-94b2-8b4431d59495 fwd="66.190.95.133" dyno= connect= service= statu
s=503 bytes=
2015-03-14T04:06:02.015965+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" hos
t=pacific-dawn-3700.herokuapp.com request_id=6563d675-9732-4a21-84f4-c486fb6d792e fwd="66.190.95.133" dyno= connect= ser
vice= status=503 bytes=
A config.ru file was never created...I'm new to Ruby and Dashing and Heroku. I've even tried creating a blank config.ru, but even more errors occur...
Found the config file in anothjer directory somehow. Popped it in, it works!

Resources