Please fill out the fields below so we can help you better.
My domain is:tab.heretical-web.xyz
I ran this command:letsencrypt --webroot certonly -w /var/www/letsencrypt/ -d tab.heretical-web.xyz
It produced this output:None, it just hung with no output
My operating system is (include version):Ubuntu 16.04
My web server is (include version):nginx 1.10.0
My hosting provider, if applicable, is:Linode
I can login to a root shell on my machine (yes or no, or I don’t know):
yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):no
If i run either:
$ sudo letsencrypt --agree-tos --email kiwiheretic@myself.com --staging --webroot certonly -w /var/www/letsencrypt/ -d tab.heretical-web.xyz
or the command shown in questions from a root prompt the session just hangs until ctrl-c is pressed.
from /var/log/letsencrypt/letsencrypt.log
2017-02-06 01:46:03,726:DEBUG:letsencrypt.cli:Root logging level set at 30
2017-02-06 01:46:03,728:INFO:letsencrypt.cli:Saving debug log to /var/log/letsencrypt/letsencrypt.log
2017-02-06 01:46:03,728:DEBUG:letsencrypt.cli:letsencrypt version: 0.4.1
2017-02-06 01:46:03,728:DEBUG:letsencrypt.cli:Arguments: ['--webroot', '-w', '/var/www/letsencrypt/', '-d', 'tab.heretical-web.xyz']
2017-02-06 01:46:03,729:DEBUG:letsencrypt.cli:Discovered plugins: PluginsRegistry(PluginEntryPoint#webroot,PluginEntryPoint#null,PluginEntryPoint#manual,PluginEntryPoint#standalone)
2017-02-06 01:46:03,734:DEBUG:letsencrypt.cli:Requested authenticator webroot and installer None
2017-02-06 01:46:03,735:DEBUG:letsencrypt.plugins.webroot:Creating root challenges validation dir at /var/www/letsencrypt/.well-known/acme-challenge
2017-02-06 01:46:03,735:DEBUG:letsencrypt.display.ops:Single candidate plugin: * webroot
Description: Webroot Authenticator
Interfaces: IAuthenticator, IPlugin
Entry point: webroot = letsencrypt.plugins.webroot:Authenticator
Initialized: <letsencrypt.plugins.webroot.Authenticator object at 0x7f99d5b7abd0>
Prep: True
2017-02-06 01:46:03,736:DEBUG:letsencrypt.cli:Selected authenticator <letsencrypt.plugins.webroot.Authenticator object at 0x7f99d5b7abd0> and installer None
My nginx configuration is:
# configuration of the server
server {
# the port your site will be served on
listen 80;
# the domain name it will serve for
server_name tab.heretical-web.xyz; # substitute your machine's IP address or FQDN
include acme_challenge.conf;
charset utf-8;
sendfile on;
# max upload size
client_max_body_size 75M; # adjust to taste
keepalive_timeout 0;
# Finally, send all non-media requests to the Django server.
location / {
proxy_pass http://localhost:8006;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $host;
}
}
The contents of acme_challenge.conf is:
#############################################################################
# Configuration file for Let's Encrypt ACME Challenge location
# This file is already included in listen_xxx.conf files.
# Do NOT include it separately!
#############################################################################
#
# This config enables to access /.well-known/acme-challenge/xxxxxxxxxxx
# on all our sites (HTTP), including all subdomains.
# This is required by ACME Challenge (webroot authentication).
# You can check that this location is working by placing ping.txt here:
# /var/www/letsencrypt/.well-known/acme-challenge/ping.txt
# And pointing your browser to:
# http://xxx.domain.tld/.well-known/acme-challenge/ping.txt
#
# Sources:
# https://community.letsencrypt.org/t/howto-easy-cert-generation-and-renewal-with-nginx/3491
#
#############################################################################
# Rule for legitimate ACME Challenge requests (like /.well-known/acme-challenge/xxxxxxxxx)
# We use ^~ here, so that we don't check other regexes (for speed-up). We actually MUST cancel
# other regex checks, because in our other config files have regex rule that denies access to files with dotted names.
location ^~ /.well-known/acme-challenge/ {
# Set correct content type. According to this:
# https://community.letsencrypt.org/t/using-the-webroot-domain-verification-method/1445/29
# Current specification requires "text/plain" or no content header at all.
# It seems that "text/plain" is a safe option.
default_type "text/plain";
# This directory must be the same as in /etc/letsencrypt/cli.ini
# as "webroot-path" parameter. Also don't forget to set "authenticator" parameter
# there to "webroot".
# Do NOT use alias, use root! Target directory is located here:
# /var/www/common/letsencrypt/.well-known/acme-challenge/
root /var/www/letsencrypt;
}
# Hide /acme-challenge subdirectory and return 404 on all requests.
# It is somewhat more secure than letting Nginx return 403.
# Ending slash is important!
location = /.well-known/acme-challenge/ {
return 404;
}
##################################################
Any ideas why this is hanging?
Thanks in advance.
