Hi! I followed this guide how to generate certificate for my domain. [image] Update: Using Free Let’s Encrypt SSL/TLS Certificates with NGINX - NGINX Learn how to use the Let’s Encrypt client to generate RSA certificates and automatically configure NGINX to use the newly issued certific…

I don’t know. To the server via gunicorn? upstream mysite_server { server unix:/home/user/projects/mysite/gunicorn.sock fail_timeout=10s; } server { listen 8004; access_log /home/user/projects/logs/mysite_access.log; error_log /home/user/projects/logs/mysite_er…

That config seems to be only handling HTTP connections There should be a second for the HTTPS connections. Where do you handle the port forwarding? Check where does port 80 go to and where does port 443 go to.

Both 80 and 443 is redirected to 8004 on this server right now from my switch. Do I have to use two different ports for this because config can’t handle both in same listen? According to the guide I mention in the beginning. It only says the nginx config to look like this. server { listen 80 …

[image] sundrik: Do I have to use two different ports for this because config can’t handle both in same listen? Exactly! Each listener can only do one protocol HTTP or HTTPS - if you need both, then you need two listeners. 80 > X = (8004) 443 > Y = (????)

Then this should be your http section (change to listen 8004): [image] sundrik: According to the guide I mention in the beginning. It only says the nginx config to look like this. server { listen 8004 default_server; listen [::]:8004 default_server; root /var/www/html; server_n…

I see that this is added by Certbot in the Guide listen 443 ssl; # managed by Certbot # RSA certificate ssl_certificate /etc/letsencrypt/live/example.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/example.com/privkey.pem; # managed by Certbot inc…

If the cert files don’t yet exist, then the web server will fail to start. Order matters. Get port 80 to reach your web server. Get a cert. Add cert to whatever service/port you need (other than to same port 80 goes).

OK the way they show it here doesn’t seem (to me) to be best practice: [both listeners are in the same server block - without any real separation] server { listen 80 default_server; listen [::]:80 default_server; root /var/www/html; server_name example.com www.example.com; li…

That could have been clearer/cleaner/less problematic for any future changes as: server { listen 80 default_server; listen [::]:80 default_server; root /var/www/html; server_name example.com www.example.com; # Redirect non-https traffic to https if ($scheme != "https") { …

I guess that example is what it is because Certbot is making the changes. Therfore that is what the nginx conf will look like after the automatet changes are made. Anyway. I have a fully functional port 80 way into my server. I can reach it. But I get 404 error when trying to create the cert. Mayb…

Invalid response ".well-known"

Help

rg305 January 22, 2019, 10:13pm 25

Look for the line with “root” in your config that listens on port 8004
That is the path you need to use with --webroot

Topic		Replies	Views
Invalid response from .well-known/acme-challenge Help	7	2091	December 27, 2018
Invalid response from http://sitebuilt.net/.well-known/acme-challenge/ Help	19	975	November 11, 2022
Error creating Certs Help	25	2783	June 10, 2021
Well-known/acme-challenge/test gives 404 Help	11	1762	January 28, 2019
Cerbot The client lacks sufficient authorization :: Invalid response Help	15	13656	January 30, 2019

Invalid response ".well-known"

Related topics