Deployed Spring Boot Application on Heroku Not working - firebase

I have my Spring Boot Application (Maven) which connects Firebase DB to fetch data and deployed on heroku. but i'm getting
heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/check/value" host=.herokuapp.com request_id=4d200dd7-c893-4cc3-8ce2-a3a12bf79592 fwd="106.201.132.7" dyno= connect= service= status=503 bytes= protocol=https
and i found that issue with connecting firebaseDB by heroku(in my localserver, it is working).

Related

Deploy shiny app with Heroku Error R10 (Boot timeout)

I am trying to deploy my shiny app with heroku, but I have this output
web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2021-03-08T04:40:12.154157+00:00 heroku[web.1]: Stopping process with SIGKILL
2021-03-08T04:40:12.344233+00:00 heroku[web.1]: Process exited with status 137
2021-03-08T04:40:12.428222+00:00 heroku[web.1]: State changed from starting to crashed
2021-03-08T04:40:16.087134+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=sccosmo.herokuapp.com request_id=c07864e8-1e9e-49ea-ac9a-c6e87eafec83 fwd="187.232.16.32" dyno= connect= service= status=503 bytes= protocol=https
2021-03-08T04:40:16.167140+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=hello.herokuapp.com request_id=a3953768-7884-4654-8db1-dee6f6a92708 fwd="187.232.16.32" dyno= connect= service= status=503 bytes= protocol=https
How can I solve this?
This is my file run.app
library(shiny)
port <- Sys.getenv('PORT')
shiny::runApp(
appDir = getwd(),
host = '0.0.0.0',
port = as.numeric(port)
)

Deploy Spring MVC on Heroku

I want to try to deploy the app on heroku. Created a simple MVC Spring that outputs "Hello Mark" in the browser. The app works. I follow the instructions.
Call:
heroku ps:scale web=1
Scaling dynos... !
! Couldn't find that process type (web).
And when you open the app
Application error
An error occurred in the application and your page could not be served. If you are the application owner, check your logs for details. You can do this from the Heroku CLI with the command
heroku logs --tail
The logs show an error:
2020-10-01T16:36:04.081129+00:00 app[api]: Initial release by user mark.sinakaev#gmail.com
2020-10-01T16:36:04.081129+00:00 app[api]: Release v1 created by user mark.sinakaev#gmail.com
2020-10-01T16:36:04.325650+00:00 app[api]: Release v2 created by user mark.sinakaev#gmail.com
2020-10-01T16:36:04.325650+00:00 app[api]: Enable Logplex by user mark.sinakaev#gmail.com
2020-10-01T16:38:12.000000+00:00 app[api]: Build started by user mark.sinakaev#gmail.com
2020-10-01T16:38:36.880432+00:00 app[api]: Release v3 created by user mark.sinakaev#gmail.com
2020-10-01T16:38:36.880432+00:00 app[api]: Deploy ab380bda by user mark.sinakaev#gmail.com
2020-10-01T16:38:39.000000+00:00 app[api]: Build succeeded
2020-10-01T16:42:01.754283+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/" host=sinakaev.herokuapp.com request_id=1b73c233-00df-4d63-abe3-b406bbd75fbc fwd="95.30.16.131" dyno= connect= service= status=503 bytes= protocol=https
2020-10-01T16:42:02.130866+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/favicon.ico" host=sinakaev.herokuapp.com request_id=40a7902a-9cd9-43f1-a693-66aa96ad1bf1 fwd="95.30.16.131" dyno= connect= service= status=503 bytes= protocol=https
2020-10-01T16:59:27.106572+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/" host=sinakaev.herokuapp.com request_id=74ad276a-e21b-4960-9e5a-b460ec0f2fca fwd="95.30.16.131" dyno= connect= service= status=503 bytes= protocol=https
2020-10-01T16:59:27.403649+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/favicon.ico" host=sinakaev.herokuapp.com request_id=53fdb320-c269-4d38-bd27-f88f46b84256 fwd="95.30.16.131" dyno= connect= service= status=503 bytes= protocol=https
Give me an idea, please, how to solve the problem?
Do you have a Procfile? You should define your web process in that file, and then you can scale up the web dyno before sending traffic.

Unable to access shiny server in docker container

I have a Dockerized R Shiny app on Google Cloud VM. It was running well but from yesterday I am not able to access the shiny server. I have checked the docker logs and it gives me below message:
**[2019-03-13T14:56:11.496] [INFO] shiny-server - Shiny Server v1.5.7.890 (Node.js v8.10.0)
[2019-03-13T14:56:11.498] [INFO] shiny-server - Using config file "/etc/shiny-server/shiny-server.conf"
[2019-03-13T14:56:11.559] [WARN] shiny-server - Running as root unnecessarily is a security risk! You could be running more securely as non-root.
[2019-03-13T14:56:11.562] [INFO] shiny-server - Starting listener on 0.0.0.0:3838**
So, does it means the shiny server is running? If YES then why I am not able to access it from a browser (on the browser it gives me an error ERR_CONNECTION_REFUSED)?
Note: The port 3838 (default shiny server port) is whitelisted from VM.

Deployed Meteor app to Heroku not working

I have deployed an app to Heroku using this tutorial: https://medium.com/#leonardykris/how-to-run-a-meteor-js-application-on-heroku-in-10-steps-7aceb12de234
I've even just created a new app with meteor create herokutest, created a new heroku app called ludotestone, and pushed it to Heroku Git, but still its not working.
When I run heroku logs --tail I get the following result:
2017-02-22T15:56:07.680626+00:00 app[api]: Release v1 created by user dev#friendsagency.com
2017-02-22T15:56:07.529897+00:00 app[api]: Initial release by user dev#friendsagency.com
2017-02-22T15:56:07.645071+00:00 app[api]: Enable Logplex by user dev#friendsagency.com
2017-02-22T15:56:07.645071+00:00 app[api]: Release v2 created by user dev#friendsagency.com
2017-02-22T15:56:07.752423+00:00 app[api]: Release v2 created by user dev#friendsagency.com
2017-02-22T15:56:07.529897+00:00 app[api]: Release v1 created by user dev#friendsagency.com
2017-02-22T15:56:29.993806+00:00 app[api]: Attach MONGODB (#ref:mongolab-silhouetted-71457) by user dev#friendsagency.com
2017-02-22T15:56:29.993806+00:00 app[api]: Release v3 created by user dev#friendsagency.com
2017-02-22T15:56:30.133334+00:00 app[api]: Release v3 created by user dev#friendsagency.com
2017-02-22T15:57:59.468311+00:00 app[api]: Set MONGO_URL config vars by user dev#friendsagency.com
2017-02-22T15:57:59.468311+00:00 app[api]: Release v4 created by user dev#friendsagency.com
2017-02-22T15:57:59.651147+00:00 app[api]: Release v4 created by user dev#friendsagency.com
2017-02-22T15:58:32.383523+00:00 heroku[router]: at=info code=H81 desc="Blank app" method=GET path="/" host=ludotestone.herokuapp.com request_id=ef4376e2-218a-44ee-89ee-a8c762c23a11 fwd="37.235.112.81" dyno= connect= service= status=502 bytes=
2017-02-22T15:58:32.907631+00:00 heroku[router]: at=info code=H81 desc="Blank app" method=GET path="/favicon.ico" host=ludotestone.herokuapp.com request_id=1b246c81-49bd-450d-8e83-7bd83e095504 fwd="37.235.112.81" dyno= connect= service= status=502 bytes=
2017-02-22T15:58:50.239561+00:00 app[api]: Release v5 created by user dev#friendsagency.com
2017-02-22T15:58:50.239561+00:00 app[api]: Set ROOT_URL config vars by user dev#friendsagency.com
2017-02-22T15:58:50.375276+00:00 app[api]: Release v5 created by user dev#friendsagency.com
2017-02-22T15:59:24.000000+00:00 app[api]: Build started by user dev#friendsagency.com
2017-02-22T16:07:15.247743+00:00 app[api]: Scaled to web#1:Free by user dev#friendsagency.com
2017-02-22T16:07:15.205972+00:00 app[api]: Deploy 7970970 by user dev#friendsagency.com
2017-02-22T16:07:15.205972+00:00 app[api]: Release v6 created by user dev#friendsagency.com
2017-02-22T16:07:15.586286+00:00 app[api]: Release v6 created by user dev#friendsagency.com
2017-02-22T15:59:24.000000+00:00 app[api]: Build succeeded
2017-02-22T16:07:43.758842+00:00 heroku[web.1]: Starting process with command `node build/bundle/main.js`
2017-02-22T16:07:46.734182+00:00 heroku[web.1]: Process exited with status 8
2017-02-22T16:07:46.620143+00:00 app[web.1]:
2017-02-22T16:07:46.621194+00:00 app[web.1]: throw new assert.AssertionError({
2017-02-22T16:07:46.620605+00:00 app[web.1]: assert.js:93
2017-02-22T16:07:46.621196+00:00 app[web.1]: ^
2017-02-22T16:07:46.623579+00:00 app[web.1]: AssertionError: "undefined" === "function"
2017-02-22T16:07:46.623582+00:00 app[web.1]: at wrapPathFunction (/app/build/bundle/programs/server/mini-files.js:77:10)
2017-02-22T16:07:46.623583+00:00 app[web.1]: at Object.<anonymous> (/app/build/bundle/programs/server/mini-files.js:108:24)
2017-02-22T16:07:46.623583+00:00 app[web.1]: at Module._compile (module.js:456:26)
2017-02-22T16:07:46.623585+00:00 app[web.1]: at Object.Module._extensions..js (module.js:474:10)
2017-02-22T16:07:46.623585+00:00 app[web.1]: at Module.load (module.js:356:32)
2017-02-22T16:07:46.623586+00:00 app[web.1]: at Function.Module._load (module.js:312:12)
2017-02-22T16:07:46.623586+00:00 app[web.1]: at Module.require (module.js:364:17)
2017-02-22T16:07:46.623587+00:00 app[web.1]: at require (module.js:380:17)
2017-02-22T16:07:46.623587+00:00 app[web.1]: at Object.<anonymous> (/app/build/bundle/programs/server/boot.js:9:13)
2017-02-22T16:07:46.623588+00:00 app[web.1]: at Module._compile (module.js:456:26)
2017-02-22T16:07:46.763859+00:00 heroku[web.1]: State changed from starting to crashed
2017-02-22T16:07:46.764493+00:00 heroku[web.1]: State changed from crashed to starting
2017-02-22T16:08:12.517015+00:00 heroku[web.1]: Starting process with command `node build/bundle/main.js`
2017-02-22T16:08:14.723827+00:00 app[web.1]:
2017-02-22T16:08:14.724103+00:00 app[web.1]: assert.js:93
2017-02-22T16:08:14.724315+00:00 app[web.1]: throw new assert.AssertionError({
2017-02-22T16:08:14.724317+00:00 app[web.1]: ^
2017-02-22T16:08:14.725795+00:00 app[web.1]: AssertionError: "undefined" === "function"
2017-02-22T16:08:14.725796+00:00 app[web.1]: at wrapPathFunction (/app/build/bundle/programs/server/mini-files.js:77:10)
2017-02-22T16:08:14.725797+00:00 app[web.1]: at Object.<anonymous> (/app/build/bundle/programs/server/mini-files.js:108:24)
2017-02-22T16:08:14.725798+00:00 app[web.1]: at Module._compile (module.js:456:26)
2017-02-22T16:08:14.725798+00:00 app[web.1]: at Object.Module._extensions..js (module.js:474:10)
2017-02-22T16:08:14.725799+00:00 app[web.1]: at Module.load (module.js:356:32)
2017-02-22T16:08:14.725799+00:00 app[web.1]: at Function.Module._load (module.js:312:12)
2017-02-22T16:08:14.725800+00:00 app[web.1]: at Module.require (module.js:364:17)
2017-02-22T16:08:14.725800+00:00 app[web.1]: at require (module.js:380:17)
2017-02-22T16:08:14.725800+00:00 app[web.1]: at Object.<anonymous> (/app/build/bundle/programs/server/boot.js:9:13)
2017-02-22T16:08:14.725801+00:00 app[web.1]: at Module._compile (module.js:456:26)
2017-02-22T16:08:14.849873+00:00 heroku[web.1]: State changed from starting to crashed
2017-02-22T16:08:14.831165+00:00 heroku[web.1]: Process exited with status 8
2017-02-22T16:20:15.789306+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=ludotestone.herokuapp.com request_id=4e8276da-dda8-4dcc-b4eb-9a480acb00d3 fwd="37.235.112.81" dyno= connect= service= status=503 bytes=
2017-02-22T16:20:17.692344+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=ludotestone.herokuapp.com request_id=ecf0bbfe-a03c-477d-9af1-69d27c9ec548 fwd="37.235.112.81" dyno= connect= service= status=503 bytes=
I have no idea what's going on, and how to fix this.

MeteorJS v 1.3 to Heroku error

I want to deploy Meteor to heroku but have problems with starting the app.
I followed this tutorial
In heroku logs -t this results in:
2016-04-25T13:20:44.434043+00:00 heroku[web.1]: State changed from
crashed to starting 2016-04-25T13:20:48.587122+00:00 heroku[web.1]:
Starting process with command `.meteor/heroku_build/bin/node
.meteor/heroku_build/app/main.js` 2016-04-25T13:21:49.118920+00:00
heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind
to $PORT within 60 seconds of launch 2016-04-25T13:21:49.118920+00:00
heroku[web.1]: Stopping process with SIGKILL
2016-04-25T13:21:50.240617+00:00 heroku[web.1]: Process exited with
status 137 2016-04-25T13:21:50.250147+00:00 heroku[web.1]: State
changed from starting to crashed 2016-04-25T13:21:51.781162+00:00
heroku[router]: at=error code=H10 desc="App crashed" method=GET
path="/" host=pcmaster.herokuapp.com
request_id=99d374ee-cd1d-460f-b2bc-ef867dca219f fwd="217.196.169.249"
dyno= connect= service= status=503 bytes=
2016-04-25T13:21:53.057121+00:00 heroku[router]: at=error code=H10
desc="App crashed" method=GET path="/favicon.ico"
host=pcmaster.herokuapp.com
request_id=43cb523f-0036-4af8-b6d6-6db4c883f2b2 fwd="217.196.169.249"
dyno= connect= service= status=503 bytes=
What do I need to do differently?
Thanks

Resources