Internal Server Error 500 after closing server

Hello, I am quite new to Ruby on Rails, so bare with me.
I just made an Ruby on Rails basic blog app with the help of a tutorial and everything was working fine until I closed the server with Ctrl+C and did yes on Terminate Batch Job. Now when I reopen the server with rails s/ rails server, I get "
We’re sorry, but something went wrong.
If you are the application owner check the logs for more information."
and Internal Server Error 500 in the console.

Here is the full log from the console:
D:\Sites\justinblogs>rails server
=> Booting Puma
=> Rails 6.0.1 application starting in development
=> Run rails server --help for more startup options
*** SIGUSR2 not implemented, signal based restart unavailable!
*** SIGUSR1 not implemented, signal based restart unavailable!
*** SIGHUP not implemented, signal based logs reopening unavailable!
Puma starting in single mode…

  • Version 4.3.1 (ruby 2.6.5-p114), codename: Mysterious Traveller
  • Min threads: 5, max threads: 5
  • Environment: development
  • Listening on tcp://[::1]:3000
  • Listening on tcp://
    Use Ctrl-C to stop
    Started GET “/” for ::1 at 2019-12-10 22:55:12 +0200
    (2.9ms) SELECT sqlite_version()
    (0.2ms) SELECT “schema_migrations”.“version” FROM “schema_migrations” ORDER BY “schema_migrations”.“version” ASC
    Processing by PostsController#index as HTML
    Rendering posts/index.html.erb within layouts/application
    Post Load (0.3ms) SELECT “posts”.
    FROM “posts”
    ↳ app/views/posts/index.html.erb:5
    Rendered posts/index.html.erb within layouts/application (Duration: 9.7ms | Allocations: 4739)
    [Webpacker] Everything’s up-to-date. Nothing to do
    Completed 500 Internal Server Error in 180ms (ActiveRecord: 1.0ms | Allocations: 17503)

What actions did you take before your server stopped working? I advise you to roll back to the time when everything worked properly. If you have solved your problem, share here so that other visitors can solve a similar problem. I also advise you to monitor the server and collect statistics This will allow you to quickly respond to malfunctions and find the reasons for the collected data.