For a client i installed a docker compose with nginx react node an certbot.
I manage to create a certificate and it expired few days ago and I can renew or create a new certificate.
Challenge reset by peer.
I also remove all https config and keep only http 80, and web site is working fine
But still can't create a certificate.
I have a similar project with same config on another server for another client and no issue.
I look on all config and the only issue that could be is a firewall issue but whitch one?
As i don't know how to keep challenge file (it's deleted after the test)
I add a file on acme-challenge directory and try to download it with curl.
nginx config for lets'encrypt:
location ^~ /.well-known/acme-challenge/ {
default_type "text/plain";
root /var/www/certbot;
}
My domain is: sam.sophia.inrae.fr
I ran this command: curl -O http://sam.sophia.inrae.fr/.well-known/acme-challenge/Test_File-1234
It produced this output:
In local server:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 15 100 15 0 0 1000 0 --:--:-- --:--:-- --:--:-- 1000
The ping display the public ip address, it's not running as localhost
In remote client:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (56) Recv failure: Connection reset by peer
My web server is (include version): nginx:alpine latest
The operating system my web server runs on is (include version): debian 5.10
My hosting provider, if applicable, is:
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):
The version of my client is (e.g. output of certbot --version
or certbot-auto --version
if you're using Certbot): certbot/certbot:latest