Letsencrypt error: "Timeout after connect"

[valian]

Letsencrypt error: "Timeout after connect"

[Valian]

So, I have two guesses:

1. You're missing

  include mime.types;
  default_type application/octet-stream;
  sendfile on;

in your http block. It looks like I've forgotten to add it to the README, but they are in https://github.com/Valian/docker-nginx-auto-ssl/blob/master/nginx.conf. I'll fix it soon.

2. server_name ~^(www\.)?influencers.cloud$; in your server for port 80 block is unneeded and blocks proper challenge file responses (but I'm not sure about this, as I've said it's just a guess).

---

In overall, I don't see the reason why you're overriding nginx.conf, since you just need some additional configuration for 443 server. My proposed solution, that should fix my both suggestions, is to just create a file influencers-cloud.conf and put it in /etc/nginx/conf.d/ using either volume or a custom Dockerfile.

server {
    listen 443 ssl;
    server_name influencers.cloud;
    include resty-server-https.conf;
    location / {
      proxy_read_timeout 120;
      proxy_set_header Host $http_host;
      proxy_set_header Authorization "";
      proxy_set_header User-Agent $http_user_agent;
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header X-Forwarded-Proto $scheme;
      proxy_set_header X-Real-IP $remote_addr;
      proxy_pass http://frontend:8000;
    }
    location /api/static {
      gzip on;
      alias /www/data/static/;
    }
    location /media {
      gzip on;
      alias /www/data/media/;
    }
  }

  server {
    listen 443 ssl;
    server_name www.influencers.cloud;
    include resty-server-https.conf;
    return 301 https://influencers.cloud$request_uri;
  }

Hope this will fix your problem @megapctr ;)

[ffigiel]

Hey, I appreciate the fast reply! I was overriding nginx.conf because I've had the same problem with conf.d first, so I opened the readme to look for hints and tried writing nginx.conf to see if it changes anything.

I switched back to conf.d and removed the server on port 80 you mentioned, and I received the certificate with no problem! Thanks a lot.