After running the command: ./letsencrypt-auto certonly -a webroot --webroot-path=/usr/share/nginx/html -d codepajamas.com -d www.codepajamas.com I get the following errors reported. Note: I’m running all these commands from a sudo user. Domain: codepajamas.com Type: unauthorized Detail: Invalid r…

If you create the file /usr/share/nginx/html/.well-known/acme-challenge/test with contents “success” can you reach it externally OK using http://codepajamas.com/.well-known/acme-challenge/test ?

You mentioned that you’re using unicorn as a backend server. You should have a proxy_pass directive pointing to the unicorn port or socket somewhere in your server block, or otherwise nginx wouldn’t be sending traffic to unicorn. Are you sure this is the correct server block/config file?

http://codepajamas.com/.well-known/acme-challenge/test I get a standard 404 screen from Rails (which means my rails app is spun up by nginx and unicorn and there is no route for /.well-known/…) the test file does not appear. I set all permissions on /usr/share/nginx/html/.well-known to 755 also. T…

Good question I also have another Nginx config file at: /etc/nginx/nginx.conf user www-data; worker_processes 4; pid /run/nginx.pid; events { worker_connections 768; } http { sendfile on; tcp_nopush on; tcp_nodelay on; keepalive_timeout 65; types_hash_max_size 2048; include /etc/nginx/mi…

I found a few other files for nginx at /etc/default/nginx But I’m on a Digital Ocean server and following their explicit directions of where to update the Nginx file so hopefully it is the correct location. https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-u…

Those instructions are not specific to your hosting provider. These things work exactly the same on every VPS/dedicated server out there. More specifically, those instructions work on a standard nginx instance. In your case, however, you’re using nginx as a reverse proxy, forwarding all traffic to …

Thanks @pfg , [image] pfg: grep -r "proxy_pass" /etc/nginx returns search results: /etc/nginx/sites-available/default /etc/nginx/sites-available/rails I added the line as you suggested location ~ /\.well-known/acme-challenge { root /usr/share/nginx/html; } to both default and rails, The …

I definitely think /etc/nginx/sites-available/rails is the correct file after looking it over. upstream app_server { server unix:/var/run/unicorn.sock fail_timeout=0; } server { listen 80; root /home/rails/rails_project/public; server_name _; index index.htm index.html; …

One thing that this changed is that now the 404 page is the Nginx/Unbuntu 404 page and no longer the rails 404 page.

Hi I made progress I had to change one little thing about your code I instead had to remove the /acme-challenge and do just: location ~ /.well-known { allow all; root /usr/share/nginx/html; } After that I can see my test file and no longer get 404. Now I’m getting a new 500 error related…

404 on .well-known/acme-challenge/

Server

Topic		Replies	Views
404 error at well-known/acme-challenge/ Help	10	42055	November 14, 2017
404 on .well-known Help	6	1719	May 4, 2020
[Solved by itself] Well-known returns 404 for letsencrypt but it is OK for me Help	3	900	June 5, 2022
Failure Creating Certificate - acme-challenge - 404 error - nginx - AWS Help	7	4729	June 11, 2020
New certificate errors Django nginx gunicorn 404 Help	5	2405	April 10, 2018

404 on .well-known/acme-challenge/

Related topics