# Configuration apache et certbot

**URL:** <https://community.letsencrypt.org/t/configuration-apache-et-certbot/252066>\
**Category:** Aide (en français)\
**Created:** [October 11, 2026, 7:13am UTC](https://community.letsencrypt.org/t/configuration-apache-et-certbot/252066 "2026-10-11T07:13:29Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![cedricguillouet](https://avatars.discourse-cdn.com/v4/letter/c/49beb7/32.png) [@cedricguillouet](https://community.letsencrypt.org/u/cedricguillouet)\
**Post date:** [October 11, 2026, 7:13am UTC](https://community.letsencrypt.org/t/configuration-apache-et-certbot/252066/1 "2026-10-11T07:13:29Z")

</div>

Bonjour,

je tente de configurer moi même apache en https. J'ai un nom de domaine qui pointe vers mon ip publique ipv4 et ipv6. Dans ma zone dns je n'avais pas de dns AAAA, j'en ai créé un en indiquant mon adresse ipv6, je ne sais pas si c'est correct, ça me semble bizarre. Quand je rentre mon ipv4 dans le navigateur je tombe bien sur mon site. www.eveil.site ne renvoie rien...  
Merci pour vos réponses, en ce dimanche

Je peux lire des réponses en Anglais : oui

Mon nom de domaine est : eveil.site

J’ai exécuté cette commande : sudo certbot --apache

Elle a produit cette sortie : Error reading HTTP response body: reader size limit exceeded

Mon serveur Web est (inclure la version) : apache 2.4.68

Le système d’exploitation sur lequel mon serveur Web s’exécute est (version incluse) : raspberryos

Mon hébergeur, le cas échéant, est : auto hébergé

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

---

<div class="post-metadata">

**Author:** ![bruncsak](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruncsak/32/18414_2.png) [@bruncsak](https://community.letsencrypt.org/u/bruncsak)\
**Post date:** [October 11, 2026, 9:16am UTC](https://community.letsencrypt.org/t/configuration-apache-et-certbot/252066/2 "2026-10-11T09:16:01Z")

</div>

@cedricguillouet, welcome to the community! 🙂

Where is the IP address `2a01:e0a:af9:67f0:7e5:cc66:4249:3ca8` coming from?  
Is it visible on the output of the command :`ip -6 addr show scope global | grep inet6` ?  
If yes, is the IP address opened for inbound connection of HTTP/HTTPS protocol in the router?

---

<div class="post-metadata">

**Author:** ![orangepizza](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/orangepizza/32/19597_2.png) [@orangepizza](https://community.letsencrypt.org/u/orangepizza)\
**Post date:** [October 11, 2026, 10:00am UTC](https://community.letsencrypt.org/t/configuration-apache-et-certbot/252066/3 "2026-10-11T10:00:47Z")

</div>

and while IPv6 doesn't do NAT it doesn't mean your router aren't running firewall for it, so you'll need to make a rule on router to open port 80/443 for your PI's IPv6 address

---

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [October 11, 2026, 1:17pm UTC](https://community.letsencrypt.org/t/configuration-apache-et-certbot/252066/4 "2026-10-11T13:17:36Z")

</div>

You used the --apache option but an `openresty` server is handling at least some of this request. Looks like OVHcloud is processing the initial request to your domain. Once you get a cert do you know how this OVH front end will handle an HTTPS request? Does it also need a cert so it can process the HTTPS

The error is because cert HTTP Challenge requests are being redirected by that openresty to your home page which is a much larger response than appropriate for an HTTP Challenge.

Examples below are for IPv4 because your IPv6 is not working. Let's Encrypt is falling back to IPv4 and gets these responses

```nohighlight
curl -i4 http://eveil.site/.well-known/acme-challenge/Test404
HTTP/1.1 302 Moved Temporarily
server: openresty
content-length: 142
location: http://www.eveil.site/.well-known/acme-challenge/Test404
x-iplb-request-id: 36C52736:C902_D5BA2105:0050_6ACB8AB9_B0893D82:1ADB5
x-iplb-instance: 52193

# Following the redirect to www redirects to your home page
curl -i4 http://www.eveil.site/.well-known/acme-challenge/Test404
HTTP/1.1 302 Moved Temporarily
server: openresty
content-length: 142
location: http://www.eveil.site
x-iplb-request-id: 36C52736:C3C8_D5BA2105:0050_6ACB8ACF_B0897D03:1ADB5
x-iplb-instance: 52193

#
curl -i4 http://www.eveil.site
HTTP/1.1 200 OK
server: openresty
content-type: text/html; charset=utf8
content-length: 13878
x-iplb-request-id: 36C52736:CC5C_D5BA2105:0050_6ACB8AD8_B0380947:18FD52
x-iplb-instance: 52243

```

---

<div class="post-metadata">

**Author:** ![cedricguillouet](https://avatars.discourse-cdn.com/v4/letter/c/49beb7/32.png) [@cedricguillouet](https://community.letsencrypt.org/u/cedricguillouet)\
**Post date:** [October 11, 2026, 2:11pm UTC](https://community.letsencrypt.org/t/configuration-apache-et-certbot/252066/5 "2026-10-11T14:11:22Z")

</div>

> [@bruncsak](#):
>
> ip -6 addr show scope global | grep inet6

ip -6 addr show scope global | grep inet6  
inet6 2a01:e0a:af9:67f0:fa86:9ff:cefd:d28a/64 scope global temporary dynamic  
inet6 2a01:e0a:af9:67f0:740f:a655:d45f:dbc4/64 scope global dynamic mngtmpaddr noprefixroute

---

<div class="post-metadata">

**Author:** ![cedricguillouet](https://avatars.discourse-cdn.com/v4/letter/c/49beb7/32.png) [@cedricguillouet](https://community.letsencrypt.org/u/cedricguillouet)\
**Post date:** [October 11, 2026, 2:18pm UTC](https://community.letsencrypt.org/t/configuration-apache-et-certbot/252066/6 "2026-10-11T14:18:28Z")

</div>

thanks for your replies.

I made rules to open port 80/443 on the firewall of the PI

The redirection is made on the router for the same port.

There was bad redirection on the ovh's configuration.  
In the dns zone, there was A adress but not with my ip, i put that.  
I've made a name server with my ip but it was wrong thing.

Excuse my english.

---

<div class="post-metadata">

**Author:** ![cedricguillouet](https://avatars.discourse-cdn.com/v4/letter/c/49beb7/32.png) [@cedricguillouet](https://community.letsencrypt.org/u/cedricguillouet)\
**Post date:** [October 11, 2026, 2:33pm UTC](https://community.letsencrypt.org/t/configuration-apache-et-certbot/252066/7 "2026-10-11T14:33:25Z")

</div>

Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:  
Domain: eveil.site  
Type: unauthorized  
Detail: 2a01:e0a:af9:67f0:fa86:9ff:cefd:d28a: Invalid response from [http://eveil.site/.well-known/acme-challenge/-Rhf6vn9DRRS6LMfw5fP26p-knh-zf69T2BSktQC-GE:](http://eveil.site/.well-known/acme-challenge/-Rhf6vn9DRRS6LMfw5fP26p-knh-zf69T2BSktQC-GE:) 404

Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache server and that it is accessible from the internet.

---

<div class="post-metadata">

**Author:** ![bruncsak](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruncsak/32/18414_2.png) [@bruncsak](https://community.letsencrypt.org/u/bruncsak)\
**Post date:** [October 11, 2026, 2:37pm UTC](https://community.letsencrypt.org/t/configuration-apache-et-certbot/252066/8 "2026-10-11T14:37:18Z")

</div>

You may want to have a look at this:

> **[Test result for eveil.site: Warning](https://letsdebug.net/eveil.site/3211151)**
>
> 1 unique issue(s) detected (MultipleIPAddressDiscrepancy)

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [October 13, 2026, 2:37pm UTC](https://community.letsencrypt.org/t/configuration-apache-et-certbot/252066/9 "2026-10-13T14:37:45Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
