-
Notifications
You must be signed in to change notification settings - Fork 548
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uninitialized constant Rackup::Handler::Rack (NameError) [Rack 3] #2508
Comments
I'm getting this same issue:
EDIT Even down to version 6.0.0 or even 5.3.7 |
I'm getting this on Ruby 3.2, Rails 7.1 and latest Passenger 6.0.20. |
Any update on this? |
Yes, I've investigated this, and unfortunately it won't be fixable in the upcoming release. It'll have to wait for the one after that. The situation is that recent rack versions now require us to depend on both the rack and rackup gems. However, the rackup gem requires ruby 2.4 and we have to support Ruby 2.0 until June when CentOS 7 goes EOL. The last piece of the puzzle is that rubygems & bundler do not allow a gem to have conditional dependencies so we can't exclude rackup on earlier rubies. It's a really unfortunate situation. |
CentOS 7 is now EOL 💀 https://endoflife.date/centos |
6.0.23 is out with better rack3 support. Please try it out. |
Issue report
Are you sure this is a bug in Passenger?
Yes, i sure this from Passenger.
Please try with the newest version of Passenger to avoid issues that have already been fixed
My Gemfile has already pointing to the latest Passenger gem
Question 1: What is the problem?
I actually install this gem to my fresh Rails application, since i wanna change it's default development Web Server from Puma to Passenger.
rails s
,passenger start
, orrails c
command return this error:Question 2: Passenger version and integration mode:
Passenger Gem v6.0.18 Standalone
Question 3: OS or Linux distro, platform (including version):
WSL2 Linux (Ubuntu-22.04)
Question 4: Passenger installation method:
Question 5: Your app's programming language (including any version managers) and framework (including versions):
Question 6: Are you using a PaaS and/or containerization? If so which one?
No
Question 7: Anything else about your setup that we should know?
Nope.
The text was updated successfully, but these errors were encountered: