Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8831641
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 14, 20262026-06-14T08:21:23+00:00 2026-06-14T08:21:23+00:00

I am using devise for authentication and for now, I can sign-up a user

  • 0

I am using devise for authentication and for now, I can sign-up a user who is automatically logged in.

However, devise does not recognise the path localhost:3000/users/sign_out

It gives an error

No route matches [GET] "/users/sign_out"

In my routes, I have the devise_for :users statement as I generated devise for Users.

I have devise set up well in my users model too, user.rb as follows

class User < ActiveRecord::Base
devise :database_authenticatable, :registerable,
     :recoverable, :rememberable, :trackable, :validatable
attr_accessible :email, :password, :password_confirmation, :remember_me
end

My rake routes show the following

destroy_user_session DELETE /users/sign_out(.:format)      devise/sessions#destroy

Anyone know why my URL path is not being recognised

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-14T08:21:25+00:00Added an answer on June 14, 2026 at 8:21 am

    It is because the route expects a DELETE HTTP action not a GET action.

    destroy_user_session DELETE /users/sign_out(.:format) devise/sessions#destroy

    By Entering a URL in the browser you are sending a GET action to that URL.

    In order to make devise accept GET action for the sign_out route change in devise.rb:

    config.sign_out_via = :delete
    
    to 
    
    config.sign_out_via = :get
    

    An alternative is to add a :method => :delete to the link in the view, this way a DELETE action will be sent to your server as Devise expects.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

So I am using Devise for user authentication in my rails app. I have
I am using devise for authentication and i want only user named admin having
I am using Devise gem for web authentication in my Application. Now i am
I am using devise for my application authentication. I am having a User model
I'm using Devise for user authentication and basic authentication. Let's say I have defined
I'm using Devise and CanCan to setup authentication and authorization in my app. Now
I am using devise as my authentication solution and now i am thinking about
I have a Rails 3 application using Devise for authentication. Now I need to
I have been using devise for authentication and cancan for authorization in my application.
I am using Devise to manage authentication in a Rails 3.1 application. It works

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.