# The server could not connect to the client to verify the domain in **URL:** \ **Category:** Help\ **Created:** [January 29, 2018, 9:30am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain-in/51640 "2018-01-29T09:30:21Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![butrm2j](https://avatars.discourse-cdn.com/v4/letter/b/0ea827/32.png) [@butrm2j](https://community.letsencrypt.org/u/butrm2j)\ **Post date:** [January 29, 2018, 9:30am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain-in/51640/1 "2018-01-29T09:30:21Z")
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. [https://crt.sh/?q=example.com](https://crt.sh/?q=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: [www.compliancecorporate.es](http://www.compliancecorporate.es) I ran this command: ./certbot-auto renew It produced this output: Attempting to renew cert ([compliancecorporate.es](http://compliancecorporate.es)) from /etc/letsencrypt/renewal/compliancecorporate.es.conf produced an unexpected error: Failed authorization procedure. [compliancecorporate.es](http://compliancecorporate.es) (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching [https://www.compliancecorporate.es.well-known/acme-challenge/Y0dGLCALd3kLAX7AD3NMdUuqTcsonPFsk0Ndix5qlPI:](https://www.compliancecorporate.es.well-known/acme-challenge/Y0dGLCALd3kLAX7AD3NMdUuqTcsonPFsk0Ndix5qlPI:) Error getting validation data, [www.compliancecorporate.es](http://www.compliancecorporate.es) (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching [https://www.compliancecorporate.es.well-known/acme-challenge/IZpRLRdrlvKzjQ4YSumpImfEUgRTkET72Qp0lvQUx7Y:](https://www.compliancecorporate.es.well-known/acme-challenge/IZpRLRdrlvKzjQ4YSumpImfEUgRTkET72Qp0lvQUx7Y:) Error getting validation data. Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/compliancecorporate.es/fullchain.pem (failure) * * * ## All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/compliancecorporate.es/fullchain.pem (failure) 1 renew failure(s), 0 parse failure(s) IMPORTANT NOTES: - The following errors were reported by the server: The operating system my web server runs on is (include version): CENTOS7 I can login to a root shell on my machine (yes or no, or I don’t know):yes It seems the problem is that is tryinto access [https://www.compliancecorporate.es.well-known/](https://www.compliancecorporate.es.well-known/)… instead of [https://www.compliancecorporate.es/.well-known/](https://www.compliancecorporate.es/.well-known/) Could you help me? ---
**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\ **Post date:** [January 29, 2018, 9:38am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain-in/51640/2 "2018-01-29T09:38:59Z")
You have a bad redirect on your site. > $ curl -X GET -I compliancecorporate.es/.well-known/acme-challenge/ > HTTP/1.1 301 Moved Permanently > Date: Mon, 29 Jan 2018 09:37:45 GMT > Server: Apache > X-Frame-Options: SAMEORIGIN > Location: [https://www](https://www). **compliancecorporate.es.well-known** /acme-challenge/ > Content-Length: 269 > Content-Type: text/html; charset=iso-8859-1 Note the absence of a trailing slash after `.es`. ---
**Author:** ![butrm2j](https://avatars.discourse-cdn.com/v4/letter/b/0ea827/32.png) [@butrm2j](https://community.letsencrypt.org/u/butrm2j)\ **Post date:** [January 29, 2018, 9:52am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain-in/51640/3 "2018-01-29T09:52:42Z")
Where can I find the configuration file to change it? Thanks in advance! ---
**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\ **Post date:** [January 29, 2018, 9:53am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain-in/51640/4 "2018-01-29T09:53:57Z")
What’s your hosting environment? Linux and Apache? Bitnami? cPanel? etc … What does this say? ```auto apachectl -S ``` ---
**Author:** ![butrm2j](https://avatars.discourse-cdn.com/v4/letter/b/0ea827/32.png) [@butrm2j](https://community.letsencrypt.org/u/butrm2j)\ **Post date:** [January 29, 2018, 9:55am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain-in/51640/5 "2018-01-29T09:55:26Z")
CENTOS 7 and Apache with Bitnami 1and1. Access to console. [root@localhost letsencrypt]# apachectl -S VirtualHost configuration: \*:80 [compliancecorporate.es](http://compliancecorporate.es) (/opt/bitnami/apache2/conf/bitnami/bitnami.conf:8) \*:443 [compliancecorporate.es](http://compliancecorporate.es) (/opt/bitnami/apache2/conf/bitnami/bitnami.conf:46) ServerRoot: "/opt/bitnami/apache2" Main DocumentRoot: “/opt/bitnami/apps/owncloud/htdocs" Main ErrorLog: “/opt/bitnami/apache2/logs/error\_log" Mutex ssl-stapling-refresh: using\_defaults Mutex rewrite-map: using\_defaults Mutex ssl-stapling: using\_defaults Mutex proxy: using\_defaults Mutex ssl-cache: using\_defaults Mutex default: dir=”/opt/bitnami/apache2/logs/” mechanism=default Mutex proxy-balancer-shm: using\_defaults PidFile: "/opt/bitnami/apache2/logs/httpd.pid" Define: DUMP\_VHOSTS Define: DUMP\_RUN\_CFG Define: USE\_PHP\_FPM User: name=“daemon” id=2 Group: name=“daemon” id=2 [root@localhost letsencrypt]# ---
**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\ **Post date:** [January 29, 2018, 9:58am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain-in/51640/6 "2018-01-29T09:58:03Z")
Can you show me `/opt/bitnami/apache2/conf/bitnami/bitnami.conf` ? I think there is going to be a `Redirect` line in there that needs to have a trailing slash `/` added to the end … ---
**Author:** ![butrm2j](https://avatars.discourse-cdn.com/v4/letter/b/0ea827/32.png) [@butrm2j](https://community.letsencrypt.org/u/butrm2j)\ **Post date:** [January 29, 2018, 10:03am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain-in/51640/7 "2018-01-29T10:03:19Z")
Thank you very much!! ---
**Author:** ![butrm2j](https://avatars.discourse-cdn.com/v4/letter/b/0ea827/32.png) [@butrm2j](https://community.letsencrypt.org/u/butrm2j)\ **Post date:** [January 29, 2018, 10:44am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain-in/51640/8 "2018-01-29T10:44:20Z")
Sorry, now I cannot see the certification date updated but the renewal process have finished correctly… ---
**Author:** ![butrm2j](https://avatars.discourse-cdn.com/v4/letter/b/0ea827/32.png) [@butrm2j](https://community.letsencrypt.org/u/butrm2j)\ **Post date:** [January 29, 2018, 11:14am UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain-in/51640/9 "2018-01-29T11:14:17Z")
Sorry, I have updated the certification but when I access through internet it shows me the old expiration date. I have tried to stop all the services through: ./ctlscript.sh restart but it continues to show me the old expiration date. Thanks in advance! Máximo Tamayo Ruiz www. i n f o r m a c o n s u l t i n g. com c/ Heros, 28. Entr dcha. 48009 BILBAO c/ V i l l a n u e v a, 29. 28001 MADRID Telf 94 424 40 14 Fax 94 424 04 33 ­­­ Advertencia legal Este mensaje y cualquier mensaje adjunto al mismo, va dirigido de manera exclusiva a su destinatario y puede contener información CONFIDENCIAL y sujeta al secreto profesional, cuya divulgación no está permitida por la ley. En caso de haber recibido este mensaje por error, le rogamos que, de forma inmediata, nos lo comunique y proceda a su eliminación, así como a la de cualquier documento adjunto al mismo. Le comunicamos que la distribución, copia o utilización de este mensaje, o de cualquier documento adjunto al mismo, cualquiera que fuera su finalidad, están prohibidas por la ley. Legal warning This message, and any document enclosed, are intended exclusively for its addressee and may contain CONFIDENTIAL information protected by a professional privilege, whose disclosure is prohibited by law. If this message has been received in error, we request you to notify us immediately via e-mail and delete it, as well as any attached document. If you are not the intended recipient you are hereby notified that any read, dissemination, copy or disolosure of this message, independently of its purpose, is strictly prohibited by law. ![](https://global.discourse-cdn.com/letsencrypt/original/3X/9/1/9111374f06d39e2a2185c742d46b781df7018017.jpg) ---
**Author:** ![butrm2j](https://avatars.discourse-cdn.com/v4/letter/b/0ea827/32.png) [@butrm2j](https://community.letsencrypt.org/u/butrm2j)\ **Post date:** [January 29, 2018, 2:45pm UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain-in/51640/10 "2018-01-29T14:45:20Z")
If you access through the web browser it shows as expiration date 15/02/2018 but with ./certbot/certbot-auto certificates [root@localhost letsencrypt]# ./certbot-auto certificates Saving debug log to /var/log/letsencrypt/letsencrypt.log * * * ## Found the following certs: Certificate Name: [compliancecorporate.es](http://compliancecorporate.es) Domains: [www.compliancecorporate.es](http://www.compliancecorporate.es) [compliancecorporate.es](http://compliancecorporate.es) Expiry Date: 2018-04-29 13:39:25+00:00 (VALID: 89 days) Certificate Path: /etc/letsencrypt/live/compliancecorporate.es/fullchain.pem Private Key Path: /etc/letsencrypt/live/compliancecorporate.es/privkey.pem ---
**Author:** ![sahsanu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sahsanu/32/89984_2.png) [@sahsanu](https://community.letsencrypt.org/u/sahsanu)\ **Post date:** [January 29, 2018, 3:08pm UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain-in/51640/11 "2018-01-29T15:08:45Z")
Hi @butrm2j, You should double check where are the `SSLCertificateFile` and `SSLCertificateKeyFile` directives pointing out in your Bitnami conf. Seems they are not using the right path to your renewed cert… or maybe you need to copy your new cert and key to some other place where Bitnami is reading them… Cheers, sahsanu ---
**Author:** ![butrm2j](https://avatars.discourse-cdn.com/v4/letter/b/0ea827/32.png) [@butrm2j](https://community.letsencrypt.org/u/butrm2j)\ **Post date:** [January 29, 2018, 4:04pm UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain-in/51640/12 "2018-01-29T16:04:57Z")
I copy what I have in the bitnami.conf: Redirect permanent /secure [https://www.compliancecorporate.es](https://www.compliancecorporate.es) ServerName [compliancecorporate.es](http://compliancecorporate.es) ServerAlias [compliancecorporate.es](http://compliancecorporate.es) [www.compliancecorporate.es](http://www.compliancecorporate.es) DocumentRoot "/opt/bitnami/apache2/htdocs" SSLEngine on SSLCertificateFile "/opt/bitnami/apache2/conf/server.crt" SSLCertificateKeyFile "/opt/bitnami/apache2/conf/server.key" SSLCACertificateFile “/opt/bitnami/apache2/conf/server-ca.crt” \ ---
**Author:** ![jared.m](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jared.m/32/17871_2.png) [@jared.m](https://community.letsencrypt.org/u/jared.m)\ **Post date:** [January 29, 2018, 4:24pm UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain-in/51640/13 "2018-01-29T16:24:44Z")
> [@butrm2j](#): > > SSLCertificateFile "/opt/bitnami/apache2/conf/server.crt" > SSLCertificateKeyFile "/opt/bitnami/apache2/conf/server.key" > SSLCACertificateFile “/opt/bitnami/apache2/conf/server-ca.crt” By default, this is not where Certbot places certificates. You'll likely need to either copy them from `/etc/letsencrypt/live/compliancecorporate.es/, or point these directives to the files in this directory (cert.pem, privkey.pem, and chain.pem, respectively.) ---
**Author:** ![butrm2j](https://avatars.discourse-cdn.com/v4/letter/b/0ea827/32.png) [@butrm2j](https://community.letsencrypt.org/u/butrm2j)\ **Post date:** [January 29, 2018, 4:32pm UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain-in/51640/14 "2018-01-29T16:32:45Z")
I have done it and I have restart the webserver… but I continue getting the 15 feb 2018 ---
**Author:** ![butrm2j](https://avatars.discourse-cdn.com/v4/letter/b/0ea827/32.png) [@butrm2j](https://community.letsencrypt.org/u/butrm2j)\ **Post date:** [January 29, 2018, 4:35pm UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain-in/51640/15 "2018-01-29T16:35:02Z")
# Default Virtual Host configuration. \ NameVirtualHost \*:80 NameVirtualHost \*:443 Redirect permanent / https://www.compliancecorporate.es/ ServerName compliancecorporate.es ServerAlias compliancecorporate.es www.compliancecorporate.es DocumentRoot "/opt/bitnami/apache2/htdocs" Options Indexes FollowSymLinks AllowOverride All Order allow,deny Allow from all = 2.3 \> Require all granted # Error Documents ErrorDocument 503 /503.html # Bitnami applications installed with a prefix URL (default) Include “/opt/bitnami/apache2/conf/bitnami/bitnami-apps-prefix.conf” # Default SSL Virtual Host configuration. \ LoadModule ssl\_module modules/mod\_ssl.so Listen 443 SSLProtocol all -SSLv2 -SSLv3 SSLHonorCipherOrder on SSLCipherSuite "EECDH+ECDSA+AESGCM EECDH+aRSA+AESGCM EECDH+ECDSA+SHA384 EECDH+ECDSA+SHA256 EECDH+aRSA+SHA384 EECDH+aRSA+SHA256 EECDH !aNULL !eNULL !LOW !3DES !MD5 !EXP !PSK !$ SSLPassPhraseDialog builtin SSLSessionCache "shmcb:/opt/bitnami/apache2/logs/ssl\_scache(512000)" SSLSessionCacheTimeout 300 Redirect permanent /secure https://www.compliancecorporate.es ServerName compliancecorporate.es ServerAlias compliancecorporate.es www.compliancecorporate.es DocumentRoot "/opt/bitnami/apache2/htdocs" SSLEngine on SSLCertificateFile "/etc/letsencrypt/live/compliancecorporate.es/server.crt" SSLCertificateKeyFile "/etc/letsencrypt/live/compliancecorporate.es/server.key" SSLCACertificateFile "/etc/letsencrypt/live/compliancecorporate.es/server-ca.crt" Options Indexes FollowSymLinks AllowOverride All Order allow,deny Allow from all = 2.3 \> Require all granted # Error Documents ErrorDocument 503 /503.html # Bitnami applications installed with a prefix URL (default) Include “/opt/bitnami/apache2/conf/bitnami/bitnami-apps-prefix.conf” # Bitnami applications that uses virtual host configuration Include “/opt/bitnami/apache2/conf/bitnami/bitnami-apps-vhosts.conf” ---
**Author:** ![sahsanu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sahsanu/32/89984_2.png) [@sahsanu](https://community.letsencrypt.org/u/sahsanu)\ **Post date:** [January 29, 2018, 4:50pm UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain-in/51640/16 "2018-01-29T16:50:30Z")
> [@butrm2j](#): > > SSLCertificateFile "/etc/letsencrypt/live/compliancecorporate.es/server.crt" > SSLCertificateKeyFile "/etc/letsencrypt/live/compliancecorporate.es/server.key" > SSLCACertificateFile "/etc/letsencrypt/live/compliancecorporate.es/server-ca.crt" As @jared.m already said, this should be: ``` SSLCertificateFile "/etc/letsencrypt/live/compliancecorporate.es/cert.pem" SSLCertificateKeyFile "/etc/letsencrypt/live/compliancecorporate.es/privkey.pem" SSLCACertificateFile "/etc/letsencrypt/live/compliancecorporate.es/chain.pem" ``` ---
**Author:** ![butrm2j](https://avatars.discourse-cdn.com/v4/letter/b/0ea827/32.png) [@butrm2j](https://community.letsencrypt.org/u/butrm2j)\ **Post date:** [January 29, 2018, 5:05pm UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain-in/51640/17 "2018-01-29T17:05:17Z")
Thank you so much!! The new expiration date appears correctly! ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [February 28, 2018, 5:05pm UTC](https://community.letsencrypt.org/t/the-server-could-not-connect-to-the-client-to-verify-the-domain-in/51640/18 "2018-02-28T17:05:34Z")
Closed on February 28, 2018, 5:05pm UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.