devise: InvalidAuthenticityToken
Environment
- Ruby [2.6.1]
- Rails [6.0.3.2]
- Devise [4.7.1]
Current behavior
ActionController::InvalidAuthenticityToken","exception_backtrace":["/home/ubuntu/.rvm/gems/ruby-2.6.1/gems/actionpack-6.0.3.2/lib/action_controller/metal/request_forgery_protection.rb:215:in `handle_unverified_request'","/home/ubuntu/.rvm/gems/ruby-2.6.1/gems/actionpack-6.0.3.2/lib/action_controller/metal/request_forgery_protection.rb:247:in `handle_unverified_request'","/home/ubuntu/.rvm/gems/ruby-2.6.1/gems/devise-4.7.1/lib/devise/controllers/helpers.rb:255:in `handle_unverified_request'","/home/ubuntu/.rvm/gems/ruby-2.6.1/gems/actionpack-6.0.3.2/lib/action_controller/metal/request_forgery_protection.rb:242:in
When trying to upgrade rails gem, it returns ActionController::InvalidAuthenticityToken It works fine with : rails (6.0.2.2)
Expected behavior
Devise and the latest version of rails should work fine.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 8
- Comments: 20 (1 by maintainers)
ERROR INVALID AUTHENTICITY TOKEN RAILS
Insert the Line bellow inside the file Application.rb: config.action_controller.allow_forgery_protection = false
Ran into a similar issue today after moving my project from my desktop to my laptop. Similar versions to what you’ve mentioned above. Except mine are:
Ruby [2.7.1] Rails [6.0.3.2] Devise [4.7.2]
I tried downgrading gems, reinstall ruby, hackish techniques I’m not proud of, anything I could think of…
Eventually ran into “ActionController::InvalidAuthenticityToken Error since re cloned git repo”
After running the following task, the problem was solved!
Didn’t even think of looking into the tmp/caching-dev.txt file.
Hopefully, that’ll help ya!
If you run into this while using Stimulus Reflex please bear in mind that if as instructed by Stimulus Reflex you set
config.cache_store = :redis_cache_store
and you set
config.session_store :cache_store
Redis server must be up otherwise you will get invalidAuthenticityToken error.
I’ve started having this issue after adding
config.session_store :cache_storeindevelopment.rb.Check if you have that, and try commenting it out. I’m not sure how the two are related.
Thanks all for digging into this one some more. Given most of us seem to agree this is not a Devise specific issue, I’m going ahead and closing it here.
If anyone is able to confirm it’s Devise related and can provide a reproduction script/test app, I’ll be happy to do some investigation.
Just in case this solved it for my app. Using latest versions of devise, active admin and rails: Gemfile
gem 'rack',"2.2.2"Terminal$ bundle updateThanks for the update. This is interesting as I’m seeing this in development mode locally, which isn’t running SSL. But I’m inclined to agree it’s a Rails or Rack issue rather than with Devise.
Are you using Rack 2.2.3 by any chance? I have seen a similar issue which can be addressed by downgrading to Rack 2.2.2. I’m not (yet) sure why exactly.