Veuillez remplir les champs ci-dessous pour que nous puissions vous aider. Remarque : vous devez fournir votre nom de domaine pour obtenir de l’aide. Les noms de domaine des certificats émis sont tous rendus publics dans les journaux de Transparence de Certificat (par exemple, https://crt.sh/?q=example.com). Par conséquent, le fait de ne pas indiquer votre nom de domaine ici n’aide pas à le garder secret, mais rend plus difficile pour nous le fait de vous aider.
Elle a produit cette sortie :
TLSv1.3 (IN), TLS alert, unrecognized name (624):
Info: OpenSSL/3.0.13: error:0A000458:SSL routines::tlsv1 unrecognized name
Mon serveur Web est (inclure la version) :
Haproxy version 2.8.30
Le système d’exploitation sur lequel mon serveur Web s’exécute est (version incluse) :
Linux Mint 22.3 - Cinnamon 64-bit (ubuntu 24.04.1)
Mon hébergeur, le cas échéant, est : At Home
Je peux me connecter à un shell root sur ma machine (oui ou non, ou je ne sais pas) : oui
J’utilise un panneau de configuration pour gérer mon site (non, ou fournit le nom et la version du panneau de configuration) : non
The error is because HAProxy is redirecting the HTTP request from Let's Encrypt to HTTPS. But, HAProxy cannot handle the HTTPS request (yet) and so the cert request fails.
frontend navidrome_https
bind *:443 ssl crt /etc/haproxy/certs/ strict-sni
http-request return status 200 content-type text/plain lf-string "%[path,field(-1,/)].${ACCOUNT_THUMBPRINT}\n" if { path_beg '/.well-known/acme-challenge/'
I have successfully restarted haproxy
Obviously, haproxy cannot manage HTTPS because there is no certificate yet
Remark:
The 1st time I restarted haproxy, I met an error talking about Low Balancer problem.
I fixed it by opening the port 80 on my router according to the Let'Encrypt recommendation.
I don't know exactly what all that means and what is the reason of the failure
If you have some idea, do not hesitate to answer this post
Regards
Yannick Savoye
I am progressing.
I thought about your remark about HTTP redirection in HAProxy.
I checked the Haproxy.cfg configuration file and I found a line that could cause this redirection. #Redirection HTTP → HTTPS
frontend navidrome_http
bind *:80
mode http redirect scheme https code 301 if !{ ssl_fc }
Well, HAProxy (or something else) returned an HTTP status 503 to Let's Encrypt. That's a Service Unavailable class error. You'd be better off asking about that on a HAProxy support or community forum.
That happens even for requests to the "home page" using HTTP.
curl -i savoye.duckdns.org
HTTP/1.0 503 Service Unavailable
cache-control: no-cache
content-type: text/html
<html><body><h1>503 Service Unavailable</h1>
No server is available to handle this request.
</body></html>
Thanx for your answer.
I have fixed the 503 error by asking HAProxy to send the request to my web server (Navidrome audio server).
It's better but I don't succeed to generate the certificate yet
When you use an HTTP Challenge (like you are) the Let's Encrypt servers send you an HTTP request to retrieve the challenge token. This is to prove you control that domain. The above is an unusual error but it happens when your server sends a very large message to the LE Server instead of the fairly small token value.
When I send a test HTTP challenge request your system redirects it to "/app/" and following that redirect I see a page about a Music Server.
Having HAProxy forward the request to your other server probably won't work unless you can configure it to response properly for "stateless" operation like you are telling acme.sh to use. And, we know you didn't do it right because of this error
I really think you are better off at a HAProxy forum. I am sure someone there can help you setup HAProxy properly to get a cert.
Trying to just add extra layers of things will only make your system more fragile even if you get it working somehow. You want a standard and reliable way to do these kinds of common tasks.