title: Docker Nginx complains: SSL: error:02001002
body: <p>I'm using the following <code>nginx.conf</code></p>
  
  <pre><code>worker_processes  1;
  
  
  events {
  worker_connections  1024;
  }
  
  http {
  include       mime.types;
  
  default_type  application/octet-stream;
  
  sendfile        on;
  
  keepalive_timeout  65;
  
  gzip on;
  gzip_disable "msie6";  
  gzip_vary on;
  gzip_proxied any;
  gzip_comp_level 6;
  gzip_buffers 16 8k;
  gzip_http_version 1.1;
  gzip_types text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript;
  
  server {
    listen         80;
    server_name    mydomain.org;
    return         301 https://$server_name$request_uri;
  }
  
  
  server {
  
    listen 443 ssl http2;
    ssl_certificate /etc/letsencrypt/live/mydomain.org/fullchain.pem; 
    ssl_certificate_key /etc/letsencrypt/live/mydomain.org/privkey.pem;
    ssl_session_timeout 1d;
    ssl_session_cache shared:SSL:50m;
    ssl_session_tickets off;
  
    ssl_protocols TLSv1.1 TLSv1.2;
    ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!3DES:!MD5:!PSK';
    ssl_prefer_server_ciphers on;
    ssl_dhparam /etc/nginx/certs/dhparam.pem; 
  
    add_header Strict-Transport-Security max-age=15768000;
  
    ssl_stapling on;
    ssl_stapling_verify on;
  
  
    ssl_trusted_certificate /etc/letsencrypt/live/mydomain.org/chain.pem; 
  
    resolver 8.8.8.8 8.8.4.4 valid=86400;
  
    root /var/www/html;
    index index.php;
    location / {
      try_files $uri $uri/ /index.php?$args;
    }
  
    rewrite /wp-admin$ $scheme://$host$uri/ permanent;
  
    location ~* ^.+\.(ogg|ogv|svg|svgz|eot|otf|woff|mp4|ttf|rss|atom|jpg|jpeg|gif|png|ico|zip|tgz|gz|rar|bz2|doc|xls|exe|ppt|tar|mid|midi|wav|bmp|rtf)$ {
      access_log off; log_not_found off; expires max;
    }
  
    location ~ [^/]\.php(/|$) {
      fastcgi_split_path_info ^(.+?\.php)(/.*)$;
      if (!-f $document_root$fastcgi_script_name) {
          return 404;
      }
        root           /var/www/html;
        fastcgi_pass   wp_db:9000;
        fastcgi_index  index.php;
        fastcgi_param SCRIPT_FILENAME /var/www/html$fastcgi_script_name;
        include        fastcgi_params;
    }    
  }
  }
  </code></pre>
  
  <p>But <code>nginx</code> container complains with:</p>
  
  <pre><code>nginx: [emerg] BIO_new_file("/etc/letsencrypt/live/mydomain.org/fullchain.pem") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/mydomain.org/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)
  </code></pre>
  
  <p>I have all the certificates on that path for let's encrypt. 
  I found this thread 
  <a href="https://serverfault.com/questions/537343/nginx-startup-fails-ssl-no-such-file-or-directory">https://serverfault.com/questions/537343/nginx-startup-fails-ssl-no-such-file-or-directory</a></p>
  
  <p>And did </p>
  
  <pre><code>chown -R root:root /etc/letsencrypt/live/mydomain.org/fullchain.pem
  chmod -R 600 /etc/letsencrypt/live/mydomain.org/fullchain.pem
  </code></pre>
  
  <p>Same error was thrown from <code>nginx</code> container. I've placed the certs on    <code>/docker-compose/etc/nginx/certs</code> giving the same permissions and changing links on <code>nging.conf</code> but nothing changed. </p>
  
  <p>What I'm missing?</p>