this happens almost immediately after a restart of the Puma service
the machine resources barely scratch 5%
puma is logging all requests as 127.0.0.1 instead of their IP Address I am using the X-Forwarded-For header in nginx, my nginx is custom compiled using chef omnibus if that makes a difference. Trying to debug so my request isn't 127.0.0.1, actual ip is (10.10.20.137). Any pointers?
ip is 216.x.x.x so it isn't even an internal address.
one thing unique to me is I am using chef omnibus so everything is compiled manually nginx, ruby, etc.
I took something from gitlab-ce to get to work locally https://gitlab.com/gitlab-org/gitlab-ce/blob/08264f4334ff48d1274f066cd5b03455bc4befdf/config/initializers/trusted_proxies.rb
I am just whitelisting ::1 and 127.0.0.1 nothing else
I think something in your middleware is doing the wrong thing. Take a look at this issue on puma/puma: https://github.com/puma/puma/pull/873#issuecomment-178099895
Try adding this to your Puma config:
set_remote_address header: "X-Forwarded-For”
trying the puma configuration change
still seeing 127.0.0.1
I didn’t have to do anything special for Puma to parse X-Forwarded-For from Varnish and HAproxy, so this is all a bit mysterious
i am wondering now if the rollbar gem could be causing this
But even that should only scrub the headers that get sent to Rollbar, and not actually remove them from the rack request.
My rails app is too slow
Using puma
@danilogarcia024 You’ll want to implement that in Rack, either nesting apps as middleware or using something like Rack::URLMap to build a routing tree. If that’s not an option you’ll likely end up needing to maintain multiple Puma processes with some kind of reverse proxy / request router in front of them
Hello. I have a Rails initializer that contains some code that I only want to run when we are running in server mode (not console or test). Than can be done if you boot with
rails server as Rails::Server is only defined when that command is run. However we use the puma binary in production, Rails::Server is not defined and Puma::Server is always defined. Is there a way I can detect that I am running inside a puma server?
In my current environment, puma becomes silent (returns no response) when I modify code while puma is up.
Of course, when I restart puma manually, it works correctly.
