some routes stopped working after upgrade

Added by Boudewijn van Liempd about 10 years ago

I am running a freebsd box with redmine and after upgrading my webserver and redmine to the latest trunk I have some strange behavior with routes. For example when I go to the main page I get a 404 error but going to /projects works. I get the list of projects, I can access them even can go as far as editing an issue but submitting will result in a 404. Also clicking administration will result in a 404.

What I can't figure out is why some links work as they should and others don't.

I am running apache22, ruby18 and passenger 2.2.10 (all latest from ports) and have installed the following gems:

  • LOCAL GEMS ***

actionmailer (2.3.5)
actionpack (2.3.5)
activerecord (2.3.5)
activeresource (2.3.5)
activesupport (2.3.5)
fastthread (1.0.7)
fcgi (0.8.7)
hoe (2.4.0)
json_pure (1.1.9)
memcache-client (1.7.5)
mysql (2.7)
passenger (2.2.10)
rack (1.0.1)
rails (2.3.5)
rake (0.8.7, 0.8.4)
rspec (1.2.2)
rspec-rails (1.2.2)
rubyforge (2.0.3)
rubygems-update (1.3.5)
sources (0.0.2)
ZenTest (4.2.1)

the error message I get is:

Processing ApplicationController#index (for xxx.xxx.xxx.xxx at 2010-03-03 08:40:40) [GET]

ActionController::RoutingError (No route matches "/index.html" with {:method=>:get}):
passenger (2.2.10) lib/phusion_passenger/rack/request_handler.rb:92:in `process_request'
passenger (2.2.10) lib/phusion_passenger/abstract_request_handler.rb:207:in `main_loop'
passenger (2.2.10) lib/phusion_passenger/railz/application_spawner.rb:418:in `start_request_handler'
passenger (2.2.10) lib/phusion_passenger/railz/application_spawner.rb:358:in `handle_spawn_application'
passenger (2.2.10) lib/phusion_passenger/utils.rb:184:in `safe_fork'
passenger (2.2.10) lib/phusion_passenger/railz/application_spawner.rb:354:in `handle_spawn_application'
passenger (2.2.10) lib/phusion_passenger/abstract_server.rb:352:in `__send__'
passenger (2.2.10) lib/phusion_passenger/abstract_server.rb:352:in `main_loop'
passenger (2.2.10) lib/phusion_passenger/abstract_server.rb:196:in `start_synchronously'
passenger (2.2.10) lib/phusion_passenger/abstract_server.rb:163:in `start'
passenger (2.2.10) lib/phusion_passenger/railz/application_spawner.rb:213:in `start'
passenger (2.2.10) lib/phusion_passenger/spawn_manager.rb:262:in `spawn_rails_application'
passenger (2.2.10) lib/phusion_passenger/abstract_server_collection.rb:126:in `lookup_or_add'
passenger (2.2.10) lib/phusion_passenger/spawn_manager.rb:256:in `spawn_rails_application'
passenger (2.2.10) lib/phusion_passenger/abstract_server_collection.rb:80:in `synchronize'
passenger (2.2.10) lib/phusion_passenger/abstract_server_collection.rb:79:in `synchronize'
passenger (2.2.10) lib/phusion_passenger/spawn_manager.rb:255:in `spawn_rails_application'
passenger (2.2.10) lib/phusion_passenger/spawn_manager.rb:154:in `spawn_application'
passenger (2.2.10) lib/phusion_passenger/spawn_manager.rb:287:in `handle_spawn_application'
passenger (2.2.10) lib/phusion_passenger/abstract_server.rb:352:in `__send__'
passenger (2.2.10) lib/phusion_passenger/abstract_server.rb:352:in `main_loop'
passenger (2.2.10) lib/phusion_passenger/abstract_server.rb:196:in `start_synchronously'

Rendering /data/webroot/boudewijn.biz/redmine/public/404.html (404 Not Found)

any pointers as to where to look would be appreciated.

Replies (2)

RE: some routes stopped working after upgrade - Added by Boudewijn van Liempd about 10 years ago

Ok found out what was causing this. It had to do with the .htaccess file in the public directory conflicting with passenger. deleting it solved my problems.

RE: some routes stopped working after upgrade - Added by Mihai Cazac almost 7 years ago

Thank you, it helped! In my case .htaccess was there because prior I've tried (unsuccesfuly) to set up redmine with apache using mod_fastcgi and mod_fcgid. Passenger was my last chance...

(1-2/2)