# No route found to match "/application/signin"

**URL:** <https://www.ruby-forum.com/t/no-route-found-to-match-application-signin/103222>\
**Category:** Rails\
**Created:** [May 3, 2007, 3:21am UTC](https://www.ruby-forum.com/t/no-route-found-to-match-application-signin/103222 "2007-05-03T03:21:42Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ryan\_Cush](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/d6d6ee/32.png) [@Ryan\_Cush](https://www.ruby-forum.com/u/Ryan_Cush)\
**Post date:** [May 3, 2007, 3:21am UTC](https://www.ruby-forum.com/t/no-route-found-to-match-application-signin/103222/1 "2007-05-03T03:21:42Z")

</div>

I’m posting this because I ran into a problem and had difficulty  
tracking down the answer. In fact, the answer was in another ruby-forum  
post, but the Search feature didn’t locate it via the keywords I was  
using. Hopefully my Subject line will help more people find this  
solution.

PROBLEM:  
I upgraded from Rails 1.1.6 to 1.2.3. When I did something that required  
me to sign in, I got:

ActionController::RoutingError (no route found to match  
“/application/signin” with {:method=\>:get}):

SOLUTION:  
Details posted here: [http://www.ruby-forum.com/topic/89699#173428](http://www.ruby-forum.com/topic/89699#173428)

In summary, it seems that the newer versions of Rails enforce that  
ApplicationController is not used to contain actions. It should just  
contain utility methods that you want your other controllers to inherit.  
Moving my “signin” method to another controller (and fixing all  
references to point to this new controller) fixed it.

- Ryan Cush  
[www.loanables.com](http://www.loanables.com)  
“Borrow it, don’t buy it!”