Can't use sockets with rails about puma

[sxua]

nginx/1.0.13

Oops, sorry, my bad. nginx logs shows me: *1 connect() to unix://tmp/puma.sock failed (13: Permission denied) while connecting to upstream

chmod a+rw /tmp/puma.sock does the trick

[thepixelmonk]

huh ok so I tried puma -b unix://tmp/sockets/puma.sock config.ru, but doesn't seem to be playing well with nginx, just gives me a bad gateway error. works fine if I don't use a socket and just use a custom port.

[thepixelmonk]

and my nginx setup works fine with unicorn's sockets.

[evanphx]

Was the first attempt calling puma via "rails server"? It looks like it got heavily confused because it's got a port number in there too.

I did just test it using nginx and it seems to work fine. What nginx configuration do you have it? Does the request show up in puma's log at all?

[sxua]

+1
also tried to pair it with nginx, but all I've got is "Bad Gateway"
this configuration works well with Unicorn, but not with Puma

nginx.conf:

upstream puma {
  server unix://tmp/puma.sock fail_timeout=0;
}

config/puma.rb:

bind "unix:///tmp/puma.sock"
pidfile "/tmp/puma.pid"

running as:

~$ puma -C ./config/puma.rb config.ru
Puma 1.0.0 starting...
* Min threads: 0, max threads: 16
* Listening on unix:///tmp/puma.sock
Use Ctrl-C to stop

[evanphx]

I'm still unable to reproduce this issue. What is in config.ru?

[sxua]

Just default Rails app

require ::File.expand_path('../config/environment',  __FILE__)
run TestApp::Application

[evanphx]

What version of nginx are you testing against? Does anything render?

[evanphx]

Oh interesting! So it was a permission problem. I'll investigate the proper way to set the perms of a unix socket.

[xpepermint]

Related to this #73