Application Error, heroku hosting, backend App - mongodb

Guys i'm trying to make a hosting for my backend app, and this is the second time i do it, the problem is that, i have this error
And, i tried to log my app so i can see where is the error, and this appears
2021-03-21T18:22:21.067459+00:00 heroku[web.1]: Starting process with command `npm run start`
2021-03-21T18:22:25.290401+00:00 app[web.1]:
2021-03-21T18:22:25.290415+00:00 app[web.1]: > server#1.0.0 start /app
2021-03-21T18:22:25.290416+00:00 app[web.1]: > nodemon index.js
2021-03-21T18:22:25.290416+00:00 app[web.1]:
2021-03-21T18:22:25.316554+00:00 app[web.1]: sh: 1: nodemon: not found
2021-03-21T18:22:25.362375+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2021-03-21T18:22:25.363310+00:00 app[web.1]: npm ERR! syscall spawn
2021-03-21T18:22:25.364814+00:00 app[web.1]: npm ERR! file sh
2021-03-21T18:22:25.365654+00:00 app[web.1]: npm ERR! errno ENOENT
2021-03-21T18:22:25.388201+00:00 app[web.1]: npm ERR! server#1.0.0 start: `nodemon index.js`
2021-03-21T18:22:25.388571+00:00 app[web.1]: npm ERR! spawn ENOENT
2021-03-21T18:22:25.389012+00:00 app[web.1]: npm ERR!
2021-03-21T18:22:25.389281+00:00 app[web.1]: npm ERR! Failed at the
server#1.0.0 start script.
2021-03-21T18:22:25.389521+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2021-03-21T18:22:25.400950+00:00 app[web.1]:
2021-03-21T18:22:25.401357+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2021-03-21T18:22:25.401620+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2021-03-21T18_22_25_390Z-debug.log
2021-03-21T18:22:25.500796+00:00 heroku[web.1]: Process exited with
status 1
2021-03-21T18:22:25.573335+00:00 heroku[web.1]: State changed from starting to crashed
2021-03-21T18:22:25.576936+00:00 heroku[web.1]: State changed from crashed to starting
2021-03-21T18:22:28.365986+00:00 heroku[web.1]: Starting process with command `npm run start`
2021-03-21T18:22:30.896431+00:00 app[web.1]:
2021-03-21T18:22:30.896468+00:00 app[web.1]: > server#1.0.0 start /app
2021-03-21T18:22:30.896468+00:00 app[web.1]: > nodemon index.js
2021-03-21T18:22:30.896468+00:00 app[web.1]:
2021-03-21T18:22:30.907038+00:00 app[web.1]: sh: 1: nodemon: not found
2021-03-21T18:22:30.919190+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2021-03-21T18:22:30.919692+00:00 app[web.1]: npm ERR! syscall spawn
2021-03-21T18:22:30.919949+00:00 app[web.1]: npm ERR! file sh
2021-03-21T18:22:30.920239+00:00 app[web.1]: npm ERR! errno ENOENT
2021-03-21T18:22:30.927062+00:00 app[web.1]: npm ERR! server#1.0.0 start: `nodemon index.js`
2021-03-21T18:22:30.927284+00:00 app[web.1]: npm ERR! spawn ENOENT
2021-03-21T18:22:30.927492+00:00 app[web.1]: npm ERR!
2021-03-21T18:22:30.927684+00:00 app[web.1]: npm ERR! Failed at the
server#1.0.0 start script.
2021-03-21T18:22:30.927851+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2021-03-21T18:22:30.963521+00:00 app[web.1]:
2021-03-21T18:22:30.963855+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2021-03-21T18:22:30.964051+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2021-03-21T18_22_30_928Z-debug.log
2021-03-21T18:22:31.015557+00:00 heroku[web.1]: Process exited with
status 1
2021-03-21T18:22:31.101810+00:00 heroku[web.1]: State changed from starting to crashed
2021-03-21T18:22:44.381282+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=daily-mern.herokuapp.com
request_id=836abccf-8d2c-432d-a50f-53810887e9ad fwd="177.254.11.56"
dyno= connect= service= status=503 bytes= protocol=https
2021-03-21T18:22:48.388632+00:00 heroku[router]: at=error code=H10 d
PS C:\Users\diego cifuentes\Desktop\Portafolio\Fullstack Projects\Daily App - MERN\server> heroku restartRestarting dynos on ⬢ daily-mern... done
PS C:\Users\diego cifuentes\Desktop\Portafolio\Fullstack Projects\Daily App - MERN\server> heroku logs --tail --app daily-mern
2021-03-21T18:15:05.905941+00:00 app[api]: Initial release by user diegodarkusgamer24#gmail.com
2021-03-21T18:15:05.905941+00:00 app[api]: Release v1 created by user diegodarkusgamer24#gmail.com
2021-03-21T18:15:06.053078+00:00 app[api]: Release v2 created by user diegodarkusgamer24#gmail.com
2021-03-21T18:15:06.053078+00:00 app[api]: Enable Logplex by user diegodarkusgamer24#gmail.com
2021-03-21T18:21:59.000000+00:00 app[api]: Build started by user diegodarkusgamer24#gmail.com
2021-03-21T18:22:16.855697+00:00 app[api]: Deploy 81dac1f3 by user diegodarkusgamer24#gmail.com
2021-03-21T18:22:16.855697+00:00 app[api]: Release v3 created by user diegodarkusgamer24#gmail.com
2021-03-21T18:22:16.875164+00:00 app[api]: Scaled to web#1:Free by user diegodarkusgamer24#gmail.com
2021-03-21T18:22:17.000000+00:00 app[api]: Build succeeded
2021-03-21T18:22:21.067459+00:00 heroku[web.1]: Starting process with command `npm run start`
2021-03-21T18:22:25.290401+00:00 app[web.1]:
2021-03-21T18:22:25.290415+00:00 app[web.1]: > server#1.0.0 start /app
2021-03-21T18:22:25.290416+00:00 app[web.1]: > nodemon index.js
2021-03-21T18:22:25.290416+00:00 app[web.1]:
2021-03-21T18:22:25.316554+00:00 app[web.1]: sh: 1: nodemon: not found
2021-03-21T18:22:25.362375+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2021-03-21T18:22:25.363310+00:00 app[web.1]: npm ERR! syscall spawn
2021-03-21T18:22:25.364814+00:00 app[web.1]: npm ERR! file sh
2021-03-21T18:22:25.365654+00:00 app[web.1]: npm ERR! errno ENOENT
2021-03-21T18:22:25.388201+00:00 app[web.1]: npm ERR! server#1.0.0 start: `nodemon index.js`
2021-03-21T18:22:25.388571+00:00 app[web.1]: npm ERR! spawn ENOENT
2021-03-21T18:22:25.389012+00:00 app[web.1]: npm ERR!
2021-03-21T18:22:25.389281+00:00 app[web.1]: npm ERR! Failed at the
server#1.0.0 start script.
2021-03-21T18:22:25.389521+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2021-03-21T18:22:25.400950+00:00 app[web.1]:
2021-03-21T18:22:25.401357+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2021-03-21T18:22:25.401620+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2021-03-21T18_22_25_390Z-debug.log
2021-03-21T18:22:25.500796+00:00 heroku[web.1]: Process exited with
status 1
2021-03-21T18:22:25.573335+00:00 heroku[web.1]: State changed from starting to crashed
2021-03-21T18:22:25.576936+00:00 heroku[web.1]: State changed from crashed to starting
2021-03-21T18:22:28.365986+00:00 heroku[web.1]: Starting process with command `npm run start`
2021-03-21T18:22:30.896431+00:00 app[web.1]:
2021-03-21T18:22:30.896468+00:00 app[web.1]: > server#1.0.0 start /app
2021-03-21T18:22:30.896468+00:00 app[web.1]: > nodemon index.js
2021-03-21T18:22:30.896468+00:00 app[web.1]:
2021-03-21T18:22:30.907038+00:00 app[web.1]: sh: 1: nodemon: not found
2021-03-21T18:22:30.919190+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2021-03-21T18:22:30.919692+00:00 app[web.1]: npm ERR! syscall spawn
2021-03-21T18:22:30.919949+00:00 app[web.1]: npm ERR! file sh
2021-03-21T18:22:30.920239+00:00 app[web.1]: npm ERR! errno ENOENT
2021-03-21T18:22:30.927062+00:00 app[web.1]: npm ERR! server#1.0.0 start: `nodemon index.js`
2021-03-21T18:22:30.927284+00:00 app[web.1]: npm ERR! spawn ENOENT
2021-03-21T18:22:30.927492+00:00 app[web.1]: npm ERR!
2021-03-21T18:22:30.927684+00:00 app[web.1]: npm ERR! Failed at the
server#1.0.0 start script.
2021-03-21T18:22:30.927851+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2021-03-21T18:22:30.963521+00:00 app[web.1]:
2021-03-21T18:22:30.963855+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2021-03-21T18:22:30.964051+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2021-03-21T18_22_30_928Z-debug.log
2021-03-21T18:22:31.015557+00:00 heroku[web.1]: Process exited with
status 1
2021-03-21T18:22:31.101810+00:00 heroku[web.1]: State changed from starting to crashed
2021-03-21T18:22:44.381282+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=daily-mern.herokuapp.com
request_id=836abccf-8d2c-432d-a50f-53810887e9ad fwd="177.254.11.56"
dyno= connect= service= status=503 bytes= protocol=https
2021-03-21T18:22:48.388632+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=daily-mern.herokuapp.com request_id=4872869b-653b-411c-8041-6c74f2c933d1 fwd="177.254.11.56" dyno= connect= service= status=503 bytes= protocol=https
2021-03-21T18:23:28.033455+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=daily-mern.herokuapp.com
request_id=938148d2-e2b9-44ec-b0e3-7c36a15c30bb fwd="177.254.11.56"
dyno= connect= service= status=503 bytes= protocol=https
2021-03-21T18:23:32.633910+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=daily-mern.herokuapp.com request_id=12ce541f-e48b-43f0-895f-4987388d0918 fwd="177.254.11.56" dyno= connect= service= status=503 bytes= protocol=https
2021-03-21T18:33:27.499912+00:00 heroku[web.1]: State changed from crashed to starting
2021-03-21T18:33:30.454323+00:00 heroku[web.1]: Starting process with command `npm run start`
2021-03-21T18:33:33.252960+00:00 app[web.1]:
2021-03-21T18:33:33.252982+00:00 app[web.1]: > server#1.0.0 start /app
2021-03-21T18:33:33.252982+00:00 app[web.1]: > nodemon index.js
2021-03-21T18:33:33.252983+00:00 app[web.1]:
2021-03-21T18:33:33.265627+00:00 app[web.1]: sh: 1: nodemon: not found
2021-03-21T18:33:33.280021+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2021-03-21T18:33:33.280574+00:00 app[web.1]: npm ERR! syscall spawn
2021-03-21T18:33:33.280907+00:00 app[web.1]: npm ERR! file sh
2021-03-21T18:33:33.281222+00:00 app[web.1]: npm ERR! errno ENOENT
2021-03-21T18:33:33.289740+00:00 app[web.1]: npm ERR! server#1.0.0 start: `nodemon index.js`
2021-03-21T18:33:33.290008+00:00 app[web.1]: npm ERR! spawn ENOENT
2021-03-21T18:33:33.290328+00:00 app[web.1]: npm ERR!
2021-03-21T18:33:33.290552+00:00 app[web.1]: npm ERR! Failed at the
server#1.0.0 start script.
2021-03-21T18:33:33.290851+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2021-03-21T18:33:33.303493+00:00 app[web.1]:
2021-03-21T18:33:33.304537+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2021-03-21T18:33:33.304746+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2021-03-21T18_33_33_292Z-debug.log
2021-03-21T18:33:33.372157+00:00 heroku[web.1]: Process exited with
status 1
2021-03-21T18:33:33.483971+00:00 heroku[web.1]: State changed from starting to crashed
2021-03-21T18:35:58.992675+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=daily-mern.herokuapp.com
request_id=af1f361c-1574-4a32-8f68-a7f0830c007a fwd="177.254.11.56"
dyno= connect= service= status=503 bytes= protocol=https
2021-03-21T18:36:01.295985+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=daily-mern.herokuapp.com request_id=759fada6-a151-4bdd-8689-5eab38ceaf35 fwd="177.254.11.56" dyno= connect= service= status=503 bytes= protocol=https
2021-03-21T18:36:27.162149+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=daily-mern.herokuapp.com
request_id=a44bcfca-29b0-4264-bc39-878747caad85 fwd="177.254.11.56"
dyno= connect= service= status=503 bytes= protocol=https
2021-03-21T18:36:30.775177+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=daily-mern.herokuapp.com request_id=ea89bde9-0278-4ded-b9e9-95925bef286b fwd="177.254.11.56" dyno= connect= service= status=503 bytes= protocol=https
I don't understand anything, what is goin on? how can i fix that?
This is my index of my backend, i'm working with node, express and mongoDB
import express from "express";
import mongoose from "mongoose";
import cors from "cors";
import dotenv from "dotenv";
import rooms from "./routes/rooms.js";
import user from "./routes/user.js";
import tasks from "./routes/tasks.js";
dotenv.config();
const PORT = process.env.PORT || 5000;
const app = express();
app.use(express.json({ limit: "20mb", extended: true }));
app.use(express.urlencoded({ limit: "20mb", extended: true }));
app.use(cors());
app.use("/rooms", rooms);
app.use("/tasks", tasks);
app.use("/user", user);
app.get("/", (req, res) => {
res.send("");
});
mongoose.connect(process.env.MONGODB, {
useNewUrlParser: true,
useUnifiedTopology: true,
dbName: "Daily-App"
});
mongoose.set("useFindAndModify", false);
app.listen(PORT, () => {
console.log("Server Working Succesfully");
});
My procfile
web: npm run start
My package json
{
"name": "server",
"version": "1.0.0",
"description": "",
"main": "index.js",
"type": "module",
"scripts": {
"start": "nodemon index.js"
},
"keywords": [],
"author": "",
"license": "ISC",
"dependencies": {
"bcryptjs": "^2.4.3",
"cors": "^2.8.5",
"dotenv": "^8.2.0",
"express": "^4.17.1",
"jsonwebtoken": "^8.5.1",
"mongoose": "^5.11.19"
}
}
If you know what's going on, i would love to read your answer, thank your for your time comunnity !

Add node version to your package.json: "engines": { "node": "v15.10.0" }
Change the "start" script from "nodemon server.js" to "node server.js". If you want to use nodemone locally, add one more script like : "dev": "nodemon server.js" and use npm run dev to start the server locally.
You must push your .env to your heroku server also.
Check if you .env file is being ignored in .gitignore.
ps: package.json: I don't see "nodemon" in your "dependencies".
did you installed it? If you installed it, it should be there like : "nodemon": "^2.0.7" or if you installed it with npm i --save-dev: "devDependencies": { "nodemon": "^2.0.7" }
Wish this help you.

Related

Deploying Kotlin Spring Boot App to Heroku - App crashes with H10

I am building an application that uploads files to Postgres with a Gradle Kotlin Spring Boot Backend. I build it locally and everything worked fine now I wanted to deploy the backend to Heroku. I added the Heroku Postgres Ressources and updated my application.properties and tested the DB connection with IntelliJ and it seems to be working.
Now when I deploy it and open my URL I get an Application error. In my console I see
GET https://unsplasy-backend.herokuapp.com/ 503 (Service Unavailable)
favicon.ico:1 GET https://unsplasy-backend.herokuapp.com/favicon.ico 503 (Service Unavailable)
After running heroku logs --tail I get the following output
2021-04-19T11:08:01.056208+00:00 app[web.1]: at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:88)
2021-04-19T11:08:01.126263+00:00 heroku[web.1]: Process exited with status 1
2021-04-19T11:08:01.203810+00:00 heroku[web.1]: State changed from starting to crashed
2021-04-19T11:08:03.074812+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=unsplasy-backend.herokuapp.com request_id=58e31d19-484f-44e5-b5b0-ba39931a10c4 fwd="45.86.203.98" dyno= connect= service= status=503 bytes= protocol=https
2021-04-19T11:08:03.513057+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=unsplasy-backend.herokuapp.com request_id=256e63d5-77de-46f9-9062-f21880e2c964 fwd="45.86.203.98" dyno= connect= service= status=503 bytes= protocol=https
2021-04-19T11:08:10.824894+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=unsplasy-backend.herokuapp.com request_id=2225a1d2-28fd-4d21-b9f9-6017da94540e fwd="45.86.203.98" dyno= connect= service= status=503 bytes= protocol=https
2021-04-19T11:08:11.203409+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=unsplasy-backend.herokuapp.com request_id=b4861295-84c0-4393-9869-8ba9ca1eb5d0 fwd="45.86.203.98" dyno= connect= service= status=503 bytes= protocol=https
2021-04-19T11:08:23.000000+00:00 app[api]: Build succeeded
2021-04-19T11:09:22.000000+00:00 app[api]: Build started by user marco.braun2013#icloud.com
2021-04-19T11:10:17.835261+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=unsplasy-backend.herokuapp.com request_id=b4c155c0-ba77-4796-b570-d61e6b5c7582 fwd="45.86.203.98" dyno= connect= service= status=503 bytes= protocol=https
2021-04-19T11:10:18.234507+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=unsplasy-backend.herokuapp.com request_id=21e5b9d2-ba5f-4b56-9733-1120855e7831 fwd="45.86.203.98" dyno= connect= service= status=503 bytes= protocol=https
2021-04-19T11:10:29.554184+00:00 app[api]: Deploy 808fbdd5 by user marco.braun2013#icloud.com
2021-04-19T11:10:29.554184+00:00 app[api]: Release v11 created by user marco.braun2013#icloud.com
2021-04-19T11:10:30.764211+00:00 heroku[web.1]: State changed from crashed to starting
2021-04-19T11:10:34.769023+00:00 heroku[web.1]: Starting process with command `java -Dserver.port=7456 $JAVA_OPTS -jar build/libs/*.jar`
2021-04-19T11:10:37.737112+00:00 app[web.1]: Create a Procfile to customize the command used to run this process: https://devcenter.heroku.com/articles/procfile
2021-04-19T11:10:37.754141+00:00 app[web.1]: Setting JAVA_TOOL_OPTIONS defaults based on dyno size. Custom settings will override them.
2021-04-19T11:10:37.757609+00:00 app[web.1]: Picked up JAVA_TOOL_OPTIONS: -Xmx300m -Xss512k -XX:CICompilerCount=2 -Dfile.encoding=UTF-8
2021-04-19T11:10:38.302494+00:00 app[web.1]: Exception in thread "main" java.lang.UnsupportedClassVersionError: mbraun/unsplasy/UnsplasyApplicationKt has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
2021-04-19T11:10:38.302797+00:00 app[web.1]: at java.lang.ClassLoader.defineClass1(Native Method)
2021-04-19T11:10:38.302798+00:00 app[web.1]: at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
2021-04-19T11:10:38.302799+00:00 app[web.1]: at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
2021-04-19T11:10:38.302800+00:00 app[web.1]: at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
2021-04-19T11:10:38.302836+00:00 app[web.1]: at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
2021-04-19T11:10:38.302883+00:00 app[web.1]: at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
2021-04-19T11:10:38.302918+00:00 app[web.1]: at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
2021-04-19T11:10:38.302993+00:00 app[web.1]: at java.security.AccessController.doPrivileged(Native Method)
2021-04-19T11:10:38.303057+00:00 app[web.1]: at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
2021-04-19T11:10:38.303149+00:00 app[web.1]: at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
2021-04-19T11:10:38.303225+00:00 app[web.1]: at org.springframework.boot.loader.LaunchedURLClassLoader.loadClass(LaunchedURLClassLoader.java:151)
2021-04-19T11:10:38.303316+00:00 app[web.1]: at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
2021-04-19T11:10:38.303318+00:00 app[web.1]: at java.lang.Class.forName0(Native Method)
2021-04-19T11:10:38.303413+00:00 app[web.1]: at java.lang.Class.forName(Class.java:348)
2021-04-19T11:10:38.303415+00:00 app[web.1]: at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:46)
2021-04-19T11:10:38.303461+00:00 app[web.1]: at org.springframework.boot.loader.Launcher.launch(Launcher.java:108)
2021-04-19T11:10:38.303548+00:00 app[web.1]: at org.springframework.boot.loader.Launcher.launch(Launcher.java:58)
2021-04-19T11:10:38.303608+00:00 app[web.1]: at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:88)
2021-04-19T11:10:38.367928+00:00 heroku[web.1]: Process exited with status 1
2021-04-19T11:10:38.426299+00:00 heroku[web.1]: State changed from starting to crashed
2021-04-19T11:10:38.816929+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=unsplasy-backend.herokuapp.com request_id=0d92e58d-9078-4909-9997-d8a806d124bd fwd="45.86.203.98" dyno= connect= service= status=503 bytes= protocol=https
2021-04-19T11:10:39.184155+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=unsplasy-backend.herokuapp.com request_id=ab885968-5f0c-4a7d-b844-1d9074b4ab45 fwd="45.86.203.98" dyno= connect= service= status=503 bytes= protocol=https
2021-04-19T11:11:03.000000+00:00 app[api]: Build succeeded
2021-04-19T11:16:52.131964+00:00 heroku[web.1]: State changed from crashed to starting
2021-04-19T11:16:56.540255+00:00 heroku[web.1]: Starting process with command `java -Dserver.port=38647 $JAVA_OPTS -jar build/libs/*.jar`
2021-04-19T11:16:58.584422+00:00 app[web.1]: Create a Procfile to customize the command used to run this process: https://devcenter.heroku.com/articles/procfile
2021-04-19T11:16:58.600495+00:00 app[web.1]: Setting JAVA_TOOL_OPTIONS defaults based on dyno size. Custom settings will override them.
2021-04-19T11:16:58.603888+00:00 app[web.1]: Picked up JAVA_TOOL_OPTIONS: -Xmx300m -Xss512k -XX:CICompilerCount=2 -Dfile.encoding=UTF-8
2021-04-19T11:16:59.012658+00:00 app[web.1]: Exception in thread "main" java.lang.UnsupportedClassVersionError: mbraun/unsplasy/UnsplasyApplicationKt has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
2021-04-19T11:16:59.012878+00:00 app[web.1]: at java.lang.ClassLoader.defineClass1(Native Method)
2021-04-19T11:16:59.012976+00:00 app[web.1]: at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
2021-04-19T11:16:59.013043+00:00 app[web.1]: at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
2021-04-19T11:16:59.013109+00:00 app[web.1]: at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
2021-04-19T11:16:59.013188+00:00 app[web.1]: at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
2021-04-19T11:16:59.013259+00:00 app[web.1]: at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
2021-04-19T11:16:59.013329+00:00 app[web.1]: at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
2021-04-19T11:16:59.014247+00:00 app[web.1]: at java.security.AccessController.doPrivileged(Native Method)
2021-04-19T11:16:59.014248+00:00 app[web.1]: at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
2021-04-19T11:16:59.014248+00:00 app[web.1]: at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
2021-04-19T11:16:59.014249+00:00 app[web.1]: at org.springframework.boot.loader.LaunchedURLClassLoader.loadClass(LaunchedURLClassLoader.java:151)
2021-04-19T11:16:59.014249+00:00 app[web.1]: at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
2021-04-19T11:16:59.014250+00:00 app[web.1]: at java.lang.Class.forName0(Native Method)
2021-04-19T11:16:59.014251+00:00 app[web.1]: at java.lang.Class.forName(Class.java:348)
2021-04-19T11:16:59.014350+00:00 app[web.1]: at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:46)
2021-04-19T11:16:59.014351+00:00 app[web.1]: at org.springframework.boot.loader.Launcher.launch(Launcher.java:108)
2021-04-19T11:16:59.014351+00:00 app[web.1]: at org.springframework.boot.loader.Launcher.launch(Launcher.java:58)
2021-04-19T11:16:59.014351+00:00 app[web.1]: at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:88)
2021-04-19T11:16:59.228371+00:00 heroku[web.1]: Process exited with status 1
2021-04-19T11:16:59.327826+00:00 heroku[web.1]: State changed from starting to crashed
2021-04-19T11:16:59.332351+00:00 heroku[web.1]: State changed from crashed to starting
2021-04-19T11:17:04.242879+00:00 heroku[web.1]: Starting process with command `java -Dserver.port=17021 $JAVA_OPTS -jar build/libs/*.jar`
2021-04-19T11:17:07.238276+00:00 app[web.1]: Create a Procfile to customize the command used to run this process: https://devcenter.heroku.com/articles/procfile
2021-04-19T11:17:07.268382+00:00 app[web.1]: Setting JAVA_TOOL_OPTIONS defaults based on dyno size. Custom settings will override them.
2021-04-19T11:17:07.272732+00:00 app[web.1]: Picked up JAVA_TOOL_OPTIONS: -Xmx300m -Xss512k -XX:CICompilerCount=2 -Dfile.encoding=UTF-8
2021-04-19T11:17:07.767002+00:00 app[web.1]: Exception in thread "main" java.lang.UnsupportedClassVersionError: mbraun/unsplasy/UnsplasyApplicationKt has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
2021-04-19T11:17:07.767483+00:00 app[web.1]: at java.lang.ClassLoader.defineClass1(Native Method)
2021-04-19T11:17:07.767673+00:00 app[web.1]: at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
2021-04-19T11:17:07.767796+00:00 app[web.1]: at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
2021-04-19T11:17:07.767953+00:00 app[web.1]: at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
2021-04-19T11:17:07.768085+00:00 app[web.1]: at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
2021-04-19T11:17:07.768273+00:00 app[web.1]: at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
2021-04-19T11:17:07.768415+00:00 app[web.1]: at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
2021-04-19T11:17:07.768819+00:00 app[web.1]: at java.security.AccessController.doPrivileged(Native Method)
2021-04-19T11:17:07.768945+00:00 app[web.1]: at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
2021-04-19T11:17:07.769079+00:00 app[web.1]: at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
2021-04-19T11:17:07.769225+00:00 app[web.1]: at org.springframework.boot.loader.LaunchedURLClassLoader.loadClass(LaunchedURLClassLoader.java:151)
2021-04-19T11:17:07.769353+00:00 app[web.1]: at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
2021-04-19T11:17:07.769510+00:00 app[web.1]: at java.lang.Class.forName0(Native Method)
2021-04-19T11:17:07.769607+00:00 app[web.1]: at java.lang.Class.forName(Class.java:348)
2021-04-19T11:17:07.769982+00:00 app[web.1]: at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:46)
2021-04-19T11:17:07.770117+00:00 app[web.1]: at org.springframework.boot.loader.Launcher.launch(Launcher.java:108)
2021-04-19T11:17:07.770257+00:00 app[web.1]: at org.springframework.boot.loader.Launcher.launch(Launcher.java:58)
2021-04-19T11:17:07.770377+00:00 app[web.1]: at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:88)
2021-04-19T11:17:07.830915+00:00 heroku[web.1]: Process exited with status 1
2021-04-19T11:17:07.943553+00:00 heroku[web.1]: State changed from starting to crashed
2021-04-19T11:18:13.716974+00:00 app[api]: Starting process with command `java -version` by user marco.braun2013#icloud.com
2021-04-19T11:18:17.924110+00:00 heroku[run.3775]: State changed from starting to up
2021-04-19T11:18:17.990783+00:00 heroku[run.3775]: Awaiting client
2021-04-19T11:18:18.323617+00:00 heroku[run.3775]: Starting process with command `java -version`
2021-04-19T11:18:22.915722+00:00 heroku[run.3775]: Process exited with status 0
2021-04-19T11:18:22.975840+00:00 heroku[run.3775]: State changed from up to complete
I am not quite sure where to start and what the best practice is after doing some research and not finding a solution. Also, I am wondering because I am not using the favicon.icon anywhere and not quite sure where it comes from and if this is the problem?
Do I have to change my Java Runtime version and if so why and what would be the best practice be? Or is there another mistake.
The error points out to the Java version you use: the app requires Java 11 but Heroku runs by default with Java 8
Exception in thread "main" java.lang.UnsupportedClassVersionError
mbraun/unsplasy/UnsplasyApplicationKt has been compiled by a more recent
version of the Java Runtime (class file version 55.0), this version of the Java
Runtime only recognizes class file versions up to 52.0
In the root folder create a file called system.properties:
java.runtime.version=11

Strapi deployed to Heroku is crashing in production?

I've got an app where the frontend is deployed to Netlify and the Strapi backend is deployed to Heroku. I recently upgraded Strapi from v3.0.6 to v3.1.3. I was previously using PostgresQL in production, so along with the Strapi upgrade I also am attempting to move over to MongoDB.
I'm attempting to deploy my backend to production, however I keep receiving a 503 error and the app crashes. You can see from the error logs below that there is an issue connecting to the Mongo database.
Here are my relevant logs from Heroku:
2020-08-06T15:06:49.848463+00:00 app[web.1]: > backend#0.1.0 start /app
2020-08-06T15:06:49.848464+00:00 app[web.1]: > strapi start
2020-08-06T15:06:49.848465+00:00 app[web.1]:
2020-08-06T15:06:52.238840+00:00 app[web.1]: (node:23) Warning: Accessing non-existent property 'count' of module exports inside circular dependency
2020-08-06T15:06:52.238869+00:00 app[web.1]: (Use `node --trace-warnings ...` to show where the warning was created)
2020-08-06T15:06:52.239130+00:00 app[web.1]: (node:23) Warning: Accessing non-existent property 'findOne' of module exports inside circular dependency
2020-08-06T15:06:52.239199+00:00 app[web.1]: (node:23) Warning: Accessing non-existent property 'remove' of module exports inside circular dependency
2020-08-06T15:06:52.239276+00:00 app[web.1]: (node:23) Warning: Accessing non-existent property 'updateOne' of module exports inside circular dependency
2020-08-06T15:07:10.279519+00:00 heroku[router]: at=error code=H20 desc="App boot timeout" method=GET path="/" host=<app-name>.herokuapp.com request_id=9e81f113-1003-42f7-82e7-59296dc1f0f8 fwd="24.19.220.31" dyno= connect= service= status=503 bytes= protocol=https
2020-08-06T15:07:22.242572+00:00 app[web.1]: [2020-08-06T15:07:22.241Z] debug ⛔️ Server wasn't able to start properly.
2020-08-06T15:07:22.243944+00:00 app[web.1]: [2020-08-06T15:07:22.243Z] error Error connecting to the Mongo database. Server selection timed out after 30000 ms
2020-08-06T15:07:22.266318+00:00 app[web.1]: npm ERR! code ELIFECYCLE
2020-08-06T15:07:22.266611+00:00 app[web.1]: npm ERR! errno 1
2020-08-06T15:07:22.269156+00:00 app[web.1]: npm ERR! backend#0.1.0 start: `strapi start`
2020-08-06T15:07:22.269330+00:00 app[web.1]: npm ERR! Exit status 1
2020-08-06T15:07:22.269513+00:00 app[web.1]: npm ERR!
2020-08-06T15:07:22.269976+00:00 app[web.1]: npm ERR! Failed at the backend#0.1.0 start script.
2020-08-06T15:07:22.270129+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-08-06T15:07:22.278069+00:00 app[web.1]:
2020-08-06T15:07:22.278314+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2020-08-06T15:07:22.278417+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2020-08-06T15_07_22_271Z-debug.log
2020-08-06T15:07:22.355748+00:00 heroku[web.1]: Process exited with status 1
2020-08-06T15:07:22.394507+00:00 heroku[web.1]: State changed from starting to crashed
2020-08-06T15:07:23.802505+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=<app-name>.herokuapp.com request_id=f5876daf-f945-46b8-88c0-08a61106cfc5 fwd="24.19.220.31" dyno= connect= service= status=503 bytes= protocol=https
I've got the Mongo URI env variable set in Heroku and the app runs fine locally. I'm using Mongo Atlas in the free tier, so I'm wondering if that has something to do with it? Does anyone have any ideas what could be the issue?
I spent 24 hours attempting to fix it before making this post, and just like that - a half hour after making this post - I fixed it, thanks to this SO answer. I needed to whitelist the IP address in order to allow the connection between MongoDB and Heroku!

I cannot connect Postgres DB with Strapi on Heroku

I try to set up Strapi + PostgresDB on Heroku.
I follow this manual step by step https://strapi.io/documentation/3.0.0-beta.x/deployment/heroku.html
When I deploy to Heroku I get: Application error
heroku logs --tail shows
npm ERR! my-host-cms#0.1.0 start: `strapi start`
2020-06-09T14:54:44.272624+00:00 app[web.1]: npm ERR! Exit status 1
2020-06-09T14:54:44.272950+00:00 app[web.1]: npm ERR!
2020-06-09T14:54:44.273144+00:00 app[web.1]: npm ERR! Failed at the my-host-cms#0.1.0 start script.
2020-06-09T14:54:44.273335+00:00 app[web.1]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-06-09T14:54:44.289977+00:00 app[web.1]:
2020-06-09T14:54:44.290269+00:00 app[web.1]: npm ERR! A complete log of this run can be found in:
2020-06-09T14:54:44.290445+00:00 app[web.1]: npm ERR! /app/.npm/_logs/2020-06-09T14_54_44_278Z-debug.log
2020-06-09T14:54:44.353188+00:00 heroku[web.1]: Process exited with status 1
2020-06-09T14:54:44.386798+00:00 heroku[web.1]: State changed from starting to crashed
2020-06-09T14:54:44.388614+00:00 heroku[web.1]: State changed from crashed to starting
2020-06-09T14:55:01.903657+00:00 heroku[web.1]: Starting process with command `npm start`
2020-06-09T14:55:05.469266+00:00 app[web.1]:
2020-06-09T14:55:05.469295+00:00 app[web.1]: > my-host-cms#0.1.0 start /app
2020-06-09T14:55:05.469296+00:00 app[web.1]: > strapi start
2020-06-09T14:55:05.469296+00:00 app[web.1]:
2020-06-09T14:55:08.015032+00:00 app[web.1]: [2020-06-09T14:55:08.013Z] error The client `sqlite3` is not installed.
2020-06-09T14:55:08.015961+00:00 app[web.1]: [2020-06-09T14:55:08.015Z] error You can install it with `$ npm install sqlite3 --save`.
and
2020-06-09T14:55:09.623864+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=my-host.herokuapp.com request_id=eea79361-593f-413e-89e2-d99d0153ddf3 fwd="37.57.145.70" dyno= connect= service= status=503 bytes= protocol=https
2020-06-09T15:01:07.901262+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/" host=my-host.herokuapp.com request_id=ce0353b0-5e45-422d-af43-f96614c8151d fwd="37.57.145.70" dyno= connect= service= status=503 bytes= protocol=https
I see it asks about sqlite3 but I have it package.json
The project was inited with --quickstart but I have made ./config/environments/production/database.json
If you installed strapi with the --quickstart flag then by default it would provision a SQLite db for you.
since you loading a db config for postpres, make sure you installed pg.
you can npm/yarn remove sqlite3 from your package.json if you not using it locally, ie.you have postgres installed and the service is running.
delete your cache folder and then npm run build
now push to heroku and open.
fyi. it is recommended that you have database.js over database.json
eg.
module.exports = ({ env }) => ({
defaultConnection: 'default',
connections: {
default: {
connector: 'bookshelf',
settings: {
client: 'postgres',
host: env('DATABASE_HOST'),
port: env.int('DATABASE_PORT'),
database: env('DATABASE_NAME'),
username: env('DATABASE_USERNAME'),
password: env('DATABASE_PASSWORD'),
ssl: env.bool('DATABASE_SSL'),
},
options: {}
},
},
});
In Heroku make sure that the postgres addon is provisioned.
check your config vars in heroku for the app is correct.
also make sure ./config/database.js or ./config/database.json has also been corrected to use the correct database.

Meteor.js App with Heroku Hosting (Connecting MongoLab DB) - An error occurred in the application and your page could not be served

I am trying to deploy my Meteor.js app to Heroku. I did this just fine without a db attached, but now I am trying to attach my MongoLab DB instance. When I tried to set this up, I am now getting the error:
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.
I took this advice, and ran heroku logs. The main error in the logs I am seeing is:
Error: failed to connect to [1:27017]
When typing heroku config | grep MONGOLAB_URI, I get the output (actual URI altered for obvious reasons):
MONGOLAB_URI: mongodb://heroku_8b43cf1g:besd10gsdgwertyapp2l4q9asd#ds69123.mongolab.com:69123/heroku_8b43cf1g
My heroku logs output:
2016-02-19T20:40:58.212644+00:00 heroku[router]: at=info method=GET path="/images/thisgray.png" host=www.mobapp.com request_id=f8233fb6-05d0-4b10-92c5-9c6c56a7de37 fwd="98.234.89.85" dyno=web.1 connect=1ms service=22ms status=200 bytes=21894
2016-02-19T20:40:58.394914+00:00 heroku[router]: at=info method=GET path="/images/thisthing.png" host=www.mobapp.com request_id=3e8d9359-df99-48a3-bdd8-8c64ef3bb53b fwd="98.234.89.85" dyno=web.1 connect=1ms service=5ms status=200 bytes=1448
2016-02-19T20:41:07.603609+00:00 heroku[router]: at=info method=GET path="/sockjs/048/myjmakg8/websocket" host=www.mobapp.com request_id=3d3e76d2-a61f-4367-a739-6c235c2ad41e fwd="98.234.89.85" dyno=web.1 connect=1ms service=8820ms status=101 bytes=175
2016-02-19T21:06:48.502986+00:00 heroku[api]: Set MONGO_URL config vars by bob#gmail.com
2016-02-19T21:06:48.502986+00:00 heroku[api]: Release v9 created by bob#gmail.com
2016-02-19T21:06:48.631929+00:00 heroku[web.1]: Restarting
2016-02-19T21:06:48.632533+00:00 heroku[web.1]: State changed from up to starting
2016-02-19T21:06:50.605685+00:00 heroku[web.1]: Starting process with command `.meteor/heroku_build/bin/node .meteor/heroku_build/app/main.js`
2016-02-19T21:06:51.951293+00:00 app[web.1]:
2016-02-19T21:06:51.951359+00:00 app[web.1]: /app/.meteor/heroku_build/app/programs/server/node_modules/fibers/future.js:278
2016-02-19T21:06:51.951567+00:00 app[web.1]: throw(ex);
2016-02-19T21:06:51.951569+00:00 app[web.1]: ^
2016-02-19T21:06:52.027676+00:00 app[web.1]: Error: failed to connect to [1:27017]
2016-02-19T21:06:52.027680+00:00 app[web.1]: at Object.Future.wait (/app/.meteor/heroku_build/app/programs/server/node_modules/fibers/future.js:398:15)
2016-02-19T21:06:52.027682+00:00 app[web.1]: at new MongoConnection (packages/mongo/mongo_driver.js:213:1)
2016-02-19T21:06:52.027683+00:00 app[web.1]: at new MongoInternals.RemoteCollectionDriver (packages/mongo/remote_collection_driver.js:4:1)
2016-02-19T21:06:52.027683+00:00 app[web.1]: at Object.<anonymous> (packages/mongo/remote_collection_driver.js:38:1)
2016-02-19T21:06:52.027684+00:00 app[web.1]: at Object.defaultRemoteCollectionDriver (packages/underscore/underscore.js:750:1)
2016-02-19T21:06:52.027686+00:00 app[web.1]: at mobapp.js:1:12
2016-02-19T21:06:52.027685+00:00 app[web.1]: at new Mongo.Collection (packages/mongo/collection.js:102:1)
2016-02-19T21:06:52.027687+00:00 app[web.1]: at /app/.meteor/heroku_build/app/programs/server/app/mobapp.js:20:4
2016-02-19T21:06:52.027688+00:00 app[web.1]: at Array.forEach (native)
2016-02-19T21:06:52.027687+00:00 app[web.1]: at /app/.meteor/heroku_build/app/programs/server/boot.js:242:10
2016-02-19T21:06:52.027689+00:00 app[web.1]: - - - - -
2016-02-19T21:06:52.027691+00:00 app[web.1]: at [object Object].<anonymous> (/app/.meteor/heroku_build/app/programs/server/npm/npm-mongo/node_modules/mongodb/lib/mongodb/connection/server.js:556:74)
2016-02-19T21:06:52.027692+00:00 app[web.1]: at [object Object].emit (events.js:106:17)
2016-02-19T21:06:52.027693+00:00 app[web.1]: at [object Object].<anonymous> (/app/.meteor/heroku_build/app/programs/server/npm/npm-mongo/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:156:15)
2016-02-19T21:06:52.027694+00:00 app[web.1]: at [object Object].emit (events.js:98:17)
2016-02-19T21:06:52.027695+00:00 app[web.1]: at Socket.<anonymous> (/app/.meteor/heroku_build/app/programs/server/npm/npm-mongo/node_modules/mongodb/lib/mongodb/connection/connection.js:534:10)
2016-02-19T21:06:52.027696+00:00 app[web.1]: at Socket.emit (events.js:95:17)
2016-02-19T21:06:52.027696+00:00 app[web.1]: at net.js:441:14
2016-02-19T21:06:52.027697+00:00 app[web.1]: at process._tickCallback (node.js:448:13)
2016-02-19T21:06:52.536968+00:00 heroku[web.1]: State changed from starting to crashed
2016-02-19T21:06:52.538299+00:00 heroku[web.1]: State changed from crashed to starting
2016-02-19T21:06:52.499425+00:00 heroku[web.1]: Process exited with status 8
2016-02-19T21:06:53.132126+00:00 heroku[web.1]: Stopping all processes with SIGTERM
2016-02-19T21:06:55.376840+00:00 heroku[web.1]: Process exited with status 143
2016-02-19T21:06:58.410626+00:00 heroku[web.1]: Starting process with command `.meteor/heroku_build/bin/node .meteor/heroku_build/app/main.js`
2016-02-19T21:07:01.046013+00:00 app[web.1]:
2016-02-19T21:07:01.046088+00:00 app[web.1]: /app/.meteor/heroku_build/app/programs/server/node_modules/fibers/future.js:278
2016-02-19T21:07:01.046292+00:00 app[web.1]: throw(ex);
2016-02-19T21:07:01.046296+00:00 app[web.1]: ^
2016-02-19T21:07:01.154404+00:00 app[web.1]: Error: failed to connect to [1:27017]
2016-02-19T21:07:01.154407+00:00 app[web.1]: at Object.Future.wait (/app/.meteor/heroku_build/app/programs/server/node_modules/fibers/future.js:398:15)
2016-02-19T21:07:01.154408+00:00 app[web.1]: at new MongoConnection (packages/mongo/mongo_driver.js:213:1)
2016-02-19T21:07:01.154409+00:00 app[web.1]: at new MongoInternals.RemoteCollectionDriver (packages/mongo/remote_collection_driver.js:4:1)
2016-02-19T21:07:01.154410+00:00 app[web.1]: at Object.defaultRemoteCollectionDriver (packages/underscore/underscore.js:750:1)
2016-02-19T21:07:01.154409+00:00 app[web.1]: at Object.<anonymous> (packages/mongo/remote_collection_driver.js:38:1)
2016-02-19T21:07:01.154410+00:00 app[web.1]: at new Mongo.Collection (packages/mongo/collection.js:102:1)
2016-02-19T21:07:01.154411+00:00 app[web.1]: at mobapp.js:1:12
2016-02-19T21:07:01.154412+00:00 app[web.1]: at /app/.meteor/heroku_build/app/programs/server/boot.js:242:10
2016-02-19T21:07:01.154413+00:00 app[web.1]: - - - - -
2016-02-19T21:07:01.154412+00:00 app[web.1]: at /app/.meteor/heroku_build/app/programs/server/app/mobapp.js:20:4
2016-02-19T21:07:01.154415+00:00 app[web.1]: at [object Object].<anonymous> (/app/.meteor/heroku_build/app/programs/server/npm/npm-mongo/node_modules/mongodb/lib/mongodb/connection/server.js:556:74)
2016-02-19T21:07:01.154412+00:00 app[web.1]: at Array.forEach (native)
2016-02-19T21:07:01.154415+00:00 app[web.1]: at [object Object].emit (events.js:106:17)
2016-02-19T21:07:01.154416+00:00 app[web.1]: at [object Object].<anonymous> (/app/.meteor/heroku_build/app/programs/server/npm/npm-mongo/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:156:15)
2016-02-19T21:07:01.154416+00:00 app[web.1]: at [object Object].emit (events.js:98:17)
2016-02-19T21:07:01.154418+00:00 app[web.1]: at Socket.emit (events.js:95:17)
2016-02-19T21:07:01.154417+00:00 app[web.1]: at Socket.<anonymous> (/app/.meteor/heroku_build/app/programs/server/npm/npm-mongo/node_modules/mongodb/lib/mongodb/connection/connection.js:534:10)
2016-02-19T21:07:01.154418+00:00 app[web.1]: at net.js:441:14
2016-02-19T21:07:01.154419+00:00 app[web.1]: at process._tickCallback (node.js:448:13)
2016-02-19T21:07:01.842656+00:00 heroku[web.1]: State changed from starting to crashed
2016-02-19T21:07:01.806613+00:00 heroku[web.1]: Process exited with status 8
2016-02-19T21:07:03.341588+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/sockjs/info?cb=8qpqf_gwxg" host=www.mobapp.com request_id=21a3ddc9-156e-45de-a6c9-c9b167ccf92b fwd="98.234.89.85" dyno= connect= service= status=503 bytes=
2016-02-19T21:07:12.176992+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/sockjs/info?cb=m_a3ombq8n" host=www.mobapp.com request_id=3735d992-8f04-46ed-90f6-6326f7949b8b fwd="98.234.89.85" dyno= connect= service= status=503 bytes=
2016-02-19T21:07:54.617993+00:00 heroku[api]: Set ROOT_URL config vars by bob#gmail.com
2016-02-19T21:07:54.618032+00:00 heroku[api]: Release v10 created by bob#gmail.com
2016-02-19T21:07:54.711020+00:00 heroku[web.1]: State changed from crashed to starting
2016-02-19T21:07:58.396900+00:00 heroku[web.1]: Starting process with command `.meteor/heroku_build/bin/node .meteor/heroku_build/app/main.js`
2016-02-19T21:08:01.569711+00:00 app[web.1]:
2016-02-19T21:08:01.569863+00:00 app[web.1]: /app/.meteor/heroku_build/app/programs/server/node_modules/fibers/future.js:278
2016-02-19T21:08:01.740472+00:00 app[web.1]: Error: failed to connect to [1:27017]
2016-02-19T21:08:01.740477+00:00 app[web.1]: at Object.Future.wait (/app/.meteor/heroku_build/app/programs/server/node_modules/fibers/future.js:398:15)
2016-02-19T21:08:01.570213+00:00 app[web.1]: throw(ex);
2016-02-19T21:08:01.570217+00:00 app[web.1]: ^
2016-02-19T21:08:01.740479+00:00 app[web.1]: at new MongoInternals.RemoteCollectionDriver (packages/mongo/remote_collection_driver.js:4:1)
2016-02-19T21:08:01.740479+00:00 app[web.1]: at Object.<anonymous> (packages/mongo/remote_collection_driver.js:38:1)
2016-02-19T21:08:01.740484+00:00 app[web.1]: at /app/.meteor/heroku_build/app/programs/server/boot.js:242:10
2016-02-19T21:08:01.740482+00:00 app[web.1]: at mobapp.js:1:12
2016-02-19T21:08:01.740478+00:00 app[web.1]: at new MongoConnection (packages/mongo/mongo_driver.js:213:1)
2016-02-19T21:08:01.740486+00:00 app[web.1]: - - - - -
2016-02-19T21:08:01.740483+00:00 app[web.1]: at /app/.meteor/heroku_build/app/programs/server/app/mobapp.js:20:4
2016-02-19T21:08:01.740485+00:00 app[web.1]: at Array.forEach (native)
2016-02-19T21:08:01.740488+00:00 app[web.1]: at [object Object].<anonymous> (/app/.meteor/heroku_build/app/programs/server/npm/npm-mongo/node_modules/mongodb/lib/mongodb/connection/server.js:556:74)
2016-02-19T21:08:01.740481+00:00 app[web.1]: at Object.defaultRemoteCollectionDriver (packages/underscore/underscore.js:750:1)
2016-02-19T21:08:01.740481+00:00 app[web.1]: at new Mongo.Collection (packages/mongo/collection.js:102:1)
2016-02-19T21:08:01.740489+00:00 app[web.1]: at [object Object].emit (events.js:106:17)
2016-02-19T21:08:01.740492+00:00 app[web.1]: at Socket.emit (events.js:95:17)
2016-02-19T21:08:01.740492+00:00 app[web.1]: at Socket.<anonymous> (/app/.meteor/heroku_build/app/programs/server/npm/npm-mongo/node_modules/mongodb/lib/mongodb/connection/connection.js:534:10)
2016-02-19T21:08:01.740494+00:00 app[web.1]: at process._tickCallback (node.js:448:13)
2016-02-19T21:08:01.740491+00:00 app[web.1]: at [object Object].emit (events.js:98:17)
2016-02-19T21:08:01.740493+00:00 app[web.1]: at net.js:441:14
2016-02-19T21:08:01.740490+00:00 app[web.1]: at [object Object].<anonymous> (/app/.meteor/heroku_build/app/programs/server/npm/npm-mongo/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:156:15)
2016-02-19T21:08:02.990797+00:00 heroku[web.1]: Process exited with status 8
2016-02-19T21:08:03.009142+00:00 heroku[web.1]: State changed from starting to crashed
2016-02-19T21:07:27.705989+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/sockjs/info?cb=5ncaj4hnta" host=www.mobapp.com request_id=6537152d-31dc-4a10-87f7-b05811a1cab0 fwd="98.234.89.85" dyno= connect= service= status=503 bytes=
2016-02-19T21:09:12.941530+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/sockjs/info?cb=xs2810gm5u" host=www.mobapp.com request_id=a66c3b26-7e28-4be4-8265-1823df31c731 fwd="98.234.89.85" dyno= connect= service= status=503 bytes=
2016-02-19T21:14:51.508051+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=www.mobapp.com request_id=64f988ab-b49c-4fc5-9131-049f15c0e3c1 fwd="98.234.89.85" dyno= connect= service= status=503 bytes=
2016-02-19T21:16:40.850757+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=www.mobapp.com request_id=b9c24f87-e849-43f5-83c9-e438b9dd4985 fwd="98.234.89.85" dyno= connect= service= status=503 bytes=
2016-02-19T21:16:38.941940+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=www.mobapp.com request_id=315428e1-9e3f-4d89-a3e4-0e66476fc1eb fwd="98.234.89.85" dyno= connect= service= status=503 bytes=
Did you provide MONGO_URL environment variable.
Something like:
export MONGO_URL=your_mongo_lab_url_here
Replace your_mongo_lab_url_here with your actual mongodb url. Hope this helps.

Heroku Sinatra Site Suddenly Down

Trying to get a beat on why my Heroku site won't load as I haven't touched in 6 months+
http://t2bthr.herokuapp.com
Below are the logs. Can anyone shed some light into this? I see this error:
/app/.gems/gems/mongo-1.3.0/lib/../lib/mongo/db.rb:130:in `issue_authentication': Failed to authenticate user 'heroku' on db 'app476164' (Mongo::AuthenticationError)
I'm just not sure why all the sudden I'd be having authentication issues.
2014-05-29T00:17:43.330292+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:11
2014-05-29T00:17:43.330293+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `instance_eval'
2014-05-29T00:17:43.330298+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `initialize'
2014-05-29T00:17:41.551293+00:00 heroku[web.1]: Starting process with command `thin -p 23291 -e production -R /home/heroku_rack/heroku.ru start`
2014-05-29T00:17:44.952612+00:00 heroku[web.1]: Process exited with status 1
2014-05-29T00:17:44.979544+00:00 heroku[web.1]: State changed from starting to crashed
2014-05-29T00:55:00.607805+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=2bthr.com request_id=a9823832-62fb-461c-a284-49968b44850e fwd="186.210.151.58" dyno= connect= service= status=503 bytes=
2014-05-29T01:03:17.147588+00:00 heroku[web.1]: State changed from crashed to starting
2014-05-29T01:03:19.495911+00:00 heroku[web.1]: Starting process with command `thin -p 7390 -e production -R /home/heroku_rack/heroku.ru start`
2014-05-29T01:03:22.751972+00:00 app[web.1]: Could not load SystemTimer >= v1.2.0. Falling back to timeout.rb. SystemTimer is STRONGLY recommended for timeouts in Ruby 1.8.7. See http://ph7spot.com/blog/system-timer-1-2-release for details.
2014-05-29T01:03:23.329833+00:00 app[web.1]: from /app/.gems/gems/mongo-1.3.0/lib/../lib/mongo/db.rb:111:in `authenticate'
2014-05-29T01:03:23.329806+00:00 app[web.1]: /app/.gems/gems/mongo-1.3.0/lib/../lib/mongo/db.rb:130:in `issue_authentication': Failed to authenticate user 'heroku' on db 'app476164' (Mongo::AuthenticationError)
2014-05-29T01:03:23.329874+00:00 app[web.1]: from ./bthr/app.rb:15
2014-05-29T01:03:23.329970+00:00 app[web.1]: from config.ru:4
2014-05-29T01:03:23.329854+00:00 app[web.1]: from ./bthr/../lib/db.rb:10:in `init_mongo'
2014-05-29T01:03:23.329914+00:00 app[web.1]: from ./bthr/app.rb:14
2014-05-29T01:03:23.329952+00:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
2014-05-29T01:03:23.330026+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `initialize'
2014-05-29T01:03:23.330045+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:63:in `new'
2014-05-29T01:03:23.329933+00:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
2014-05-29T01:03:23.329894+00:00 app[web.1]: from /app/.gems/gems/sinatra-1.2.2/lib/sinatra/base.rb:1222:in `configure'
2014-05-29T01:03:23.329989+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:23
2014-05-29T01:03:23.330008+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `instance_eval'
2014-05-29T01:03:23.330081+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:18
2014-05-29T01:03:23.330118+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `initialize'
2014-05-29T01:03:23.330063+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:63:in `map'
2014-05-29T01:03:23.330136+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:11:in `new'
2014-05-29T01:03:23.330100+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `instance_eval'
2014-05-29T01:03:23.330191+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `instance_eval'
2014-05-29T01:03:23.330155+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:11
2014-05-29T01:03:23.330211+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `initialize'
2014-05-29T01:03:23.330248+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:1
2014-05-29T01:03:23.330230+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:1:in `new'
2014-05-29T01:03:24.749727+00:00 heroku[web.1]: State changed from starting to crashed
2014-05-29T01:03:24.741605+00:00 heroku[web.1]: Process exited with status 1
2014-05-29T01:24:47.714571+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=2bthr.com request_id=037cebb1-d9eb-450e-97f1-e3846121d2b9 fwd="204.155.149.27" dyno= connect= service= status=503 bytes=
2014-05-29T01:31:12.690405+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=2bthr.com request_id=776fe43b-c755-47e7-b741-5a2ff59b1ee8 fwd="91.200.12.70" dyno= connect= service= status=503 bytes=
2014-05-29T01:31:13.714036+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/wp-login.php host=2bthr.com request_id=66ac2b17-b220-448a-ad98-d684bbdba67c fwd="91.200.12.70" dyno= connect= service= status=503 bytes=
2014-05-29T01:54:42.347628+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=2bthr.com request_id=6d6e97c9-467d-4598-a590-b9c595cc9204 fwd="198.204.249.34" dyno= connect= service= status=503 bytes=
2014-05-29T02:25:42.894295+00:00 heroku[web.1]: State changed from crashed to starting
2014-05-29T02:25:45.238484+00:00 heroku[web.1]: Starting process with command `thin -p 27261 -e production -R /home/heroku_rack/heroku.ru start`
2014-05-29T02:25:49.223844+00:00 app[web.1]: Could not load SystemTimer >= v1.2.0. Falling back to timeout.rb. SystemTimer is STRONGLY recommended for timeouts in Ruby 1.8.7. See http://ph7spot.com/blog/system-timer-1-2-release for details.
2014-05-29T02:25:49.446648+00:00 app[web.1]: /app/.gems/gems/mongo-1.3.0/lib/../lib/mongo/db.rb:130:in `issue_authentication': Failed to authenticate user 'heroku' on db 'app476164' (Mongo::AuthenticationError)
2014-05-29T02:25:49.446654+00:00 app[web.1]: from /app/.gems/gems/mongo-1.3.0/lib/../lib/mongo/db.rb:111:in `authenticate'
2014-05-29T02:25:49.446656+00:00 app[web.1]: from ./bthr/../lib/db.rb:10:in `init_mongo'
2014-05-29T02:25:49.446663+00:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
2014-05-29T02:25:49.446670+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:23
2014-05-29T02:25:49.446667+00:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
2014-05-29T02:25:49.446658+00:00 app[web.1]: from ./bthr/app.rb:15
2014-05-29T02:25:49.446659+00:00 app[web.1]: from /app/.gems/gems/sinatra-1.2.2/lib/sinatra/base.rb:1222:in `configure'
2014-05-29T02:25:49.446669+00:00 app[web.1]: from config.ru:4
2014-05-29T02:25:49.446673+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `initialize'
2014-05-29T02:25:49.446672+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `instance_eval'
2014-05-29T02:25:49.446675+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:63:in `new'
2014-05-29T02:25:49.446676+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:63:in `map'
2014-05-29T02:25:49.446678+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:18
2014-05-29T02:25:49.446683+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `initialize'
2014-05-29T02:25:49.446696+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:1:in `new'
2014-05-29T02:25:49.446661+00:00 app[web.1]: from ./bthr/app.rb:14
2014-05-29T02:25:49.446681+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `instance_eval'
2014-05-29T02:25:49.446754+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:1
2014-05-29T02:25:49.446686+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:11:in `new'
2014-05-29T02:25:49.446688+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:11
2014-05-29T02:25:49.446691+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `instance_eval'
2014-05-29T02:25:49.446692+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `initialize'
2014-05-29T02:25:50.718902+00:00 heroku[web.1]: State changed from starting to crashed
2014-05-29T02:25:50.711009+00:00 heroku[web.1]: Process exited with status 1
2014-05-29T05:06:51.450635+00:00 heroku[web.1]: State changed from crashed to starting
2014-05-29T05:06:54.632367+00:00 app[web.1]: Could not load SystemTimer >= v1.2.0. Falling back to timeout.rb. SystemTimer is STRONGLY recommended for timeouts in Ruby 1.8.7. See http://ph7spot.com/blog/system-timer-1-2-release for details.
2014-05-29T05:06:54.918788+00:00 app[web.1]: from ./bthr/../lib/db.rb:10:in `init_mongo'
2014-05-29T05:06:54.918790+00:00 app[web.1]: from ./bthr/app.rb:15
2014-05-29T05:06:54.918751+00:00 app[web.1]: from /app/.gems/gems/mongo-1.3.0/lib/../lib/mongo/db.rb:111:in `authenticate'
2014-05-29T05:06:54.918791+00:00 app[web.1]: from /app/.gems/gems/sinatra-1.2.2/lib/sinatra/base.rb:1222:in `configure'
2014-05-29T05:06:54.918794+00:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
2014-05-29T05:06:54.918736+00:00 app[web.1]: /app/.gems/gems/mongo-1.3.0/lib/../lib/mongo/db.rb:130:in `issue_authentication': Failed to authenticate user 'heroku' on db 'app476164' (Mongo::AuthenticationError)
2014-05-29T05:06:54.918793+00:00 app[web.1]: from ./bthr/app.rb:14
2014-05-29T05:06:54.918796+00:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
2014-05-29T05:06:54.918798+00:00 app[web.1]: from config.ru:4
2014-05-29T05:06:54.918799+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:23
2014-05-29T05:06:54.918802+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `initialize'
2014-05-29T05:06:54.918800+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `instance_eval'
2014-05-29T05:06:54.918803+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:63:in `new'
2014-05-29T05:06:54.918807+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `instance_eval'
2014-05-29T05:06:54.918806+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:18
2014-05-29T05:06:54.918808+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `initialize'
2014-05-29T05:06:54.918811+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:11
2014-05-29T05:06:54.918814+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `initialize'
2014-05-29T05:06:54.918810+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:11:in `new'
2014-05-29T05:06:54.918804+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:63:in `map'
2014-05-29T05:06:54.918816+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:1
2014-05-29T05:06:54.918815+00:00 app[web.1]: from /home/heroku_rack/heroku.ru:1:in `new'
2014-05-29T05:06:54.918812+00:00 app[web.1]: from /app/.gems/gems/rack-1.2.2/lib/rack/builder.rb:46:in `instance_eval'
2014-05-29T05:06:56.095995+00:00 heroku[web.1]: State changed from starting to crashed
2014-05-29T05:06:53.328857+00:00 heroku[web.1]: Starting process with command `thin -p 58046 -e production -R /home/heroku_rack/heroku.ru start`
2014-05-29T05:06:56.090088+00:00 heroku[web.1]: Process exited with status 1
2014-05-29T05:28:10.046206+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/?author=1 host=2bthr.com request_id=5792f655-69f8-4b48-860a-8780a01db388 fwd="94.102.53.194" dyno= connect= service= status=503 bytes=
2014-05-29T09:55:11.507149+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=2bthr.com request_id=170b4b0b-f566-4c5e-be01-f19c8f50cd85 fwd="105.237.54.93" dyno= connect= service= status=503 bytes=
2014-05-29T09:55:14.043513+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/favicon.ico host=2bthr.com request_id=fb065a48-8adf-4516-8313-67d50be49e11 fwd="105.237.54.93" dyno= connect= service= status=503 bytes=
2014-05-29T09:56:43.107933+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/ host=2bthr.com request_id=dc3f3987-2caa-4b73-80b8-062d2ace6fa5 fwd="150.70.97.119" dyno= connect= service= status=503 bytes=
2014-05-29T10:06:23.161084+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=HEAD path=/ host=2bthr.com request_id=7acf11a7-27f9-42ed-81ec-12d6a488b936 fwd="119.63.193.194" dyno= connect= service= status=503 bytes=
2014-05-29T10:21:06.786562+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path=/robots.txt host=www.2bthr.com request_id=0fcd52e8-98f6-426c-bf9a-8600159d5976 fwd="65.55.52.111" dyno= connect= service= status=503 bytes=
If you are using the MongoLab add-on (https://addons.heroku.com/mongolab), they recently announced that on May 22 and May 23, they would be resetting everyone's login credentials in response to the Heartbleed bug.
If you were not using the MONGOLAB_URI environment variable to connect to your database, but instead hard-coded your login URI, then your app would error out. To fix this, update your username and password. To prevent future errors like this in the future, create an additional database user and use that username and password wherever you use a hard-coded login.
Here is a post that describes some of the steps MongoLab has taken to address the issue:
http://blog.mongolab.com/2014/04/heartbleed-security-update/