Hello, I’m trying to set again ssl cert on debian 10 with nginx via certbot
after selecting the desired domain name and vhost I recieved such error message:
Failed authorization procedure. jouve-corp.fr (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://www.jouve-corp.fr [213.186.33.5]: “<html xml:lang=“fr-FR” lang=“fr-FR”>\n\n<title qtlid=“28806”>F\xe9licitations ! Votre domaine a bien \xe9t\xe9 cr\xe9\xe9 chez OVH !</”
IMPORTANT NOTES:
The following errors were reported by the server:
Domain: jouve-corp.fr
Type: unauthorized
Detail: Invalid response from http://www.jouve-corp.fr
[213.186.33.5]: “<html xml:lang=“fr-FR”
lang=“fr-FR”>\n\n<title qtlid=“28806”>Félicitations !
Votre domaine a bien été créé chez OVH !</”
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
Your account credentials have been saved in your Certbot
configuration directory at /etc/letsencrypt. You should make a
secure backup of this folder now. This configuration directory will
also contain certificates and private keys obtained by Certbot so
making regular backups of this folder is ideal.
My version of certbot : 0.31.0
How can i fix it ? How can i remove this redirect ?
The "fix" seems to be to exclude the challenge requests from "however" HTTP is normally handled by your server.
Redirections are typically in the vhost config files.
Do you have access to them?
Can you modify your vhost configs?
If so, just modify it to your desire or liking.
That depends on the web server software used.
Each software has a "usual" location for storing config files.
[but they also allow for custom included files, so your particular situation could be unique]
You might want to answer these questions to help us help you better/faster:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
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. crt.sh | 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:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
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):
I ran this command: certbot --nginx -d jouve-corp.fr
It produced this output: Failed authorization procedure. jouve-corp.fr (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://www.jouve-corp.fr [213.186.33.5]: “\n\nF\xe9licitations ! Votre domaine a bien \xe9t\xe9 cr\xe9\xe9 chez OVH !</”
My web server is (include version): Nginx 1.14.2
The operating system my web server runs on is (include version): Debian Buster (Debian 10)
My hosting provider, if applicable, is: My domain provider : OVH and i don’t have web hosting plan on my domain.
I can login to a root shell on my machine : yes
I’m using a control panel to manage my site : OVH cloud
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): certbot 0.31.0
In most cases, administrators will remove this file from sites-enabled/ and
leave it as reference inside of sites-available where it will continue to be
updated by the nginx packaging team.
This file will automatically load configuration files provided by other
applications, such as Drupal or Wordpress. These applications will be made
available underneath a path with that package name, such as /drupal8.
Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples.
Default server configuration
server {
listen 80 default_server;
listen [::]:80 default_server;
# SSL configuration
#
# listen 443 ssl default_server;
# listen [::]:443 ssl default_server;
#
# Note: You should disable gzip for SSL traffic.
# See: https://bugs.debian.org/773332
#
# Read up on ssl_ciphers to ensure a secure configuration.
# See: https://bugs.debian.org/765782
#
# Self signed certs generated by the ssl-cert package
# Don't use them in a production server!
#
# include snippets/snakeoil.conf;
root /var/www/html;
# Add index.php to the list if you are using PHP
index index.html index.htm index.nginx-debian.html;
server_name _;
location / {
# First attempt to serve request as file, then
# as directory, then fall back to displaying a 404.
try_files $uri $uri/ =404;
}
# pass PHP scripts to FastCGI server
#
#location ~ \.php$ {
# include snippets/fastcgi-php.conf;
#
# # With php-fpm (or other unix sockets):
# fastcgi_pass unix:/run/php/php7.3-fpm.sock;
# # With php-cgi (or other tcp sockets):
# fastcgi_pass 127.0.0.1:9000;
#}
# deny access to .htaccess files, if Apache's document root
# concurs with nginx's one
#
#location ~ /\.ht {
# deny all;
#}
Have you set up your DNS records @ OVH correctly to point to your server at Scaleway? Because on my system, your hostnames still resolve to 213.186.33.5 which is an OVH IP address.
That last part is confirmed by the way by just surfing to your site. I’m not very good at French, but the fact it says “OVH” in the line under the first “Félicitations” is a dead giveaway
I’m not familiair with OVH nor with Scaleway. You’ll need to know the IP address of the server where your site is actually hosted on Scaleway. Perhaps just running ifconfig will tell you. Then, if you have the IP address, you should go to the control panel of your DNS zone at OVH and change the IP addresses of the A records for www.jouve-corp.fr and jouve-corp.fr to that Scaleway IP address.
I just changed the IP addresses of the A records for www.jouve-corp.fr and jouve-corp.fr to this Scaleway IP address, I will try as soon as possible thanks !
