Specs: Rails 4.2.4, Ruby 2.1.9, running puma, EC2 instance in production mode
I have an SSL certificate that I want to install on my server but using techniques like this one yields no results
rails s puma -b 'ssl://0.0.0.0:9292?key=path_to_key.key&cert=path_to_cert.crt&verify_mode=none&ca=path_to_root_bundle.crt'
Instead of a functioning server I get
Puma starting in single mode... * Version 3.2.0 (ruby 2.1.9-p490), codename: Spring Is A Heliocentric Viewpoint * Min threads: 0, max threads: 16 * Environment: production * Listening on tcp://ssl://0.0.0.0:9292?key=~/evslideshow.key&cert=~/e3b162f57ea48f91.crt&verify_mode=peer&ca=~/gd_bundle-g2-g1.crt:80 * Exiting /home/ec2-user/.rvm/gems/ruby-2.1.9@slideshow/gems/puma-3.2.0/lib/puma/binder.rb:240:in `initialize': getaddrinfo: Name or service not known (SocketError)
Now my mind is playing with different options. I could continue using puma and somehow make it work. I could switch to a different server gem. Or I could use Amazon's certificate management system (though I'm guessing there are some costs involved with that).
Any help is greatly appreciated, I'm trying to save myself a long and wild goose chase.