I'm deploying a Rails (Rails v5.0.0.1) app to heroku. However when I try visiting the app it crashes with error code of H10. After googling for a while I tried restarting all dynos for the app as people suggest but it didn't work. What's even weirder is that I cannot run heroku run rails console to access the console, when I run that, it shows:
Usage:
rails new APP_PATH [options]
Options:
-r, [--ruby=PATH] # Path to the Ruby binary of your choice
# Default: /app/vendor/ruby-2.3.0/bin/ruby
-m, [--template=TEMPLATE] # Path to some application template (can be a filesystem path or URL)
-d, [--database=DATABASE] # Preconfigure for selected database (options: mysql/oracle/postgresql/sqlite3/frontbase/ibm_db/sqlserver/jdbcmysql/jdbcsqlite3/jdbcpostgresql/jdbc)
# Default: sqlite3
-j, [--javascript=JAVASCRIPT] # Preconfigure for selected JavaScript library
# Default: jquery
[--skip-gemfile], [--no-skip-gemfile] # Don't create a Gemfile
-B, [--skip-bundle], [--no-skip-bundle] # Don't run bundle install
-G, [--skip-git], [--no-skip-git] # Skip .gitignore file
[--skip-keeps], [--no-skip-keeps] # Skip source control .keep files
-M, [--skip-action-mailer], [--no-skip-action-mailer] # Skip Action Mailer files
-O, [--skip-active-record], [--no-skip-active-record] # Skip Active Record files...
Note that I can run heroku run rake db:migrate after pushing to heroku. Here's the logs:
2016-12-18T06:44:34.515479+00:00 heroku[web.1]: Process exited with status 127
2016-12-18T06:44:46.337848+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mighty-island-98480.herokuapp.com request_id=fd929087-20a6-4c20-b534-f14261d3de11 fwd="210.245.33.22" dyno= connect= service= status=503 bytes=
2016-12-18T06:44:46.757726+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=mighty-island-98480.herokuapp.com request_id=ff3d39de-e593-41d4-b8d1-26fa9befc27e fwd="203.205.28.130" dyno= connect= service= status=503 bytes=
2016-12-18T06:46:59.953430+00:00 heroku[web.1]: State changed from crashed to starting
2016-12-18T06:47:05.203056+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 26350 -e production`
2016-12-18T06:47:06.697360+00:00 app[web.1]: bash: bin/rails: No such file or directory
2016-12-18T06:47:06.797834+00:00 heroku[web.1]: State changed from starting to crashed
2016-12-18T06:47:06.798798+00:00 heroku[web.1]: State changed from crashed to starting
2016-12-18T06:47:06.775021+00:00 heroku[web.1]: Process exited with status 127
2016-12-18T06:47:11.275436+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 31405 -e production`
2016-12-18T06:47:13.273106+00:00 app[web.1]: bash: bin/rails: No such file or directory
2016-12-18T06:47:13.382651+00:00 heroku[web.1]: State changed from starting to crashed
2016-12-18T06:47:13.364125+00:00 heroku[web.1]: Process exited with status 127
2016-12-18T06:47:15.177482+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=mighty-island-98480.herokuapp.com request_id=838f042a-36fb-4b80-9dd1-68146388a2f9 fwd="203.205.28.130" dyno= connect= service= status=503 bytes=
2016-12-18T06:47:14.847769+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mighty-island-98480.herokuapp.com request_id=329ddb98-3588-4a7e-ba85-86f2ebb0c787 fwd="203.205.28.130" dyno= connect= service= status=503 bytes=
2016-12-18T06:47:17.892965+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mighty-island-98480.herokuapp.com request_id=64f4d85b-f4be-473b-886b-16bcbabcebb2 fwd="210.245.33.22" dyno= connect= service= status=503 bytes=
2016-12-18T06:47:18.158159+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=mighty-island-98480.herokuapp.com request_id=6f95c551-e2a1-4afd-aa6a-00344743d3d9 fwd="203.205.28.130" dyno= connect= service= status=503 bytes=
2016-12-18T06:47:35.998915+00:00 app[api]: Starting process with command `bundle exec rake rails console` by user yaphats280396#gmail.com
2016-12-18T06:47:42.534769+00:00 heroku[run.1014]: Awaiting client
2016-12-18T06:47:42.584498+00:00 heroku[run.1014]: Starting process with command `bundle exec rake rails console`
2016-12-18T06:47:42.560559+00:00 heroku[run.1014]: State changed from starting to up
2016-12-18T06:47:50.393316+00:00 heroku[run.1014]: Process exited with status 1
2016-12-18T06:47:50.411848+00:00 heroku[run.1014]: State changed from up to complete
2016-12-18T06:48:03.813169+00:00 app[api]: Starting process with command `rails console` by user yaphats280396#gmail.com
2016-12-18T06:48:09.475386+00:00 heroku[run.8367]: Awaiting client
2016-12-18T06:48:09.520745+00:00 heroku[run.8367]: Starting process with command `rails console`
2016-12-18T06:48:09.640673+00:00 heroku[run.8367]: State changed from starting to up
2016-12-18T06:48:14.736012+00:00 heroku[run.8367]: State changed from up to complete
2016-12-18T06:48:14.699247+00:00 heroku[run.8367]: Process exited with status 0
2016-12-18T06:52:47.096470+00:00 heroku[slug-compiler]: Slug compilation started
2016-12-18T06:55:24.601041+00:00 heroku[slug-compiler]: Slug compilation started
2016-12-18T06:58:02.189014+00:00 app[api]: Deploy 18728fe by user yaphats280396#gmail.com
2016-12-18T06:58:02.189014+00:00 app[api]: Release v6 created by user yaphats280396#gmail.com
2016-12-18T06:58:02.340404+00:00 heroku[slug-compiler]: Slug compilation started
2016-12-18T06:58:02.340411+00:00 heroku[slug-compiler]: Slug compilation finished
2016-12-18T06:58:02.437765+00:00 heroku[web.1]: State changed from crashed to starting
2016-12-18T06:58:07.513403+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 44886 -e production`
2016-12-18T06:58:09.081681+00:00 heroku[web.1]: Process exited with status 127
2016-12-18T06:58:08.964854+00:00 app[web.1]: bash: bin/rails: No such file or directory
2016-12-18T06:58:09.105664+00:00 heroku[web.1]: State changed from starting to crashed
2016-12-18T07:00:25.355827+00:00 heroku[web.1]: State changed from crashed to starting
2016-12-18T07:00:30.147971+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 52383 -e production`
2016-12-18T07:00:31.821352+00:00 app[web.1]: bash: bin/rails: No such file or directory
2016-12-18T07:00:31.890663+00:00 heroku[web.1]: State changed from starting to crashed
2016-12-18T07:00:31.872039+00:00 heroku[web.1]: Process exited with status 127
2016-12-18T07:01:45.326964+00:00 app[api]: Starting process with command `bundle exec rake db:migrate` by user yaphats280396#gmail.com
2016-12-18T07:01:50.459013+00:00 heroku[run.9961]: Awaiting client
2016-12-18T07:01:50.478532+00:00 heroku[run.9961]: Starting process with command `bundle exec rake db:migrate`
2016-12-18T07:01:50.751333+00:00 heroku[run.9961]: State changed from starting to up
2016-12-18T07:01:56.569373+00:00 heroku[run.9961]: Process exited with status 0
2016-12-18T07:01:56.582918+00:00 heroku[run.9961]: State changed from up to complete
2016-12-18T07:02:03.799642+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mighty-island-98480.herokuapp.com request_id=a886d9c7-771c-4bbc-b0ae-c69a9a2711eb fwd="203.205.28.130" dyno= connect= service= status=503 bytes=
2016-12-18T07:02:04.128488+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=mighty-island-98480.herokuapp.com request_id=b639d3fe-89b8-4e85-bec5-092711ab9177 fwd="203.205.28.130" dyno= connect= service= status=503 bytes=
2016-12-18T07:02:06.282079+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mighty-island-98480.herokuapp.com request_id=2a99589c-6000-464f-8d6e-15bca538bb84 fwd="210.245.33.22" dyno= connect= service= status=503 bytes=
2016-12-18T07:02:06.575156+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=mighty-island-98480.herokuapp.com request_id=b520a6ee-4bfa-4116-b535-ce00c641097c fwd="203.205.28.130" dyno= connect= service= status=503 bytes=
2016-12-18T07:02:23.077596+00:00 app[api]: Starting process with command `rails console` by user yaphats280396#gmail.com
2016-12-18T07:02:29.656336+00:00 heroku[run.4122]: Awaiting client
2016-12-18T07:02:29.734024+00:00 heroku[run.4122]: Starting process with command `rails console`
2016-12-18T07:02:29.759224+00:00 heroku[run.4122]: State changed from starting to up
2016-12-18T07:02:35.660219+00:00 heroku[run.4122]: State changed from up to complete
2016-12-18T07:02:35.644039+00:00 heroku[run.4122]: Process exited with status 0
2016-12-18T07:06:57.871793+00:00 app[api]: Starting process with command `rails console` by user yaphats280396#gmail.com
2016-12-18T07:07:04.028124+00:00 heroku[run.5253]: State changed from starting to up
2016-12-18T07:07:04.151355+00:00 heroku[run.5253]: Awaiting client
2016-12-18T07:07:04.186644+00:00 heroku[run.5253]: Starting process with command `rails console`
2016-12-18T07:07:09.461403+00:00 heroku[run.5253]: Process exited with status 0
2016-12-18T07:07:09.459229+00:00 heroku[run.5253]: State changed from up to complete
2016-12-18T07:08:01.251294+00:00 app[api]: Starting process with command `spring stop` by user yaphats280396#gmail.com
2016-12-18T07:08:06.994287+00:00 heroku[run.2057]: Awaiting client
2016-12-18T07:08:07.013915+00:00 heroku[run.2057]: Starting process with command `spring stop`
2016-12-18T07:08:07.238356+00:00 heroku[run.2057]: State changed from starting to up
2016-12-18T07:08:11.161840+00:00 heroku[run.2057]: State changed from up to complete
2016-12-18T07:08:11.142680+00:00 heroku[run.2057]: Process exited with status 1
2016-12-18T07:18:42.513123+00:00 heroku[slug-compiler]: Slug compilation started
2016-12-18T07:18:42.513132+00:00 heroku[slug-compiler]: Slug compilation finished
2016-12-18T07:18:42.641136+00:00 heroku[web.1]: State changed from crashed to starting
2016-12-18T07:18:42.376404+00:00 app[api]: Release v7 created by user yaphats280396#gmail.com
2016-12-18T07:18:42.376404+00:00 app[api]: Deploy 0f0c253 by user yaphats280396#gmail.com
2016-12-18T07:18:48.864292+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 56507 -e production`
2016-12-18T07:18:51.479943+00:00 heroku[web.1]: Process exited with status 127
2016-12-18T07:18:51.513045+00:00 heroku[web.1]: State changed from starting to crashed
2016-12-18T07:18:51.514288+00:00 heroku[web.1]: State changed from crashed to starting
2016-12-18T07:18:51.351956+00:00 app[web.1]: bash: bin/rails: No such file or directory
2016-12-18T07:18:56.601461+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 47201 -e production`
2016-12-18T07:18:58.427067+00:00 app[web.1]: bash: bin/rails: No such file or directory
2016-12-18T07:18:58.490908+00:00 heroku[web.1]: Process exited with status 127
2016-12-18T07:18:58.523092+00:00 heroku[web.1]: State changed from starting to crashed
2016-12-18T07:19:26.047830+00:00 app[api]: Starting process with command `bundle exec rake db:migrate` by user yaphats280396#gmail.com
2016-12-18T07:19:31.378985+00:00 heroku[run.4257]: Awaiting client
2016-12-18T07:19:31.407367+00:00 heroku[run.4257]: Starting process with command `bundle exec rake db:migrate`
2016-12-18T07:19:31.663915+00:00 heroku[run.4257]: State changed from starting to up
2016-12-18T07:19:37.609181+00:00 heroku[run.4257]: State changed from up to complete
2016-12-18T07:19:37.628694+00:00 heroku[run.4257]: Process exited with status 0
2016-12-18T07:19:47.465402+00:00 app[api]: Starting process with command `rails console` by user yaphats280396#gmail.com
2016-12-18T07:19:53.296424+00:00 heroku[run.8574]: Awaiting client
2016-12-18T07:19:53.460124+00:00 heroku[run.8574]: State changed from starting to up
2016-12-18T07:19:53.343683+00:00 heroku[run.8574]: Starting process with command `rails console`
2016-12-18T07:19:57.742878+00:00 heroku[run.8574]: State changed from up to complete
2016-12-18T07:19:57.727626+00:00 heroku[run.8574]: Process exited with status 0
2016-12-18T07:20:40.222378+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=mighty-island-98480.herokuapp.com request_id=221c14dd-1775-4891-83ce-e8a24678075f fwd="203.205.28.130" dyno= connect= service= status=503 bytes=
2016-12-18T07:20:40.532629+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=mighty-island-98480.herokuapp.com request_id=5b2ff337-7233-49bc-a4a8-6b8dd1d485ff fwd="203.205.28.130" dyno= connect= service= status=503 bytes=
I've deployed a couple of apps to Heroku before but never come across this weird situation. I will provide further files/details if needed.
I figured it out: I forgot to provide a Procfile for Puma
Related
I deployed .NET app on Heroku docker
deploying went good no error
but when I tried to open the app I'm getting error
tried a few things like created VAR named PORT and gave value 5000 doesn't workout
2023-01-22T12:30:50.674761+00:00 heroku[web.1]: Starting process with command `dotnet ./Muapp.dll --urls\=http://\*:5000`
2023-01-22T12:30:51.685276+00:00 app[web.1]: Welcome to Muapp!
2023-01-22T12:30:51.685567+00:00 app[web.1]:
2023-01-22T12:30:51.685571+00:00 app[web.1]:
2023-01-22T12:30:51.909353+00:00 app[web.1]: warn: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[60]
2023-01-22T12:30:51.909375+00:00 app[web.1]: Storing keys in a directory '/app/.aspnet/DataProtection-Keys' that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed.
2023-01-22T12:30:51.928587+00:00 app[web.1]: warn: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[35]
2023-01-22T12:30:51.928590+00:00 app[web.1]: No XML encryptor configured. Key {f5035bc0-d6dd-402b-92f8-51341dd3511a} may be persisted to storage in unencrypted form.
2023-01-22T12:30:54.638199+00:00 app[web.1]: info: Microsoft.Hosting.Lifetime[14]
2023-01-22T12:30:54.638211+00:00 app[web.1]: Now listening on: http://[::]:5000
2023-01-22T12:30:54.642119+00:00 app[web.1]: info: Microsoft.Hosting.Lifetime[0]
2023-01-22T12:30:54.642121+00:00 app[web.1]: Application started. Press Ctrl+C to shut down.
2023-01-22T12:30:54.642714+00:00 app[web.1]: info: Microsoft.Hosting.Lifetime[0]
2023-01-22T12:30:54.642715+00:00 app[web.1]: Hosting environment: Production
2023-01-22T12:30:54.642715+00:00 app[web.1]: info: Microsoft.Hosting.Lifetime[0]
2023-01-22T12:30:54.642716+00:00 app[web.1]: Content root path: /app
2023-01-22T12:31:50.857290+00:00 heroku[web.1]: Error R10 (Boot timeout) -> Web process failed to bind to $PORT within 60 seconds of launch
2023-01-22T12:31:50.888117+00:00 heroku[web.1]: Stopping process with SIGKILL
2023-01-22T12:31:51.047126+00:00 heroku[web.1]: Process exited with status 137
2023-01-22T12:31:51.113768+00:00 heroku[web.1]: State changed from starting to crashed
2023-01-22T13:53:20.502985+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=oby.herokuapp.com request_id=6e089f4e-52e2-4c32-b28f-efc7999777ac fwd="104.28.255.112" dyno= connect= service= status=503 bytes= protocol=https
2023-01-22T13:53:22.376963+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=oby.herokuapp.com request_id=824189c7-7244-4070-bccb-7af1b4584e78 fwd="104.28.255.112" dyno= connect= service= status=503 bytes= protocol=https
2023-01-22T13:53:27.109966+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=oby.herokuapp.com request_id=eb7e2b1b-37d4-471c-9514-43da912b827d fwd="104.28.255.112" dyno= connect= service= status=503 bytes= protocol=http
2023-01-22T13:53:28.779659+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=oby.herokuapp.com request_id=6c5c88ed-ac9a-4e70-b422-d0bf294baeb4 fwd="104.28.255.112" dyno= connect= service= status=503 bytes= protocol=http
Heroku assigns you a port that it wants you to listen on. That port is passed to you in an environment variable called PORT. So you can't decide that you want to listen on port 5000 as that will very likely not be the port Heroku assigns you.
When Heroku discovers that you haven't bound to the assigned port, it kills your container.
To bind to the correct port, change your startup command to
dotnet ./Muapp.dll --urls=http://*:${PORT}
I've been looking for few days many tutorials to try to find my solution but i just can't get it.
Overview :
Im building an Asp.net Core (3.1) app which i've set up for running on docker. My goal is to deploy it to heroku.
Problem :
I can make it work on local to try with a docker container run but when i deploy it to heroku (the image was created without troubles) i get the error screen message:
"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"
Setup
Heroku :
dyno in use : api /bin/sh -c ASPNETCORE_URLS\=http://*:\$PORT\ dotnet\
build pack : https://github.com/jincod/dotnetcore-buildpack
Code
Dockerfile
WORKDIR /src
COPY *.sln .
COPY Ecomm.UnitTests/*.csproj Ecomm.UnitTests/
COPY Ecomm.Api/*.csproj Ecomm.Api/
RUN dotnet restore
COPY . .
# testing
FROM build AS testing
WORKDIR /src/Ecomm.Api
RUN dotnet build
WORKDIR /src/Ecomm.UnitTests
RUN dotnet test
# publish
FROM build AS publish
WORKDIR /src/Ecomm.Api
RUN dotnet publish -c Release -o /src/publish
FROM mcr.microsoft.com/dotnet/core/aspnet:3.1 AS runtime
WORKDIR /src
COPY --from=publish /src/publish .
# heroku uses the following
CMD ASPNETCORE_URLS=http://*:$PORT dotnet Ecomm.Api.dll
Program.cs (default script)
public class Program
{
public static void Main(string[] args)
{
CreateHostBuilder(args).Build().Run();
}
public static IHostBuilder CreateHostBuilder(string[] args) =>
Host.CreateDefaultBuilder(args)
.ConfigureWebHostDefaults(webBuilder =>
{
webBuilder.UseStartup<Startup>();
});
}
Startup.cs (default script)
public class Startup
{
public Startup(IConfiguration configuration)
{
Configuration = configuration;
}
public IConfiguration Configuration { get; }
// This method gets called by the runtime. Use this method to add services to the container.
public void ConfigureServices(IServiceCollection services)
{
services.AddControllers();
}
// This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
{
if (env.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
else
{
app.UseExceptionHandler("/Error");
// The default HSTS value is 30 days. You may want to change this for production scenarios, see https://aka.ms/aspnetcore-hsts.
app.UseHsts();
}
app.UseHttpsRedirection();
app.UseRouting();
app.UseEndpoints(endpoints =>
{
endpoints.MapControllers();
});
}
}
Launchsettings.json
"Ecomm.Api": {
"commandName": "Project",
"launchBrowser": true,
"launchUrl": "/weatherforecast",
"applicationUrl": "https://localhost:5001;http://localhost:5000",
"environmentVariables": {
"ASPNETCORE_ENVIRONMENT": "Production"
}
}
Comparaison between running a container locally and deploy to heroku
Local interface
Heroku interface
methods used to push on Heroku container register:
docker login --username=_ --password=$HEROKU_API_KEY registry.heroku.com
heroku container:push api -a $HEROKU_APP_NAME --recursive
heroku container:release api -a $HEROKU_APP_NAME
Errors logs in heroku :
2020-01-18T14:53:32.255720+00:00 heroku[api.1]: State changed from crashed to starting
2020-01-18T14:53:35.853732+00:00 heroku[api.1]: Starting process with command `/bin/sh -c ASPNETCORE_URLS\=http://\*:\59573\ dotnet\ Ecomm.Api.dll`
2020-01-18T14:53:36.494742+00:00 heroku[api.1]: State changed from starting to up
2020-01-18T14:53:37.754733+00:00 app[api.1]: Hosting environment: Production
2020-01-18T14:53:37.754802+00:00 app[api.1]: Content root path: /src
2020-01-18T14:53:37.754925+00:00 app[api.1]: Now listening on: http://[::]:59573
2020-01-18T14:53:37.754946+00:00 app[api.1]: Application started. Press Ctrl+C to shut down.
2020-01-18T14:53:39.762409+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/" host=dariorega-ecomm-api.herokuapp.com request_id=7538ce41-5d5e-4081-b214-eb1e50fdcc6c fwd="188.155.40.41" dyno= connect= service= status=503 bytes= protocol=https
2020-01-18T14:53:40.075446+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/favicon.ico" host=dariorega-ecomm-api.herokuapp.com request_id=4f1ff94a-eb45-4301-9c3a-74ece82abe84 fwd="188.155.40.41" dyno= connect= service= status=503 bytes= protocol=https
2020-01-18T14:53:51.155230+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/api" host=dariorega-ecomm-api.herokuapp.com request_id=1cc3eeac-1ce5-4a67-82e0-ee680beecc90 fwd="188.155.40.41" dyno= connect= service= status=503 bytes= protocol=https
2020-01-18T14:53:51.440188+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/favicon.ico" host=dariorega-ecomm-api.herokuapp.com request_id=caa51bcd-a153-444b-88b5-c024d1b2ae84 fwd="188.155.40.41" dyno= connect= service= status=503 bytes= protocol=https
2020-01-18T14:53:56.045125+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/weatherforecast" host=dariorega-ecomm-api.herokuapp.com request_id=bcdc8195-9da6-4258-a48b-4614d885302a fwd="188.155.40.41" dyno= connect= service= status=503 bytes= protocol=https
2020-01-18T14:53:56.292724+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/favicon.ico" host=dariorega-ecomm-api.herokuapp.com request_id=2329aa44-bdb0-43e3-bbbf-58bd87a09f8c fwd="188.155.40.41" dyno= connect= service= status=503 bytes= protocol=https
Logs i get in local container :
after running a docker container run with that same dockerfile :
info: Microsoft.Hosting.Lifetime[0]
Now listening on: http://[::]:5000
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
Content root path: /src
warn: Microsoft.AspNetCore.HttpsPolicy.HttpsRedirectionMiddleware[3]
Failed to determine the https port for redirect
But it works
Conclusion
I've tried many things in the docker file or to edit the program.cs defining useUrl methods but i still can't make it work. I don't know if something is related beceause of the http /https process since the https isnt setup/working. And heroku use https.
Or should i define an url somehwere ?, any help welcome !
Thanks in advance for your time taken reading this
Try to setup HttpsRedirection https://github.com/jincod/AspNetCoreDemoApp/blob/master/src/AspNetCoreDemoApp/Startup.cs#L13 and ForwardedHeadersOptions https://github.com/jincod/AspNetCoreDemoApp/blob/master/src/AspNetCoreDemoApp/Startup.cs#L23-L29
P.S.: you use container deployment without dotnetcore-buildpack:)
I got the couchdb image from docker (https://hub.docker.com/_/couchdb) and then i run the follow commands:
docker run -p 5984:5984 -d --name my-couchdb2 couchdb:latest
docker commit 1d329ef7c516 registry.heroku.com/coucherte/web
docker tag my-couchdb2 registry.heroku.com/coucherte/web
docker push registry.heroku.com/coucherte/web
heroku container:release web --app coucherte
After this the dyno crashes, with "heroku logs --app coucherte" i get this log:
2019-02-28T17:55:15.064991+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=coucherte.herokuapp.com request_id=b875a9ce-6b45-4e37-b0fa-9a0ff243b5de fwd="177.251.168.219" dyno= connect= service= status=503 bytes= protocol=http
2019-02-28T17:55:15.542527+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/favicon.ico" host=coucherte.herokuapp.com request_id=291c7afd-0e7d-41f2-846e-6555dbdb4621 fwd="177.251.168.219" dyno= connect= service= status=503 bytes= protocol=http
2019-02-28T18:00:23.647796+00:00 heroku[web.1]: State changed from crashed to starting
2019-02-28T18:00:27.580280+00:00 heroku[web.1]: Starting process with command `/opt/couchdb/bin/couchdb`
2019-02-28T18:00:28.727119+00:00 heroku[web.1]: State changed from starting to crashed
2019-02-28T18:00:28.670713+00:00 app[web.1]: [WARN tini (4)] Tini is not running as PID 1 and isn't registered as a child subreaper.
2019-02-28T18:00:28.670738+00:00 app[web.1]: Zombie processes will not be re-parented to Tini, so zombie reaping won't work.
2019-02-28T18:00:28.670753+00:00 app[web.1]: To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1.
2019-02-28T18:00:28.674975+00:00 app[web.1]: find: 'couchdb' is not the name of a known user
2019-02-28T18:00:28.727539+00:00 heroku[web.1]: Process exited with status 1
2019-02-28T18:02:42.410954+00:00 heroku[web.1]: State changed from crashed to starting
2019-02-28T18:02:51.032603+00:00 heroku[web.1]: Starting process with command `/opt/couchdb/bin/couchdb`
2019-02-28T18:02:53.540759+00:00 heroku[web.1]: State changed from starting to crashed
2019-02-28T18:02:53.517057+00:00 heroku[web.1]: Process exited with status 1
2019-02-28T18:02:53.453924+00:00 app[web.1]: [WARN tini (4)] Tini is not running as PID 1 and isn't registered as a child subreaper.
2019-02-28T18:02:53.453944+00:00 app[web.1]: Zombie processes will not be re-parented to Tini, so zombie reaping won't work.
2019-02-28T18:02:53.453960+00:00 app[web.1]: To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini as a child subreaper, or run Tini as PID 1.
2019-02-28T18:02:53.454218+00:00 app[web.1]: find: 'couchdb' is not the name of a known user
What i am doing wrong? How i have to change the PORT for Heroku? Do i have to change couchdb settings to work with HTTPS when working with Heroku?
UPDATE
I now figured out that inside the image in the root directory there is a file called docker-entrypoint.sh. In this file there is this line:
find /opt/couchdb \! \( -user couchdb -group couchdb \) -exec chown -f couchdb:couchdb '{}' +
So on this line i think it crashes in heroku. So there is a problem with the user couchdb. Localy it works and i can find the user with:
cut -d: -f1 /etc/passwd
but on heroku the user does not exist or cannot be found. Why?
UPDATE 2
The answer is here: https://github.com/apache/couchdb-docker/issues/136
I am trying to deploy an app https://github.com/valasek/timesheet on Heroku using a docker image.
App has a go backend (negroni/gorilla) and Vue.js/Vuetify.js on the frontend and is using PostgreSQL persistence.
I am stuck on deployment. I do not know how to debug, how to show the command line output, what is failing ... and any help highly appreciated.
Relevant Dockerfile - https://github.com/valasek/timesheet/blob/master/Dockerfile
Here are the steps I am doing:
> docker build --rm -f "Dockerfile" -t timesheet:latest .
Successfully tagged timesheet:latest
...
> heroku container:push timesheet:latest --app timesheet-cloud
...
The push refers to repository [registry.heroku.com/timesheet-cloud/timesheet]
...
Your image has been successfully pushed. You can now release it with the 'container:release' command.
> heroku container:release timesheet --app timesheet-cloud
Releasing images timesheet to timesheet-cloud... done
> heroku ps -a timesheet-cloud
Free dyno hours quota remaining this month: 971h 8m (97%)
Free dyno usage for this app: 0h 0m (0%)
For more information on dyno sleeping and how to upgrade, see:
https://devcenter.heroku.com/articles/dyno-sleeping
No dynos on ⬢ timesheet-cloud
> heroku logs --app timesheet-cloud
2019-02-15T08:33:49.373221+00:00 app[api]: Deployed timesheet (709022e100f9) by user <email-reducted>#gmail.com
2019-02-15T08:33:49.373221+00:00 app[api]: Release v20 created by user <email-reducted>#gmail.com
2019-02-15T08:34:43.901070+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/" host=timesheet-cloud.herokuapp.com request_id=4c21eb79-5344-4d40-b341-8977128c873f fwd="195.250.152.42" dyno= connect= service= status=503 bytes= protocol=https
2019-02-15T08:34:44.842322+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/favicon.ico" host=timesheet-cloud.herokuapp.com request_id=b66caaee-880a-46a0-918b-e778a49334f4 fwd="195.250.152.42" dyno= connect= service= status=503 bytes= protocol=https
2019-02-15T08:34:54.865321+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/" host=timesheet-cloud.herokuapp.com request_id=d5af6aa7-0279-4f0e-a4cc-0f9e8682ec2f fwd="195.250.152.42" dyno= connect= service= status=503 bytes= protocol=https
2019-02-15T08:34:55.158317+00:00 heroku[router]: at=error code=H14 desc="No web processes running" method=GET path="/favicon.ico" host=timesheet-cloud.herokuapp.com request_id=2d69f4b5-9015-48de-9314-c493703818d1 fwd="195.250.152.42" dyno= connect= service= status=503 bytes= protocol=https
This is likely to happen because Heroku does not detect any endpoint for your application (binded on port 3000 by default).
Heroku attributes your app a dynamic port, and put the port value on the env variable named $PORT.
Your app have to use the value specified by Heroku in this variable and listen for incoming connections on it, because that is where Heroku will forward connections.
The variable has to be read when the app starts:
https://help.heroku.com/PPBPA231/how-do-i-use-the-port-environment-variable-in-container-based-apps
You can check current env variables on your app using heroku run printenv
(I see you are using Viper, that should handle env variables. However they say in their documentation that when from env, it is case sensitive, maybe that could explain why it does not work for you: https://github.com/spf13/viper#working-with-environment-variables)
Thank you #Jonathan Muller. Solved!
GUI is running on https://timesheet-cloud.herokuapp.com.
On Heroku DB connection and PORT string should be read from the environment variables
DATABASE_URL
PORT
Updated was file timesheet.yaml.
BaseUrl in Axios is set to '' so Axios is using relative API URLs, which works. Fixed in file axiosSettings.js.
Before the command heroku run printenv returned:
panic: dial tcp 127.0.0.1:5432: connect: connection refused
Now I am getting:
Running printenv on ⬢ timesheet-cloud... up, run.1962 (Free)
Feb 15 16:22:34.186 [INFO] config file /timesheet.yaml
Feb 15 16:22:34.197 [INFO] connecting to DB postgres://user:hash#ec2-54-235-68-3.compute-1.amazonaws.com:5432/dbname
Feb 15 16:22:34.246 [INFO] connected to DB postgres://user:hash#ec2-54-235-68-3.compute-1.amazonaws.com:5432/dbname
I am doing my first deployment to Heroku and I have an Application Error. It reads
An error occurred in the application and your page could not be served. Please try again in a few moments.
I have added the pg to gemfile and followed the setup for puma web server.
Does someone know how I can fix this? I've looked around and read other posts but none of those solutions seem to be able to fix what's going on with me.
2015-06-23T06:08:05.135418+00:00 app[web.1]: bash: bin/rails: No such file or directory
2015-06-23T06:08:05.857563+00:00 heroku[web.1]: State changed from starting to crashed
2015-06-23T06:08:05.845406+00:00 heroku[web.1]: Process exited with status 127
2015-06-23T07:39:56.871349+00:00 heroku[web.1]: State changed from crashed to starting
2015-06-23T07:40:07.045897+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 52445 -e production`
2015-06-23T07:40:09.416565+00:00 heroku[web.1]: State changed from starting to crashed
2015-06-23T07:40:09.406842+00:00 heroku[web.1]: Process exited with status 127
2015-06-23T07:40:08.580332+00:00 app[web.1]: bash: bin/rails: No such file or directory
2015-06-23T11:06:31.005547+00:00 heroku[web.1]: State changed from crashed to starting
2015-06-23T11:06:40.489918+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 45824 -e production`
2015-06-23T11:06:41.944126+00:00 app[web.1]: bash: bin/rails: No such file or directory
2015-06-23T11:06:42.728921+00:00 heroku[web.1]: State changed from starting to crashed
2015-06-23T11:06:42.716580+00:00 heroku[web.1]: Process exited with status 127
2015-06-23T19:27:47.611339+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/robots.txt" host=areyoutaken.herokuapp.com request_id=1c5dc120-24d1-4823-9283-3c396d899d41 fwd="157.55.39.235" dyno= connect= service= status=503 bytes=
2015-06-23T19:27:56.576248+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=areyoutaken.herokuapp.com request_id=ffe06a2f-7fe2-4dd9-8fac-199aa9ce48b0 fwd="157.55.39.235" dyno= connect= service= status=503 bytes=
2015-06-23T19:47:05.610561+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=areyoutaken.herokuapp.com request_id=38597d3a-750c-4ff4-8384-67de523c6226 fwd="73.54.214.248" dyno= connect= service= status=503 bytes=
2015-06-24T03:34:44.769597+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=areyoutaken.herokuapp.com request_id=855033cb-e6db-4a3d-9346-f7a6ef7b7a28 fwd="73.54.214.248" dyno= connect= service= status=503 bytes=
2015-06-24T03:34:47.517061+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=areyoutaken.herokuapp.com request_id=e99f4acd-fed1-4b8f-9037-94747cbc567b fwd="73.54.214.248" dyno= connect= service= status=503 bytes=
2015-06-24T03:43:15.864729+00:00 heroku[api]: Starting process with command `false && AUTOMATED DIAGNOSIS BEING RUN BY HEROKU SUPPORT; cat Procfile` by
2015-06-24T03:43:25.864817+00:00 heroku[run.4070]: Awaiting client
2015-06-24T03:43:25.891312+00:00 heroku[run.4070]: Starting process with command `false && AUTOMATED DIAGNOSIS BEING RUN BY HEROKU SUPPORT; cat Procfile`
2015-06-24T03:43:26.288537+00:00 heroku[run.4070]: State changed from starting to up
2015-06-24T03:43:27.558053+00:00 heroku[api]: Starting process with command `false && AUTOMATED DIAGNOSIS BEING RUN BY HEROKU SUPPORT; cat Gemfile` by
2015-06-24T03:43:28.191980+00:00 heroku[run.4070]: Process exited with status 1
2015-06-24T03:43:28.214454+00:00 heroku[run.4070]: State changed from up to complete
2015-06-24T03:43:37.193534+00:00 heroku[run.2198]: Starting process with command `false && AUTOMATED DIAGNOSIS BEING RUN BY HEROKU SUPPORT; cat Gemfile`
2015-06-24T03:43:37.159595+00:00 heroku[run.2198]: Awaiting client
2015-06-24T03:43:37.655722+00:00 heroku[run.2198]: State changed from starting to up
2015-06-24T03:43:38.924101+00:00 heroku[api]: Starting process with command `false && AUTOMATED DIAGNOSIS BEING RUN BY HEROKU SUPPORT; cat Gemfile.lock` by
2015-06-24T03:43:39.577465+00:00 heroku[run.2198]: Process exited with status 0
2015-06-24T03:43:39.584141+00:00 heroku[run.2198]: State changed from up to complete
2015-06-24T03:43:48.245771+00:00 heroku[run.5907]: Awaiting client
2015-06-24T03:43:48.289767+00:00 heroku[run.5907]: Starting process with command `false && AUTOMATED DIAGNOSIS BEING RUN BY HEROKU SUPPORT; cat Gemfile.lock`
2015-06-24T03:43:48.504068+00:00 heroku[run.5907]: State changed from starting to up
2015-06-24T03:43:49.678442+00:00 heroku[api]: Starting process with command `false && AUTOMATED DIAGNOSIS BEING RUN BY HEROKU SUPPORT; cat config/unicorn.rb` by
2015-06-24T03:43:50.294772+00:00 heroku[run.5907]: State changed from up to complete
2015-06-24T03:43:50.260085+00:00 heroku[run.5907]: Process exited with status 0
2015-06-24T03:43:58.833931+00:00 heroku[run.9140]: Awaiting client
2015-06-24T03:43:58.873519+00:00 heroku[run.9140]: Starting process with command `false && AUTOMATED DIAGNOSIS BEING RUN BY HEROKU SUPPORT; cat config/unicorn.rb`
2015-06-24T03:43:59.122398+00:00 heroku[run.9140]: State changed from starting to up
2015-06-24T03:44:00.508136+00:00 heroku[api]: Starting process with command `false && AUTOMATED DIAGNOSIS BEING RUN BY HEROKU SUPPORT; cat config/puma.rb` by
2015-06-24T03:44:01.467150+00:00 heroku[run.9140]: Process exited with status 1
2015-06-24T03:44:01.478969+00:00 heroku[run.9140]: State changed from up to complete
2015-06-24T03:44:20.474134+00:00 heroku[run.8902]: Awaiting client
2015-06-24T03:44:20.555661+00:00 heroku[run.8902]: Starting process with command `false && AUTOMATED DIAGNOSIS BEING RUN BY HEROKU SUPPORT; cat config/puma.rb`
2015-06-24T03:44:20.712591+00:00 heroku[run.8902]: State changed from starting to up
2015-06-24T03:44:22.491184+00:00 heroku[api]: Starting process with command `false && AUTOMATED DIAGNOSIS BEING RUN BY HEROKU SUPPORT; cat config/initializers/timeout.rb` by
2015-06-24T03:44:23.203713+00:00 heroku[run.8902]: Process exited with status 1
2015-06-24T03:44:23.233656+00:00 heroku[run.8902]: State changed from up to complete
2015-06-24T03:44:32.457146+00:00 heroku[run.9448]: Awaiting client
2015-06-24T03:44:32.507243+00:00 heroku[run.9448]: Starting process with command `false && AUTOMATED DIAGNOSIS BEING RUN BY HEROKU SUPPORT; cat config/initializers/timeout.rb`
2015-06-24T03:44:32.756976+00:00 heroku[run.9448]: State changed from starting to up
2015-06-24T03:44:34.110457+00:00 heroku[api]: Starting process with command `false && AUTOMATED DIAGNOSIS BEING RUN BY HEROKU SUPPORT; cat config/initializers/database_connection.rb` by
2015-06-24T03:44:34.809918+00:00 heroku[run.9448]: State changed from up to complete
2015-06-24T03:44:34.793131+00:00 heroku[run.9448]: Process exited with status 1
2015-06-24T03:44:44.529225+00:00 heroku[run.2356]: Awaiting client
2015-06-24T03:44:44.556511+00:00 heroku[run.2356]: Starting process with command `false && AUTOMATED DIAGNOSIS BEING RUN BY HEROKU SUPPORT; cat config/initializers/database_connection.rb`
2015-06-24T03:44:44.822631+00:00 heroku[run.2356]: State changed from starting to up
2015-06-24T03:44:46.004603+00:00 heroku[api]: Starting process with command `false && AUTOMATED DIAGNOSIS BEING RUN BY HEROKU SUPPORT; cat config/environments/production.rb` by
2015-06-24T03:44:46.603524+00:00 heroku[run.2356]: Process exited with status 1
2015-06-24T03:44:46.597452+00:00 heroku[run.2356]: State changed from up to complete
2015-06-24T03:44:54.417247+00:00 heroku[run.7130]: Awaiting client
2015-06-24T03:44:54.475518+00:00 heroku[run.7130]: Starting process with command `false && AUTOMATED DIAGNOSIS BEING RUN BY HEROKU SUPPORT; cat config/environments/production.rb`
2015-06-24T03:44:54.774410+00:00 heroku[run.7130]: State changed from starting to up
2015-06-24T03:44:56.747720+00:00 heroku[run.7130]: Process exited with status 0
2015-06-24T03:44:56.759805+00:00 heroku[run.7130]: State changed from up to complete
2015-06-24T09:30:26.772688+00:00 heroku[web.1]: State changed from crashed to starting
2015-06-24T09:30:37.719614+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 56552 -e production`
2015-06-24T09:30:39.822774+00:00 app[web.1]: bash: bin/rails: No such file or directory
2015-06-24T09:30:40.715770+00:00 heroku[web.1]: State changed from starting to crashed
2015-06-24T09:30:40.694675+00:00 heroku[web.1]: Process exited with status 127
2015-06-24T12:58:54.912618+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/robots.txt" host=areyoutaken.herokuapp.com request_id=586e8274-8b09-4fa7-922b-de3dbaac1ce7 fwd="157.55.39.153" dyno= connect= service= status=503 bytes=
2015-06-24T12:59:09.862623+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=areyoutaken.herokuapp.com request_id=2d1999bb-cf85-40af-b477-8c05dcca74a9 fwd="157.55.39.154" dyno= connect= service= status=503 bytes=
2015-06-24T14:13:48.499735+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=areyoutaken.herokuapp.com request_id=c0e307ba-f974-4834-b4f8-ab50c4f8c52a fwd="207.46.13.64" dyno= connect= service= status=503 bytes=
2015-06-24T14:48:17.955631+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=areyoutaken.herokuapp.com request_id=c3815567-dafa-4524-b82c-3663b18cbb54 fwd="157.55.39.78" dyno= connect= service= status=503 bytes=
2015-06-24T15:27:49.824212+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=areyoutaken.herokuapp.com request_id=b56c868b-9733-42d8-a654-64f688297124 fwd="157.55.39.78" dyno= connect= service= status=503 bytes=
2015-06-24T16:41:13.827034+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=areyoutaken.herokuapp.com request_id=eab5322d-303d-4ba3-843c-855676ab8d19 fwd="157.55.39.154" dyno= connect= service= status=503 bytes=
2015-06-24T18:21:42.899175+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=areyoutaken.herokuapp.com request_id=d8f211e6-2d7a-4d24-b6f1-a75e121ba8e6 fwd="157.55.39.5" dyno= connect= service= status=503 bytes=
2015-06-24T21:18:51.904467+00:00 heroku[api]: Set MAX_THREADS config vars by
2015-06-24T21:18:51.904467+00:00 heroku[api]: Release v6 created by
2015-06-24T21:18:52.025225+00:00 heroku[web.1]: State changed from crashed to starting
2015-06-24T21:19:02.708240+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 55492 -e production`
2015-06-24T21:19:04.412120+00:00 app[web.1]: bash: bin/rails: No such file or directory
2015-06-24T21:19:05.233124+00:00 heroku[web.1]: State changed from starting to crashed
2015-06-24T21:19:05.234307+00:00 heroku[web.1]: State changed from crashed to starting
2015-06-24T21:19:05.221340+00:00 heroku[web.1]: Process exited with status 127
2015-06-24T21:19:12.614653+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 44814 -e production`
2015-06-24T21:19:15.139278+00:00 app[web.1]: bash: bin/rails: No such file or directory
2015-06-24T21:19:15.849254+00:00 heroku[web.1]: Process exited with status 127
2015-06-24T21:19:15.868089+00:00 heroku[web.1]: State changed from starting to crashed
2015-06-24T21:20:22.629350+00:00 heroku[api]: Set MIN_THREADS config vars by
2015-06-24T21:20:22.629350+00:00 heroku[api]: Release v7 created by
2015-06-24T21:20:22.741201+00:00 heroku[web.1]: State changed from crashed to starting
2015-06-24T21:20:36.211995+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 21287 -e production`
2015-06-24T21:20:38.504385+00:00 app[web.1]: bash: bin/rails: No such file or directory
2015-06-24T21:20:39.497977+00:00 heroku[web.1]: Process exited with status 127
2015-06-24T21:20:39.506527+00:00 heroku[web.1]: State changed from starting to crashed
2015-06-24T21:20:54.735772+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=areyoutaken.herokuapp.com request_id=e476ba5f-9607-4d86-b7e5-d42f84d44252 fwd="73.54.214.248" dyno= connect= service= status=503 bytes=
2015-06-24T21:20:55.912874+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=areyoutaken.herokuapp.com request_id=70352214-654e-417e-8d42-82c302bb53eb fwd="73.54.214.248" dyno= connect= service= status=503 bytes=
2015-06-24T21:23:31.726199+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=areyoutaken.herokuapp.com request_id=a6cb8ae0-841e-4fc1-ab35-084ac9822e90 fwd="73.54.214.248" dyno= connect= service= status=503 bytes=
2015-06-24T21:23:34.015037+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path="/" host=areyoutaken.herokuapp.com request_id=9b038059-df69-479a-b843-398ec4c4dc8e fwd="73.54.214.248" dyno= connect= service= status=503 bytes=
Do you have a Procfile at the root of your directory? Current heroku dev docs recommend having one to tell heroku how to start your application.
Try including "web: bundle exec puma -C config/puma.rb" in a Procfile.