Lua-resty-auto-ssl: 替换 nginx.conf 的内容后 Nginx 无法启动

创建于 2019-02-02  ·  11评论  ·  资料来源: auto-ssl/lua-resty-auto-ssl

我尝试在全新安装的 Debian 9 上安装 lua-resty-auto-ssl

我做了以下

apt update
apt install nginx
apt install build-essential
apt install luarocks
luarocks install lua-resty-auto-ssl
mkdir /etc/resty-auto-ssl
chown www-data /etc/resty-auto-ssl

然后我用在自述https://github.com/GUI/lua-resty-auto-ssl 中发布的最小示例替换了 /etc/nginx/nginx.conf

但是把ngix.conf的内容换成minimal example后,nginx就不能启动了

我得到

root<strong i="13">@vultr</strong>:/etc/nginx# /etc/init.d/nginx start
[....] Starting nginx (via systemctl): nginx.serviceJob for nginx.service failed because the control process exited with error code.
See "systemctl status nginx.service" and "journalctl -xe" for details.
 failed!
root<strong i="14">@vultr</strong>:/etc
root<strong i="17">@vultr</strong>:/etc/nginx# systemctl status nginx.service
● nginx.service - A high performance web server and a reverse proxy server
   Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sat 2019-02-02 20:17:41 UTC; 50s ago
     Docs: man:nginx(8)
  Process: 6606 ExecStop=/sbin/start-stop-daemon --quiet --stop --retry QUIT/5 --pidfile /run/nginx.pid (code=exited, status=0/SUCCESS)
  Process: 483 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
  Process: 6923 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)
 Main PID: 496 (code=exited, status=0/SUCCESS)

Feb 02 20:17:41 vultr.guest systemd[1]: Starting A high performance web server and a reverse proxy server...
Feb 02 20:17:41 vultr.guest nginx[6923]: nginx: [emerg] unknown directive "lua_shared_dict" in /etc/nginx/nginx.conf:14
Feb 02 20:17:41 vultr.guest nginx[6923]: nginx: configuration file /etc/nginx/nginx.conf test failed
Feb 02 20:17:41 vultr.guest systemd[1]: nginx.service: Control process exited, code=exited status=1
Feb 02 20:17:41 vultr.guest systemd[1]: Failed to start A high performance web server and a reverse proxy server.
Feb 02 20:17:41 vultr.guest systemd[1]: nginx.service: Unit entered failed state.
Feb 02 20:17:41 vultr.guest systemd[1]: nginx.service: Failed with result 'exit-code'.

我的 nginx.conf 的内容

user www-data;
worker_processes auto;
pid /run/nginx.pid;
include /etc/nginx/modules-enabled/*.conf;

events {
  worker_connections 1024;
}

http {
  # The "auto_ssl" shared dict should be defined with enough storage space to
  # hold your certificate data. 1MB of storage holds certificates for
  # approximately 100 separate domains.
  lua_shared_dict auto_ssl 1m;
  # The "auto_ssl_settings" shared dict is used to temporarily store various settings
  # like the secret used by the hook server on port 8999. Do not change or
  # omit it.
  lua_shared_dict auto_ssl_settings 64k;

  # A DNS resolver must be defined for OCSP stapling to function.
  #
  # This example uses Google's DNS server. You may want to use your system's
  # default DNS servers, which can be found in /etc/resolv.conf. If your network
  # is not IPv6 compatible, you may wish to disable IPv6 results by using the
  # "ipv6=off" flag (like "resolver 8.8.8.8 ipv6=off").
  resolver 8.8.8.8;

  # Initial setup tasks.
  init_by_lua_block {
    auto_ssl = (require "resty.auto-ssl").new()

    -- Define a function to determine which SNI domains to automatically handle
    -- and register new certificates for. Defaults to not allowing any domains,
    -- so this must be configured.
    auto_ssl:set("allow_domain", function(domain)
      return true
    end)

    auto_ssl:init()
  }

  init_worker_by_lua_block {
    auto_ssl:init_worker()
  }

  # HTTPS server
  server {
    listen 443 ssl;

    # Dynamic handler for issuing or returning certs for SNI domains.
    ssl_certificate_by_lua_block {
      auto_ssl:ssl_certificate()
    }

    # You must still define a static ssl_certificate file for nginx to start.
    #
    # You may generate a self-signed fallback with:
    #
    # openssl req -new -newkey rsa:2048 -days 3650 -nodes -x509 \
    #   -subj '/CN=sni-support-required-for-valid-ssl' \
    #   -keyout /etc/ssl/resty-auto-ssl-fallback.key \
    #   -out /etc/ssl/resty-auto-ssl-fallback.crt
    ssl_certificate /etc/ssl/resty-auto-ssl-fallback.crt;
    ssl_certificate_key /etc/ssl/resty-auto-ssl-fallback.key;
  }

  # HTTP server
  server {
    listen 80;

    # Endpoint used for performing domain verification with Let's Encrypt.
    location /.well-known/acme-challenge/ {
      content_by_lua_block {
        auto_ssl:challenge_server()
      }
    }
  }

  # Internal server running on port 8999 for handling certificate tasks.
  server {
    listen 127.0.0.1:8999;

    # Increase the body buffer size, to ensure the internal POSTs can always
    # parse the full POST contents into memory.
    client_body_buffer_size 128k;
    client_max_body_size 128k;

    location / {
      content_by_lua_block {
        auto_ssl:hook_server()
      }
    }
  }
}

知道出了什么问题吗?

所有11条评论

看起来 nginx 没有正确加载 lua。
这是我的 dockerfile,基于 ubuntu 16:04。 也许它会帮助你:
https://pastebin.com/dnENPEaM
通过正确的设置,您的配置应该可以正常工作

看起来 nginx 没有正确加载 lua。
这是我的 dockerfile,基于 ubuntu 16:04。 也许它会帮助你:
https://pastebin.com/dnENPEaM
通过正确的设置,您的配置应该可以正常工作

谢谢,我将手动运行文件中的命令来安装它。 在其他一切之前使用 apt 安装 nginx 可以吗?

我开始关注你的文件,但不明白这些行是做什么的

ADD mime.types /etc/nginx/
ADD fastcgi_params /etc/nginx/

ADD ./start.sh /root/

到那时我做了所有其他的事情,没有错误

你可能更喜欢使用 openresty

不幸的是仍然没有成功。 我在全新安装的 Debian 9 上做了以下操作,这次我没有安装 Ngix,而是安装了 Openresty

apt update
apt upgrade
wget -qO - https://openresty.org/package/pubkey.gpg | apt-key add -
apt-get -y install software-properties-common
add-apt-repository -y "deb http://openresty.org/package/debian $(lsb_release -sc) openresty"
apt-get update
apt-get install openresty
apt install luarocks
apt install build-essential
luarocks install lua-resty-auto-ssl
mkdir /etc/resty-auto-ssl
chown www-data /etc/resty-auto-ssl

然后我更改了 /etc/openresty/nginx.conf 的内容

但我在尝试启动后得到以下信息

root<strong i="10">@vultr</strong>:/etc/openresty# /etc/init.d/openresty start
[....] Starting openresty (via systemctl): openresty.serviceJob for openresty.service failed because the control process exited with error code.
See "systemctl status openresty.service" and "journalctl -xe" for details.
 failed!

错误是

root<strong i="14">@vultr</strong>:~# systemctl status --no-pager --full openresty.service      
● openresty.service - full-fledged web platform
   Loaded: loaded (/lib/systemd/system/openresty.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2019-02-03 19:44:22 UTC; 16min ago
  Process: 18855 ExecStop=/sbin/start-stop-daemon --quiet --stop --retry QUIT/5 --pidfile /usr/local/openresty/nginx/logs/nginx.pid (code=exited, status=0/SUCCESS)
  Process: 18886 ExecStartPre=/usr/local/openresty/nginx/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)
 Main PID: 12782 (code=exited, status=0/SUCCESS)

Feb 03 19:44:22 vultr.guest systemd[1]: Starting full-fledged web platform...
Feb 03 19:44:22 vultr.guest nginx[18886]: nginx: [emerg] BIO_new_file("/etc/ssl/resty-auto-ssl-fallback.crt") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/ssl/resty-auto-ssl-fallback.crt','r') error:2006D080:BIO routines:BIO_new_file:no such file)
Feb 03 19:44:22 vultr.guest nginx[18886]: nginx: configuration file /usr/local/openresty/nginx/conf/nginx.conf test failed
Feb 03 19:44:22 vultr.guest systemd[1]: openresty.service: Control process exited, code=exited status=1
Feb 03 19:44:22 vultr.guest systemd[1]: Failed to start full-fledged web platform.
Feb 03 19:44:22 vultr.guest systemd[1]: openresty.service: Unit entered failed state.
Feb 03 19:44:22 vultr.guest systemd[1]: openresty.service: Failed with result 'exit-code'.

我从跑步开始

openssl req -new -newkey rsa:2048 -days 3650 -nodes -x509 -subj '/CN=sni-support-required-for-valid-ssl' \
> -keyout /etc/ssl/resty-auto-ssl-fallback.key -out /etc/ssl/resty-auto-ssl-fallback.crt

我现在面临的唯一问题是,如果我去https://mydomain.com ,证书是由“sni-support-required-for-valid-ssl”提供的,看起来它不会为我的域生成 letencrypt 证书。

这是一个权限问题。 如果我将 nginx 用户更改为 root 一切正常。 我会找到修复它的方法,然后我会写一个安装指南。

谢谢你的帮助。 我写了一个分步指南以供将来参考

在 Debian 上安装 lua resty auto ssl

我的 nginx.conf 的内容

`用户 www-data;
worker_processes 自动;
pid /run/nginx.pid;

如果要使用此配置,请远程转义字符

包括 /etc/nginx/modules-enabled/*.conf;

事件{
worker_connections 768;
}

http {

# 基本配置
发送文件;
tcp_nopush 开启;
tcp_nodelay 开启;
keepalive_timeout 65;
types_hash_max_size 2048;
包括 /etc/nginx/mime.types;
default_type 应用程序/八位字节流;

# ssl 配置
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_prefer_server_ciphers on;

# 日志配置
log_format 自定义 '$remote_addr - $remote_user [$time_local] '
'"$request" $status $body_bytes_sent '
'"$http_referer" "$http_user_agent" "$http_x_forwarded_for"';

access_log /var/log/nginx/access.log 自定义;
error_log /var/log/nginx/error.log;

# gzip
gzip 上;

#虚拟主机配置
包括/etc/nginx/conf.d/*.conf;

包括 /etc/nginx/sites-enabled/*;

lua_shared_dict prometheus_metrics 10M;
lua_package_path "/home/kunal/Documents/nginx-lua-prometheus/?.lua;;";
init_worker_by_lua_block {
prometheus = require("prometheus").init("prometheus_metrics")
metric_requests = prometheus:counter (
"nginx_http_requests_total", "HTTP 请求数", {"host", "status"})
metric_latency = prometheus:直方图
"nginx_http_request_duration_seconds", "HTTP 请求延迟", {"host"})
metric_connections = prometheus:gauge (
"nginx_http_connections", "HTTP 连接数", {"state"})
}
log_by_lua_block {
metric_ requests:inc (1, {ngx.var.server_name, ngx.var.status})
metric_latency :observe (tonumber(ngx.var.request_time), {ngx.var.server_name})
}
`

关于这里有什么问题的任何建议?

谢谢你的帮助。 我写了一个分步指南以供将来参考

在 Debian 上安装 lua resty auto ssl

@arya6000

我遇到了同样的问题,但是您发布的链接现在已损坏:(

估计你能帮我?

此页面是否有帮助?
0 / 5 - 0 等级

相关问题

discobean picture discobean  ·  8评论

stackrainbow picture stackrainbow  ·  20评论

sahildeliwala picture sahildeliwala  ·  16评论

kshnurov picture kshnurov  ·  3评论

jmvbxx picture jmvbxx  ·  6评论