# ActionDispatch::RemoteIp::IpSpoofAttackError exception

**URL:** <https://discuss.rubyonrails.org/t/actiondispatch-ipspoofattackerror-exception/70101>\
**Category:** rubyonrails-talk\
**Created:** [January 6, 2015, 12:44pm UTC](https://discuss.rubyonrails.org/t/actiondispatch-ipspoofattackerror-exception/70101 "2015-01-06T12:44:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jason\_FB](https://sea2.discourse-cdn.com/rubyonrails/user_avatar/discuss.rubyonrails.org/jason_fb/32/826_2.png) [@Jason\_FB](https://discuss.rubyonrails.org/u/Jason_FB)\
**Post date:** [January 6, 2015, 12:44pm UTC](https://discuss.rubyonrails.org/t/actiondispatch-ipspoofattackerror-exception/70101/1 "2015-01-06T12:44:06Z")

</div>

I am running Rails 3.2.21 on Heroku and yesterday I started seeing a low occurrence exceptions with this signature:

ActionDispatch::RemoteIp::IpSpoofAttackError: IP spoofing attack?!HTTP\_CLIENT\_IP="10.166.210.93"HTTP\_X\_FORWARDED\_FOR="10.166.210.93, 74.121.112.50"

here is the full stacktrace:

> <https://gist.github.com/jasonfb/652fff633de527fe08fb>

Heroku says this is a "false positive" and suggested I turn this off in m app config:

config.action\_dispatch.ip\_spoofing\_check = false

However, they are unable to explain why we've been running for 2 months on their platform until yesterday without this popping up, and yesterday was the first occurrence of it.

any ideas?

-Jason