Ruby on rails 带Puma的本地主机通配符SSL_Ruby On Rails_Ssl_Puma

Ruby on rails 带Puma的本地主机通配符SSL

ruby-on-rails ssl

Ruby on rails 带Puma的本地主机通配符SSL,ruby-on-rails,ssl,puma,Ruby On Rails,Ssl,Puma,我有一个Rails 6.0应用程序和Puma 4.3。我需要使用自定义域设置通配符SSL证书。我已经查看了很多不同的资源，但我似乎无法让任何东西正常工作。我所看到的大多数东西都是针对非通配符设置的这是我的配置/puma.rb。我已经尝试了当前的配置以及被注释掉的东西 ## # Configure Puma server require 'fileutils' workers Integer(ENV.fetch('WEB_CONCURRENCY', 2)) threads_count = In

我有一个Rails 6.0应用程序和Puma 4.3。我需要使用自定义域设置通配符SSL证书。我已经查看了很多不同的资源，但我似乎无法让任何东西正常工作。我所看到的大多数东西都是针对非通配符设置的

这是我的

配置/puma.rb

。我已经尝试了当前的配置以及被注释掉的东西

##
# Configure Puma server

require 'fileutils'
workers Integer(ENV.fetch('WEB_CONCURRENCY', 2))
threads_count = Integer(ENV.fetch('MAX_THREADS', 5))
threads threads_count, threads_count

key  = %w[. config ssl myapp-local.com.key].join('/')
crt = %w[. config ssl myapp-local.com.crt].join('/')
ssl_bind '127.0.0.1', '9292', {
  key:         key,
  cert:        crt,
  verify_mode: :peer
}
# if ENV['ENVIRONMENT'] == 'development'
#   unless File.exist?(key)
#     def generate_root_cert(root_key)
#       root_ca = OpenSSL::X509::Certificate.new
#       root_ca.version = 2 # cf. RFC 5280 - to make it a "v3" certificate
#       root_ca.serial = 0x0
#       root_ca.subject = OpenSSL::X509::Name.parse "/C=BE/O=A1/OU=A/CN=*.myapp-local.com"
#       root_ca.issuer = root_ca.subject # root CA's are "self-signed"
#       root_ca.public_key = root_key.public_key
#       root_ca.not_before = Time.now
#       root_ca.not_after = root_ca.not_before + 2 * 365 * 24 * 60 * 60 # 2 years validity
#
#       root_ca.sign(root_key, OpenSSL::Digest::SHA256.new)
#       root_ca
#     end
#
#     root_key = OpenSSL::PKey::RSA.new(2048)
#     file = File.new(key, "wb")
#     file.write(root_key)
#     file.close
#
#     root_cert = generate_root_cert(root_key)
#
#     file = File.new(cert, "wb")
#     file.write(root_cert)
#     file.close
#   end
#
#   ssl_bind '127.0.0.1', '9292', {
#     key:         key,
#     cert:        cert,
#     verify_mode: :peer
#   }
#
#   puts "Using local SSL cert..."
# end

preload_app!

rackup      DefaultRackup
port        ENV.fetch('PORT', 3000)
environment ENV.fetch('RACK_ENV', 'development')

on_worker_boot do
    ##
    # Force Scout Agent launch. Required because of use of nginx in Procfile
    ScoutApm::Agent.instance.start_background_worker
end

on_worker_fork { FileUtils.touch('/tmp/app-initialized') }

我正在使用

工头。这是我的Procfile.dev
：
redis: (ps aux | grep 6379 | grep redis | awk '{ print $2 }' | xargs kill -s SIGINT) && redis-server --port 6379
resque: rake resque:workers QUEUE='*' COUNT='5'
scheduler: rake resque:scheduler
web: puma

然后在/etc/hosts
中，我有：
127.0.0.1   localhost
255.255.255.255 broadcasthost
::1             localhost
127.0.0.1 app.myapp-local.com

当我转到https://app.myapp-local.com:3000
我从Chrome收到一个错误(ERR\u SSL\u PROTOCOL\u ERROR)
错误
我还尝试手动生成证书，如下所示：
name=myapp-local.com
openssl req \
  -new \
  -newkey rsa:2048 \
  -sha256 \
  -days 3650 \
  -nodes \
  -x509 \
  -keyout $name.key \
  -out $name.crt \
  -config <(cat <<-EOF
  [req]
  distinguished_name = req_distinguished_name
  x509_extensions = v3_req
  prompt = no
  [req_distinguished_name]
  CN = $name
  [v3_req]
  keyUsage = keyEncipherment, dataEncipherment
  extendedKeyUsage = serverAuth
  subjectAltName = @alt_names
  [alt_names]
  DNS.1 = $name
  DNS.2 = *.$name
EOF
)

mv myapp-local.com.crt myapp-local.com.key config/ssl
sudo security add-trusted-cert -d -r trustRoot -k /Library/Keychains/System.keychain config/ssl/myapp-local.com.crt

if ENV['ENVIRONMENT'] == 'development'
  key  = %w[. config ssl myapp-local.com.key].join('/')
  crt  = %w[. config ssl myapp-local.com.pem].join('/')
  ca   = "/Users/Daniel Bonnell/Library/Application\ Support/Certificate\ Authority/myapp/myapp.certAuthorityConfig"

  ssl_bind '127.0.0.1', '3000', {
    key:         key,
    cert:        crt,
    ca:          ca,
    verify_mode: :peer
  }
end

现在，当我启动应用程序时，我在日志中看到：
17:12:45 web.1 | [68495] * Listening on ssl://127.0.0.1:3000?cert=./config/ssl/myapp-local.com.pem&key=./config/ssl/myapp-local.com.key&verify_mode=peer&no_tlsv1=false&no_tlsv1_1=false&ca=/Users/Daniel Bonnell/Library/Application Support/Certificate Authority/myapp/myapp.certAuthorityConfig
17:12:45 web.1 | [68495] * Listening on tcp://0.0.0.0:5300

如果我转到https://app.myapp-local.com:3000
我看到以下错误：
17:14:19 web.1 | 2020-03-28 17:14:19 -0500: SSL error, peer: 127.0.0.1, peer cert: /O=member: F4B00436-9C90-4941-B053-A83BCB633934 DD31B694-6F02-4C8D-98C2-640DABBEB3F8/CN=member: F4B00436-9C90-4941-B053-A83BCB633934 DD31B694-6F02-4C8D-98C2-640DABBEB3F8, #<Puma::MiniSSL::SSLError: OpenSSL certificate verification error: unable to get local issuer certificate - 20>

17:15:32 web.1 | 2020-03-28 17:15:32 -0500: HTTP parse error, malformed request (): #<Puma::HttpParserError: Invalid HTTP format, parsing fails.>

随后，我使用mkcert
生成了一个证书，然后在我的密钥链（MacOS）中设置了一个本地CA。
我成功地使设置正常工作。我认为有两个问题。首先，我将SSL绑定到端口3000，然后再向下，将Puma绑定到端口3000。我将port ENV.fetch（'port'，3000）
更改为port ENV.fetch（'port'，3001）
。第二，我指向了错误的CA。下面的设置现在似乎适合我。我可以在端口3000上访问我的应用程序，我不再看到那个讨厌的SSL错误。希望这对别人有帮助。我花了10个小时才弄明白。“当我转到时，我从Chrome收到一个ERR_SSL_PROTOCOL_ERROR错误。”-对我来说，您的配置在端口3000上执行纯HTTP，而在端口9292上执行SSL。这可以解释您看到的错误，即HTTPS访问不支持HTTPS的端口。我刚刚更新了我的问题。我尝试了一个本地CA的新配置。我想我越来越接近了，但现在我的证书似乎出现了某种问题？我已经检查过了，端口9292上没有任何运行。看起来只有3000和5300（不确定该端口来自何处）在使用中。