Raspberry Pi (Debian Buster) + nginx

[produktive]

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: bbq.crabdance.com

I ran this command: sudo certbot --nginx

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator nginx, Installer nginx

Which names would you like to activate HTTPS for?

---

1: bbqpi.local
2: bbq.crabdance.com

---

Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter ‘c’ to cancel): 2
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for bbq.crabdance.com
Waiting for verification…
Cleaning up challenges
Deploying Certificate to VirtualHost /etc/nginx/sites-enabled/default

Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.

---

1: No redirect - Make no further changes to the webserver configuration.
2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for
new sites, or if you’re confident your site works on HTTPS. You can undo this
change by editing your web server’s configuration.

---

Select the appropriate number [1-2] then [enter] (press ‘c’ to cancel): 2
Redirecting all traffic on port 80 to ssl in /etc/nginx/sites-enabled/default

---

Congratulations! You have successfully enabled https://bbq.crabdance.com

You should test your configuration at:
https://www.ssllabs.com/ssltest/analyze.html?d=bbq.crabdance.com

---

IMPORTANT NOTES:

• Congratulations! Your certificate and chain have been saved at:
  /etc/letsencrypt/live/bbq.crabdance.com/fullchain.pem
  Your key file has been saved at:
  /etc/letsencrypt/live/bbq.crabdance.com/privkey.pem
  Your cert will expire on 2020-10-21. To obtain a new or tweaked
  version of this certificate in the future, simply run certbot again
  with the “certonly” option. To non-interactively renew all of
  your certificates, run “certbot renew”

• If you like Certbot, please consider supporting our work by:

  Donating to ISRG / Let’s Encrypt: https://letsencrypt.org/donate
  Donating to EFF: https://eff.org/donate-le

My web server is (include version): nginx 1.14.2

The operating system my web server runs on is (include version): Raspberry Pi OS (Debian Buster)

My hosting provider, if applicable, is: N/A

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): 0.31.0

I have opened port 443 on my router to forward to my Raspberry Pi. https site does not load. What is going wrong?

[Rip]

Hi @produktive

From my location your port 443 is filtered/blocked.
PORT STATE SERVICE
80/tcp open http
443/tcp filtered https
Suggest you recheck your firewall(s) and router. Possibly an upstram (ISP block)?

Rip

[produktive]

I have it opened on my router, as you can see here.

Their website does not have it listed as a blocked port: https://www.xfinity.com/support/articles/list-of-blocked-ports

I use a dynamic DNS service (afraid.org). I noticed in the nginx config it has an option about ipv6, is there some sort of Dynamic DNS entry modification I need to make to accommodate ipv6 somehow?

I thankfully found the error! In the port forwarding options, it asked for UDP or TCP or both. I had both selected. Changing it to TCP only made it work.

[Rip]

@produktive

anging it to TCP only made it work.

Glad you found a solution!

Rip