# Getting Past strscan Gem Issues in Rails

DevFeed: [Getting Past strscan Gem Issues in Rails](<https://devfeed.tech/articles/getting-past-strscan-gem-issues-in-rails-28285.md>)

Original publisher: [Read original article](<http://fuzzyblog.io/blog/rails/2022/06/23/getting-past-strscan-gem-issues-in-rails.html>)

Author: Fuzzygroup

Published: 2022-06-23T07:51:00Z

Content type: tutorial

Language: en

Sources: [Scott Johnson](<https://devfeed.tech/sources/scott-johnson.md>)

Topics: [Rails](<https://devfeed.tech/topics/rails.md>), [Ruby](<https://devfeed.tech/topics/ruby.md>), [nginx](<https://devfeed.tech/topics/nginx.md>), [configuration](<https://devfeed.tech/topics/configuration.md>)

Tags: [cartazzi](<https://devfeed.tech/tags/cartazzi.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [deploy](<https://devfeed.tech/tags/deploy.md>), [hatchbox](<https://devfeed.tech/tags/hatchbox.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [rails](<https://devfeed.tech/tags/rails.md>), [ruby](<https://devfeed.tech/tags/ruby.md>), [ssh](<https://devfeed.tech/tags/ssh.md>)

## AI overview

This troubleshooting article explains how a Rails 7.0.3 deployment on HatchBox failed because the application had activated strscan 3.0.1 while the Gemfile required 3.0.3. After other suggested fixes failed, adding a Passenger-level Bundler configuration through HatchBox's custom NGINX configuration resolved the problem.

## Source excerpt

Yesterday I deployed a new thing via HatchBox and I was using the very, very latest - Rails 7.0.3. My deploy was textbook perfect and then I viewed it in Chrome and got that awful, awful message: Web application could not be started Insert loud cursing here I know the drill - it is a lower level error than HatchBox can handle (although I can think of at least a few ways HatchBox could handle it) - so do the dance: SSH into the box sudo su tail -f /var/log/nginx/error.log Read the error, google and assess. Here was the error: root@cartazzi3-web1:/home/deploy/Cartazzi/releases/20220608082805# tail -f /var/log/nginx/error.log App 14330 output: /usr/share/passenger/helper-scripts/rack-preloader.rb:189:in `block in <module:App>' App 14330 output: /usr/lib/ruby/vendor_ruby/phusion_passenger/loader_shared_helpers.rb:397:in `run_block_and_record_step_progress' App 14330 output: /usr/share/passenger/helper-scripts/rack-preloader.rb:188:in `<module:App>' App 14330 output: /usr/share/passenger/helper-scripts/rack-preloader.rb:30:in `<module:PhusionPassenger>' App 14330 output: /usr/share/passenger/helper-scripts/rack-preloader.rb:29:in `<main>' [ E 2022-06-22 15:04:13.2231 21017/T9t age/Cor/App/Implementation.cpp:221 ]: Could not spawn process for application /home/deploy/cartazzi_marketing/current: The application encountered the following error: You have already activated strscan 3.0.1, but your Gemfile requires strscan 3.0.3. Since strscan is a default gem, you can either remove your dependency on it or try updating to a newer version of bundler that supports strscan as a default gem. (Gem::LoadError) Error ID: 9a03b9ce Error details saved to: /tmp/passenger-error-pO6ZTu.html The normal googling suggested things like: Update strscan on the host system Mess with Gemfile Mess with Gemfile.lock Add a Passenger level configuration var for bundler I'd give citations for these but Chrome just crashed and it is closing in on 4 am and the weariness in my bones doesn't allow me to r