My current puma configuration... not working.

puma-as-service appears to start but does not

Trying to follow instructions at 
https://github.com/puma/puma/tree/master/tools/jungle/init.d#installation 
but it doesn't seem to be working. My sense is that public.production.config 
is correct since I can start puma with bundle exec puma ( illiustrated below ) 
but it own't start with /etc/init.d/puma... so I suspect /etc/puma.conf

jw@paisley:~$ sudo /etc/init.d/puma start
[sudo] password for jw:

 * => Running the jungle...               
 * --> Woke up puma /home/production/www.domain.com/current/public      
 * user production                                               
 * log to /home/production/www.domain.com/current/log/puma.log                                                            

Starting /usr/local/bin/run-puma...
Detaching to start /usr/local/bin/run-puma...done.

jw@paisley:~$ curl http://0.0.0.0:80
curl: (7) Failed connect to 0.0.0.0:80; Connection refused

jw@paisley:~$ curl http://0.0.0.0:9292
curl: (7) Failed connect to 0.0.0.0:9292; Connection refused

==========================================
HOWEVER, this works... as user production.  Note that I had to change from 80 to 9292 because production doesn't have sudo permission, which is needed for ports below... 1024?
==========================================

production@paisley:~/www.domain.com/current$ bundle exec puma --config config/puma.production.config
Puma starting in single mode...
* Version 2.3.2, codename: Delicious Thin Mints
* Min threads: 0, max threads: 16
* Environment: production
* Listening on tcp://v3.domain.com:9292
* Daemonizing...


production@paisley:~/www.domain.com/current$ curl -I http://v3.domain.com:9292
... success ... !

public,production.config

at /home/production/www.domain.com/current/puma.production.config

environment 'production'

daemonize true
pidfile '/home/production/www.domain.com/current/tmp/pids/puma.pid'
state_path '/home/production/www.domain.com/current/tmp/pids/puma.state'
stdout_redirect '/home/production/www.domain.com/current/log/puma.log', '/home/production/www.domain.com/current/log/puma.error.log'

bind 'tcp://v3.domain.com:80'

puma.conf

at /etc/puma.conf

/home/production/www.domain.com/current,production,/home/production/www.domain.com/current/config/puma.production.config,/home/production/www.domain.com/current/log/puma.log

puma.log

at /home/production/www.domain.com/current/log/puma.log


Puma starting in single mode...
* Version 2.3.2, codename: Delicious Thin Mints
* Min threads: 0, max threads: 16
* Environment: production