Puma giving trouble deploying the application to Hetzner

Hi All,
I had the JumpStart Pro running fine on Hetzner cloud using Linux 18.04 which was not updated since last 6 months. Yesterday I pulled all new changes from JumpStart Pro and it suddenly broke my application. I see one of the major change is Puma from 4.3 to 5.0. After lots of tweaking I was unsuccessful so restore my server for older version using Puma 4.3, however still facing issues.
I am getting following errors:

 using conf file /home/subrat/app/shared/puma.rb
      01 $HOME/.rbenv/bin/rbenv exec bundle exec puma -C /home/subrat/app/shared/puma.rb --daemon
      01 [2796] Puma starting in cluster mode...
      01 [2796] * Version 4.3.5 (ruby 2.7.1-p83), codename: Mysterious Traveller
      01 [2796] * Min threads: 4, max threads: 16
      01 [2796] * Environment: production
      01 [2796] * Process workers: 2
      01 [2796] * Preloading application
      01 [2796] ! Unable to load application: NameError: uninitialized constant Noticed
      01 bundler: failed to load command: puma (/home/subrat/app/shared/bundle/ruby/2.7.0/bin/puma)
      01 NameError: uninitialized constant Noticed

/home/subrat/app/releases/20201125052249/app/channels/notification_channel.rb:1:in `<main>'
xxx
xxx
xxx
  /home/subrat/app/shared/bundle/ruby/2.7.0/bin/puma:23:in `<top (required)>'
puma stderr: Nothing written
** DEPLOY FAILED
** Refer to log/capistrano.log for details. Here are the last 20 lines:


Not sure what I am doing wrong. Is there any documentation on how to deploy Jumpstart to a Linux Box?

Still have the Noticed gem in your Gemfile?

Hi Chris, I was able to solve the issue by downgrading the Puma Gem from 5.0 to 4.3. Is there any documentation on how to use Puma Gem 5.0 as it perhaps require installing Puma gem on remote server?