Could not apply cerbot on my Microsoft DNS

raymondhani · November 3, 2019, 10:52pm

My domain is: languaza.net

I ran this command: sudo certbot --nginx after using ./certbot-auto certonly --standalone

It produced this output: redirected on https://languaza.net but with This site can’t be reached

My web server is (include version): nginx

The operating system my web server runs on is (include version): ubuntu 18.4 on digital ocean

My hosting provider, is Digital Ocean but I bought my DNS from Microsoft

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

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):

rg305 · November 4, 2019, 12:02am

If this IP information is correct, there is no problem with DNS:
Name: languaza.net
Address: 178.128.172.184

You ran both certbot-auto and certbot ?
Please show the output of these commands:

certbot-auto --version
certbot --version
certbot-auto certificates
certbot certificates

raymondhani · November 4, 2019, 12:23am

yes the IP is correct
certbot --version 0.31.0

certbot certificates

Found the following certs:
Certificate Name: languaza.net
Domains: languaza.net
Expiry Date: 2020-02-01 21:00:06+00:00 (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/languaza.net/fullchain.pem
Private Key Path: /etc/letsencrypt/live/languaza.net/privkey.pem

I couldn't run certbot-auto...

rg305 · November 4, 2019, 12:32am

Ok so you have a good certbot and it has a valid cert.

rg305 · November 4, 2019, 12:35am

That is correct:
https://www.ssllabs.com/ssltest/analyze.html?d=languaza.net&hideResults=on

HTTP connects:

HTTP/1.1 200 OK
Server: nginx/1.14.0 (Ubuntu)
Date: Mon, 04 Nov 2019 00:33:33 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 35370
Connection: keep-alive
X-Powered-By: Express
Accept-Ranges: bytes
Cache-Control: public, max-age=0
Last-Modified: Sun, 03 Nov 2019 23:58:15 GMT
ETag: W/"8a2a-16e33b47862"

But HTTPS fails to connect:

curl -Iki https://languaza.net/
curl: (7) Failed to connect to languaza.net port 443: Connection timed out

If you can, please show output of
nginx -T

raymondhani · November 4, 2019, 2:09am

Please note that i reverted the nginx configuration using a command like nginx rollback or something like that to get the website back to life.

as well please notify me if there is something confidential that i need to hide from the following nginx info.

nginx -T output

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
# configuration file /etc/nginx/nginx.conf:
user www-data;
worker_processes auto;
pid /run/nginx.pid;
include /etc/nginx/modules-enabled/*.conf;

events {
        worker_connections 768;
        # multi_accept on;
}

  http {

    ##
    # Basic Settings
    ##

    sendfile on;
    tcp_nopush on;
    tcp_nodelay on;
    keepalive_timeout 65;
    types_hash_max_size 2048;
    # server_tokens off;

    # server_names_hash_bucket_size 64;
    # server_name_in_redirect off;

    include /etc/nginx/mime.types;
    default_type application/octet-stream;

    ##
    # SSL Settings
    ##

    ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # Dropping SSLv3, ref: POODLE
    ssl_prefer_server_ciphers on;

    ##
    # Logging Settings
    ##

    access_log /var/log/nginx/access.log;
    error_log /var/log/nginx/error.log;

    ##
    # Gzip Settings
    ##

    gzip on;

    # 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/javascript text/xml application/xml application/xml+rss text/javascript;

    ##
    # Virtual Host Configs
    ##

    include /etc/nginx/conf.d/*.conf;
    include /etc/nginx/sites-enabled/*;
    }


#mail {
#       # See sample authentication script at:
#       # http://wiki.nginx.org/ImapAuthenticateWithApachePhpScript
#
#       # auth_http localhost/auth.php;
#       # pop3_capabilities "TOP" "USER";
#       # imap_capabilities "IMAP4rev1" "UIDPLUS";
#
#       server {
#               listen     localhost:110;
#               protocol   pop3;
#               proxy      on;
#       }
#
#       server {
#               listen     localhost:143;
#               protocol   imap;
#               proxy      on;
#       }
#}

# configuration file /etc/nginx/modules-enabled/50-mod-http-geoip.conf:
load_module modules/ngx_http_geoip_module.so;

# configuration file /etc/nginx/modules-enabled/50-mod-http-image-filter.conf:
load_module modules/ngx_http_image_filter_module.so;

# configuration file /etc/nginx/modules-enabled/50-mod-http-xslt-filter.conf:
load_module modules/ngx_http_xslt_filter_module.so;

# configuration file /etc/nginx/modules-enabled/50-mod-mail.conf:
load_module modules/ngx_mail_module.so;

# configuration file /etc/nginx/modules-enabled/50-mod-stream.conf:
load_module modules/ngx_stream_module.so;

# configuration file /etc/nginx/mime.types:

types {
    text/html                             html htm shtml;
    text/css                              css;
    text/xml                              xml;
    image/gif                             gif;
    image/jpeg                            jpeg jpg;
    application/javascript                js;
    application/atom+xml                  atom;
    application/rss+xml                   rss;

    text/mathml                           mml;
    text/plain                            txt;
    text/vnd.sun.j2me.app-descriptor      jad;
    text/vnd.wap.wml                      wml;
    text/x-component                      htc;

    image/png                             png;
    image/tiff                            tif tiff;
    image/vnd.wap.wbmp                    wbmp;
    image/x-icon                          ico;
    image/x-jng                           jng;
    image/x-ms-bmp                        bmp;
    image/svg+xml                         svg svgz;
    image/webp                            webp;

    application/font-woff                 woff;
    application/java-archive              jar war ear;
    application/json                      json;
    application/mac-binhex40              hqx;
    application/msword                    doc;
    application/pdf                       pdf;
    application/postscript                ps eps ai;
    application/rtf                       rtf;
    application/vnd.apple.mpegurl         m3u8;
    application/vnd.ms-excel              xls;
    application/vnd.ms-fontobject         eot;
    application/vnd.ms-powerpoint         ppt;
    application/vnd.wap.wmlc              wmlc;
    application/vnd.google-earth.kml+xml  kml;
    application/vnd.google-earth.kmz      kmz;
    application/x-7z-compressed           7z;
    application/x-cocoa                   cco;
    application/x-java-archive-diff       jardiff;
    application/x-java-jnlp-file          jnlp;
    application/x-makeself                run;
    application/x-perl                    pl pm;
    application/x-pilot                   prc pdb;
    application/x-rar-compressed          rar;
    application/x-redhat-package-manager  rpm;
    application/x-sea                     sea;
    application/x-shockwave-flash         swf;
    application/x-stuffit                 sit;
    application/x-tcl                     tcl tk;
    application/x-x509-ca-cert            der pem crt;
    application/x-xpinstall               xpi;
    application/xhtml+xml                 xhtml;
    application/xspf+xml                  xspf;
    application/zip                       zip;

    application/octet-stream              bin exe dll;
    application/octet-stream              deb;
    application/octet-stream              dmg;
    application/octet-stream              iso img;
    application/octet-stream              msi msp msm;

    application/vnd.openxmlformats-officedocument.wordprocessingml.document    docx;
    application/vnd.openxmlformats-officedocument.spreadsheetml.sheet          xlsx;
    application/vnd.openxmlformats-officedocument.presentationml.presentation  pptx;

    audio/midi                            mid midi kar;
    audio/mpeg                            mp3;
    audio/ogg                             ogg;
    audio/x-m4a                           m4a;
    audio/x-realaudio                     ra;

    video/3gpp                            3gpp 3gp;
    video/mp2t                            ts;
    video/mp4                             mp4;
    video/mpeg                            mpeg mpg;
    video/quicktime                       mov;
    video/webm                            webm;
    video/x-flv                           flv;
    video/x-m4v                           m4v;
    video/x-mng                           mng;
    video/x-ms-asf                        asx asf;
    video/x-ms-wmv                        wmv;
    video/x-msvideo                       avi;
}

# configuration file /etc/nginx/sites-enabled/default:
##
# You should look at the following URL's in order to grasp a solid understanding
# of Nginx configuration files in order to fully unleash the power of Nginx.
# https://www.nginx.com/resources/wiki/start/
# https://www.nginx.com/resources/wiki/start/topics/tutorials/config_pitfalls/
# https://wiki.debian.org/Nginx/DirectoryStructure
#
# In most cases, administrators will remove this file from sites-enabled/ and
# leave it as reference inside of sites-available where it will continue to be
# updated by the nginx packaging team.
#
# This file will automatically load configuration files provided by other
# applications, such as Drupal or Wordpress. These applications will be made
# available underneath a path with that package name, such as /drupal8.
#
# Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
##

# Default server configuration
#
server {
        listen 80 default_server;
        listen [::]:80 default_server;

        # SSL configuration
        #
        # listen 443 ssl default_server;
        # listen [::]:443 ssl default_server;
        #
        # Note: You should disable gzip for SSL traffic.
        # See: https://bugs.debian.org/773332
        #
        # Read up on ssl_ciphers to ensure a secure configuration.
        # See: https://bugs.debian.org/765782
        #
        # Self signed certs generated by the ssl-cert package
        # Don't use them in a production server!
        #
        # include snippets/snakeoil.conf;

        root /var/www/html;

        # Add index.php to the list if you are using PHP
        index index.html index.htm index.nginx-debian.html app.js;

        server_name languaza.net;

        location / {
                # First attempt to serve request as file, then
                # as directory, then fall back to displaying a 404.
                proxy_pass http://localhost:3000;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
        }

        # pass PHP scripts to FastCGI server
        #
        #location ~ \.php$ {
        #       include snippets/fastcgi-php.conf;
        #
        #       # With php-fpm (or other unix sockets):
        #       fastcgi_pass unix:/var/run/php/php7.0-fpm.sock;
        #       # With php-cgi (or other tcp sockets):
        #       fastcgi_pass 127.0.0.1:9000;
        #}

        # deny access to .htaccess files, if Apache's document root
        # concurs with nginx's one
        #
        #location ~ /\.ht {
        #       deny all;
        #}

    listen [::]:443 ssl ipv6only=on; # managed by Certbot
    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/languaza.net/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/languaza.net/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}


# Virtual Host configuration for example.com
#
# You can move that to a different file under sites-available/ and symlink that
# to sites-enabled/ to enable it.
#
#server {
#       listen 80;
#       listen [::]:80;
#
#       server_name example.com;
#
#       root /var/www/example.com;
#       index index.html;
#
#       location / {
#               try_files $uri $uri/ =404;
#       }
#}

# configuration file /etc/letsencrypt/options-ssl-nginx.conf:
# This file contains important security parameters. If you modify this file
# manually, Certbot will be unable to automatically provide future security
# updates. Instead, Certbot will print and log an error message with a path to
# the up-to-date file that you will need to refer to when manually updating
# this file.

ssl_session_cache shared:le_nginx_SSL:1m;
ssl_session_timeout 1440m;

ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_prefer_server_ciphers on;

ssl_ciphers "ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:ECDHE-ECDSA-DES-CBC3-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:!DSS";

rg305 · November 4, 2019, 2:26am

I can’t find anything wrong with your nginx config.
But HTTPS continues to be blocked.
Are you using a firewall?
If so, ensure port 443 is allowed in.
If not, or yes but allowed, does your ISP block port 443?

raymondhani · November 4, 2019, 2:33am

it seems that was the problem the https://languaza.net works now and secured thanks a lot … now how do i make the http redirects on the https ? i mean just by writing languaza.net it redirects on the https://??

as well does the https affects the website loading speed ?

rg305 · November 4, 2019, 2:46am

HTTPS does require encryption so it should be slightly slower.

For HTTP to HTTPS redirections:
The simplest way is to separate the http section from the https section.
Right now both are in the same file and in the same server block:
/etc/nginx/sites-enabled/default
Once separated, add to the http section:

return 301 https://$host$request_uri;

Otherwise, you have to check for connection protocol and when http then redirect:

if ($scheme != "https") {
    return 301 https://$host$request_uri;
}#if

raymondhani · November 4, 2019, 2:49am

actually the cerbot asked me to do it for me in the first place… and did it in fact but i reverted it.

is there any command that would do it for me ?

rg305 · November 4, 2019, 2:51am

I'm not sure certbot is "smart enough" to properly code it in a single block.
[that may be why your site failed before]

Ideally http and https should be separated.
Do that first and then ask certbot to redirect for you.

rg305 · November 4, 2019, 2:55am

Here is copy of what a working file can look like (less all the noise):

server { #HTTP
        listen 80 default_server;
        listen [::]:80 default_server;
        root /var/www/html;
        index index.html index.htm index.nginx-debian.html app.js;
        server_name languaza.net;
        location / {
             return 301 https://$host$request_uri; #redirect all to HTTPS
        }#location
}#server

server { #HTTPS
    listen 443 ssl; # managed by Certbot
    listen [::]:443 ssl ipv6only=on; # managed by Certbot
        root /var/www/html;
        # Add index.php to the list if you are using PHP
        index index.html index.htm index.nginx-debian.html app.js;
        server_name languaza.net;
        location / {
                # First attempt to serve request as file, then
                # as directory, then fall back to displaying a 404.
                proxy_pass http://localhost:3000;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
        }#location
    ssl_certificate /etc/letsencrypt/live/languaza.net/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/languaza.net/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}#server

But you still have the problem where port 443 is NOT accessible from the Internet.
So you will redirect all the port 80 connections to 443 and they won’t be able to connect

raymondhani · November 4, 2019, 3:01am

thanks for your efforts in helping me … so as i see in my file that i have 2 sections for server {} … do i just copy and paste replacing my file ??

how so ? i just tried and the https is working as well this is my ufw status in the server

        443 (v6)                   ALLOW       Anywhere (v6)

raymondhani · November 4, 2019, 3:07am

and btw how do i make it auto renewal ?

rg305 · November 4, 2019, 3:16am

yes.

Cerbot should have setup a cron job or systemd timer

Success!

curl -Iki https://languaza.net/
HTTP/1.1 200 OK
Server: nginx/1.14.0 (Ubuntu)
Date: Mon, 04 Nov 2019 03:16:35 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 35386
Connection: keep-alive
X-Powered-By: Express
Accept-Ranges: bytes
Cache-Control: public, max-age=0
Last-Modified: Mon, 04 Nov 2019 02:35:28 GMT
ETag: W/"8a3a-16e34446872"

But I still don't see the HTTP to HTTPS redirection.

raymondhani · November 6, 2019, 2:52pm

yes I had to sleep this day and been busy a bit this week , however I am afraid to change values in the nginx config file … is there a way to roll back changes in case something wrong happened ?

but for now both http and https works right ?

rg305 · November 6, 2019, 3:30pm

Yes.

Yes.
The simplest is to copy any file to a safe location before making any changes to it.
And copy back the original if changes need to be fully reverted.

rg305 · November 6, 2019, 3:36pm

Post #12 has a good copy of the HTTP and HTTPS in two separate blocks and redirecting HTTP to HTTPS.

system · December 6, 2019, 3:43pm

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.