# Apache2 client denied by server configuration

**URL:** <https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846>\
**Category:** Help\
**Created:** [December 2, 2022, 9:24am UTC](https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846 "2022-12-02T09:24:10Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Davidoffo](https://avatars.discourse-cdn.com/v4/letter/d/e9a140/32.png) [@Davidoffo](https://community.letsencrypt.org/u/Davidoffo)\
**Post date:** [December 2, 2022, 9:24am UTC](https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846/1 "2022-12-02T09:24:10Z")

</div>

Hello,

I am fairly new to certificates and I am having some issues I don't understand. Hope someone can help me out or push me in the right direction.

**My domain is:**

```nohighlight
nederheim.nl

```

**I ran this command:**

```nohighlight
sudo certbot certonly --apache -v --dry-run

```

**It produced this output:**

```nohighlight
Performing the following challenges:
http-01 challenge for nederheim.nl
http-01 challenge for www.nederheim.nl
Waiting for verification...
Challenge failed for domain nederheim.nl
Challenge failed for domain www.nederheim.nl
http-01 challenge for nederheim.nl
http-01 challenge for www.nederheim.nl

Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
  Domain: nederheim.nl
  Type: unauthorized
  Detail: 92.108.177.33: Invalid response from http://nederheim.nl/.well-known/acme-challenge/3IgHPBz_9SnWclnot5w9btJe29OVy4zBxdalz4eu68s: 403

  Domain: www.nederheim.nl
  Type: unauthorized
  Detail: 92.108.177.33: Invalid response from http://www.nederheim.nl/.well-known/acme-challenge/-SSCoBf6SMdLHWb0-dIIMMajj4x04pMV6VqPis1gi2o: 403

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.

```

**My web server is (include version):**

```nohighlight
Apache/2.4.52 (Ubuntu)

```

The operating system my web server runs on is (include version):

```nohighlight
Ubuntu 22.04.1 LTS

```

**My hosting provider, if applicable, is:**

```nohighlight
TransIP

```

**I can login to a root shell on my machine (yes or no, or I don't know):**

```nohighlight
Yes

```

**I'm using a control panel to manage my site (no, or provide the name and version of the control panel):**

```nohighlight
No

```

The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot):

```nohighlight
certbot 1.32.0

```

**Log from apache2**

```nohighlight
[Fri Dec 02 09:57:49.699509 2022] [access_compat:error] [pid 790742] [client 3.17.74.78:53568] AH01797: client denied by server configuration: /var/lib/letsencrypt/http_challenges/3IgHPBz_9SnWclnot5w9btJe29OVy4zBxdalz4eu68s
[Fri Dec 02 09:57:49.873331 2022] [access_compat:error] [pid 790743] [client 54.202.242.235:12338] AH01797: client denied by server configuration: /var/lib/letsencrypt/http_challenges/3IgHPBz_9SnWclnot5w9btJe29OVy4zBxdalz4eu68s
[Fri Dec 02 09:57:49.906330 2022] [access_compat:error] [pid 790744] [client 23.178.112.107:19374] AH01797: client denied by server configuration: /var/lib/letsencrypt/http_challenges/3IgHPBz_9SnWclnot5w9btJe29OVy4zBxdalz4eu68s
[Fri Dec 02 09:57:49.939463 2022] [access_compat:error] [pid 790745] [client 3.17.74.78:53578] AH01797: client denied by server configuration: /var/lib/letsencrypt/http_challenges/-SSCoBf6SMdLHWb0-dIIMMajj4x04pMV6VqPis1gi2o
[Fri Dec 02 09:57:50.147336 2022] [access_compat:error] [pid 790746] [client 54.202.242.235:12352] AH01797: client denied by server configuration: /var/lib/letsencrypt/http_challenges/-SSCoBf6SMdLHWb0-dIIMMajj4x04pMV6VqPis1gi2o
[Fri Dec 02 09:57:50.169706 2022] [access_compat:error] [pid 790742] [client 23.178.112.106:26592] AH01797: client denied by server configuration: /var/lib/letsencrypt/http_challenges/-SSCoBf6SMdLHWb0-dIIMMajj4x04pMV6VqPis1gi2o

```

**/etc/sites-available settings**

```nohighlight
<VirtualHost <server ip>:80>
    ServerName www.nederheim.nl
    ServerAlias nederheim.nl

    DocumentRoot /var/www/html

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

    <Directory /var/lib/letsencrypt/http_challenges>
        Require all granted
    </Directory>
    <Location /.well-known/acme-challenge>
        Require all granted
    </Location>
</VirtualHost>

```

```nohighlight
<VirtualHost <server ip>:443>
    ServerName www.nederheim.nl
    ServerAlias nederheim.nl

    DocumentRoot /var/www/html
    
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

    <Directory /var/lib/letsencrypt/http_challenges>
    	Require all granted
    </Directory>
    <Location /.well-known/acme-challenge>
        Require all granted
    </Location>

</VirtualHost>

```

I am not sure if it makes sense to add the directory and location settings to both the virtual host settings of port 80 and 443 as I said I am fairly new to this 🙂

---

<div class="post-metadata">

**Author:** ![Davidoffo](https://avatars.discourse-cdn.com/v4/letter/d/e9a140/32.png) [@Davidoffo](https://community.letsencrypt.org/u/Davidoffo)\
**Post date:** [December 2, 2022, 10:55am UTC](https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846/2 "2022-12-02T10:55:03Z")

</div>

I just noticed my site is not reachable to the public which makes sense why letsencrypt cannot make any connection. I think it is only reachable for certain IP adresses (such as my own) which why I didn't notice it before.

---

<div class="post-metadata">

**Author:** ![Rip](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rip/32/70863_2.png) [@Rip](https://community.letsencrypt.org/u/Rip)\
**Post date:** [December 2, 2022, 12:22pm UTC](https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846/3 "2022-12-02T12:22:22Z")

</div>

Hi @Davidoffo and welcome to the forum.  
If it helps any, I can reach your site on both port(s) 80 and 443.  
**HTTPS is serving a LE Certificate valid until Thu, 02 Mar 2023 10:41:05 GMT**

 ![2](https://global.discourse-cdn.com/letsencrypt/original/3X/2/e/2e9a2bb2b4c4789e1b5fe83751fc585ccfd91c12.png)

* * *

 ![1](https://global.discourse-cdn.com/letsencrypt/original/3X/2/c/2c7690b43197adaf9d7f3470c40adfba26faf963.png)

So at least you know others can access your site at this time. (I am in Oregon USA)  
As for the

```nohighlight
 AH01797: client denied by server configuration

```

It looks like that is a _permissions issue_ that needs to be resolved for sure. ~~I am certain another volunteer here would help you with your Apache configuration _even though it is a bit out of scope for this forum._~~  
Personally I suspect this directive may have something to do with the issue.

> [@Davidoffo](#):
>
> ```nohighlight
> <Directory /var/lib/letsencrypt/http_challenges>
> Require all granted
> </Directory>
> 
> ```

**Take a read here:**

> [@Wrong rights for /var/lib/letsencrypt/http\_challenges (0700 instead of 0755)](https://community.letsencrypt.org/t/wrong-rights-for-var-lib-letsencrypt-http-challenges-0700-instead-of-0755/102885):
>
> I…

ALSO if you share the output of the following commands it will help.

```nohighlight
apache2ctl -S
apache2ctl -t -D DUMP_VHOSTS

```

---

<div class="post-metadata">

**Author:** ![Davidoffo](https://avatars.discourse-cdn.com/v4/letter/d/e9a140/32.png) [@Davidoffo](https://community.letsencrypt.org/u/Davidoffo)\
**Post date:** [December 2, 2022, 1:50pm UTC](https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846/4 "2022-12-02T13:50:15Z")

</div>

Hey thanks for your reply!

I was able to fix my issue to add this to my virtual host file:

```nohighlight
<Location />
    Allow from all
</Location>

```

After this is was able to reach the site with certbot and a certificate was successfully installed 🙂

If you think this is wrong let me know!

---

<div class="post-metadata">

**Author:** ![Bruce5051](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruce5051/32/76576_2.png) [@Bruce5051](https://community.letsencrypt.org/u/Bruce5051)\
**Post date:** [December 2, 2022, 3:32pm UTC](https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846/5 "2022-12-02T15:32:02Z")

</div>

> [@Davidoffo](#):
>
> `http://www.nederheim.nl/.well-known/acme-challenge/-SSCoBf6SMdLHWb0-dIIMMajj4x04pMV6VqPis1gi2o`

Doesn't seem like the proper responses are being sent for the HTTP-01 Challenges

```nohighlight
$ curl -I http://nederheim.nl/.well-known/acme-challenge/3IgHPBz_9SnWclnot5w9btJe29OVy4zBxdalz4eu68s
HTTP/1.1 302 Found
Date: Fri, 02 Dec 2022 15:29:05 GMT
Server: Apache/2.4.52 (Ubuntu)
Location: https://www.nederheim.nl.well-known/acme-challenge/3IgHPBz_9SnWclnot5w9btJe29OVy4zBxdalz4eu68s
Content-Type: text/html; charset=iso-8859-1

$ curl -I http://www.nederheim.nl/.well-known/acme-challenge/-SSCoBf6SMdLHWb0-dIIMMajj4x04pMV6VqPis1gi2o
HTTP/1.1 302 Found
Date: Fri, 02 Dec 2022 15:29:26 GMT
Server: Apache/2.4.52 (Ubuntu)
Location: https://www.nederheim.nl.well-known/acme-challenge/-SSCoBf6SMdLHWb0-dIIMMajj4x04pMV6VqPis1gi2o
Content-Type: text/html; charset=iso-8859-1

```

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [December 2, 2022, 5:38pm UTC](https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846/6 "2022-12-02T17:38:05Z")

</div>

> [@Rip](#):
>
> ALSO if you share the output of the following commands it will help.
> 
> ```nohighlight
> apache2ctl -S
> apache2ctl -t -D DUMP_VHOSTS
> 
> ```

We are dealing with `Apache`.  
Take nothing for granted.

---

<div class="post-metadata">

**Author:** ![Davidoffo](https://avatars.discourse-cdn.com/v4/letter/d/e9a140/32.png) [@Davidoffo](https://community.letsencrypt.org/u/Davidoffo)\
**Post date:** [December 9, 2022, 12:35pm UTC](https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846/7 "2022-12-09T12:35:49Z")

</div>

Sorry for my late response. You are right there is still something wrong. See the output:

```nohighlight
AH00526: Syntax error on line 9 of /etc/apache2/sites-enabled/nederheim-ssl.conf:
SSLCertificateFile: file '/etc/letsencrypt/live/nederheim.nl/fullchain.pem' does not exist or is empty
Action '-t -D DUMP_VHOSTS' failed.

```

I am not sure why it is giving this message, because the file does exist at the given location.

---

<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:** [December 9, 2022, 1:43pm UTC](https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846/8 "2022-12-09T13:43:20Z")

</div>

> [@Davidoffo](#):
>
> I am not sure why it is giving this message,

Need to use sudo for those like:

```nohighlight
sudo apache2ctl -S
sudo apache2ctl -t -D DUMP_VHOSTS

```

Lack of permissions prevent Apache from reading the cert files

---

<div class="post-metadata">

**Author:** ![Davidoffo](https://avatars.discourse-cdn.com/v4/letter/d/e9a140/32.png) [@Davidoffo](https://community.letsencrypt.org/u/Davidoffo)\
**Post date:** [December 9, 2022, 2:06pm UTC](https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846/9 "2022-12-09T14:06:29Z")

</div>

A yes. Here the output with sudo rights:

```nohighlight
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using <serverip>. Set the 'ServerName' directive globally to suppress this message
VirtualHost configuration:
<serverip> is a NameVirtualHost
         default server jan.upcycle.nederheim.nl (/etc/apache2/sites-enabled/jan.upcycle-ssl.conf:1)
         port 443 namevhost jan.upcycle.nederheim.nl (/etc/apache2/sites-enabled/jan.upcycle-ssl.conf:1)
                 alias www.jan.upcycle.nederheim.nl
         port 443 namevhost (/etc/apache2/sites-enabled/default-ssl.conf:2)
         port 443 namevhost gitlab.nederheim.nl (/etc/apache2/sites-enabled/gitlab-ssl.conf:1)
                 alias www.gitlab.nederheim.nl
         port 443 namevhost mattermost.nederheim.nl (/etc/apache2/sites-enabled/mattermost-ssl.conf:1)
                 alias www.mattermost.nederheim.nl
         port 443 namevhost www.nederheim.nl (/etc/apache2/sites-enabled/nederheim-ssl.conf:1)
                 alias nederheim.nl
         port 443 namevhost jandirk.upcycle.nederheim.nl (/etc/apache2/sites-enabled/jandirk.upcycle-ssl.conf:1)
                 alias www.jandirk.upcycle.nederheim.nl
192.168.178.27:80 is a NameVirtualHost
         default server jan.upcycle.nederheim.nl (/etc/apache2/sites-enabled/jan.upcycle.conf:1)
         port 80 namevhost jan.upcycle.nederheim.nl (/etc/apache2/sites-enabled/jan.upcycle.conf:1)
                 alias www.jan.upcycle.nederheim.nl
         port 80 namevhost gitlab.nederheim.nl (/etc/apache2/sites-enabled/gitlab.conf:1)
         port 80 namevhost mattermost.nederheim.nl (/etc/apache2/sites-enabled/mattermost.conf:1)
         port 80 namevhost www.nederheim.nl (/etc/apache2/sites-enabled/nederheim.conf:1)
                 alias nederheim.nl
         port 80 namevhost jandirk.upcycle.nederheim.nl (/etc/apache2/sites-enabled/jandirk.upcycle.conf:1)
                 alias www.jandirk.upcycle.nederheim.nl

```

---

<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:** [December 9, 2022, 2:36pm UTC](https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846/10 "2022-12-09T14:36:34Z")

</div>

Can you show us the contents of this file. We'll start here to fix the problem with the redirect.

> [@Davidoffo](#):
>
> `/etc/apache2/sites-enabled/nederheim.conf`

Also, do you have any .htaccess file in use? If so, please show that too

---

<div class="post-metadata">

**Author:** ![Davidoffo](https://avatars.discourse-cdn.com/v4/letter/d/e9a140/32.png) [@Davidoffo](https://community.letsencrypt.org/u/Davidoffo)\
**Post date:** [December 9, 2022, 2:57pm UTC](https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846/11 "2022-12-09T14:57:45Z")

</div>

Contents of the "/etc/apache2/sites-enabled/nederheim.conf" file:

```nohighlight
<VirtualHost <serverip>:80>
    ServerName www.nederheim.nl
    ServerAlias nederheim.nl
    ServerAdmin <email>
    Redirect / https://www.nederheim.nl
    DocumentRoot /var/www/html

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
    <Location />
	Allow from all
    </Location>
</VirtualHost>

```

I should not have a .htaccess file in use.

---

<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:** [December 9, 2022, 3:06pm UTC](https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846/12 "2022-12-09T15:06:35Z")

</div>

> [@Davidoffo](#):
>
> `Redirect / https://www.nederheim.nl`

You need to add a `/` after .nl  
You will see a missing / in the Location response header from Bruce's example in post #5 if you look carefully.

Also, I recommend removing all the IP addresses from your VirtualHost so they are like:

```nohighlight
<VirtualHost *:80>
and 
<VirtualHost *:443>

```

It is very rare these days to need the IP address and it makes you vulnerable to changes in IP values.

You must change them all so they are the same though. Can't just do one at a time.

---

<div class="post-metadata">

**Author:** ![Davidoffo](https://avatars.discourse-cdn.com/v4/letter/d/e9a140/32.png) [@Davidoffo](https://community.letsencrypt.org/u/Davidoffo)\
**Post date:** [December 9, 2022, 3:45pm UTC](https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846/13 "2022-12-09T15:45:15Z")

</div>

That is a difficult one to see thanks! I changed the redirect in the config to:

`Redirect / https://www.nederheim.nl/`

But unfortunately I still have a similar response as seen from Bruce's example:

```nohighlight
curl -I http://www.nederheim.nl/.well-known/acme-challenge/-SSCoBf6SMdLHWb0-dIIMMajj4x04pMV6VqPis1gi2o
HTTP/1.1 302 Found
Date: Fri, 09 Dec 2022 15:40:56 GMT
Server: Apache/2.4.52 (Ubuntu)
Location: https://www.nederheim.nl/.well-known/acme-challenge/-SSCoBf6SMdLHWb0-dIIMMajj4x04pMV6VqPis1gi2o
Content-Type: text/html; charset=iso-8859-1

```

---

<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:** [December 9, 2022, 3:57pm UTC](https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846/14 "2022-12-09T15:57:06Z")

</div>

> [@Davidoffo](#):
>
> But unfortunately I still have a similar response as seen from Bruce's example:

No, it is different because the Location is now correct 🙂

Bruce's post: (note it is `.nl.well-known`)

```nohighlight
curl -I http://nederheim.nl/.well-known/acme-challenge/3IgHPBz_9SnWclnot5w9btJe29OVy4zBxdalz4eu68s
HTTP/1.1 302 Found
Location: https://www.nederheim.nl.well-known/acme-challenge/3IgHPBz_9SnWclnot5w9btJe29OVy4zBxdalz4eu68s

```

Yours is now `.nl/.well-known` as it should be:

```nohighlight
curl -I http://www.nederheim.nl/.well-known/acme-challenge/-SSCoBf6SMdLHWb0-dIIMMajj4x04pMV6VqPis1gi2o
HTTP/1.1 302 Found
Location: https://www.nederheim.nl/.well-known/acme-challenge/-SSCoBf6SMdLHWb0-dIIMMajj4x04pMV6VqPis1gi2o

```

---

<div class="post-metadata">

**Author:** ![Davidoffo](https://avatars.discourse-cdn.com/v4/letter/d/e9a140/32.png) [@Davidoffo](https://community.letsencrypt.org/u/Davidoffo)\
**Post date:** [December 9, 2022, 4:03pm UTC](https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846/15 "2022-12-09T16:03:08Z")

</div>

You are right! Thanks for the quick responses. I learned a lot 🙂

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [December 9, 2022, 6:44pm UTC](https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846/16 "2022-12-09T18:44:35Z")

</div>

> [@MikeMcQ](#):
>
> I recommend removing all the IP addresses from your VirtualHost

Did you make that change?

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [December 9, 2022, 6:48pm UTC](https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846/17 "2022-12-09T18:48:06Z")

</div>

This file has no server name:  
[if not used, it should be removed/deleted]

```nohighlight
port 443 namevhost (/etc/apache2/sites-enabled/default-ssl.conf:2)

```

These files lack the "`www`" alias [which are being used in the HTTPS vhost]:

```nohighlight
port 80 namevhost gitlab.nederheim.nl (/etc/apache2/sites-enabled/gitlab.conf:1)
port 80 namevhost mattermost.nederheim.nl (/etc/apache2/sites-enabled/mattermost.conf:1)

```

---

<div class="post-metadata">

**Author:** ![Davidoffo](https://avatars.discourse-cdn.com/v4/letter/d/e9a140/32.png) [@Davidoffo](https://community.letsencrypt.org/u/Davidoffo)\
**Post date:** [December 10, 2022, 9:16am UTC](https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846/18 "2022-12-10T09:16:02Z")

</div>

I understand the recommendation and advantages to remove the IP addresses as MikeMcQ said. But for now I like it to be as specific as possible for learning and understanding a bit more what I am doing if that makes sense.

I added the serverAlias for the files gitlab.conf and mattermost.conf thank you. I am still working on those files. Both of them have a reverse proxy to ngix. I am still trying to figure out how this works with letsencrypt. At the moment letsencrypt can not reach these websites. Which makes sense because of the reverse proxy.

Edit:  
Nevermind I just did a --dry-run and letsenecrypt now seems to be able to reach it! Could this be the case of the missing alias or any other changes I did?

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [December 10, 2022, 7:19pm UTC](https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846/19 "2022-12-10T19:19:32Z")

</div>

> [@Davidoffo](#):
>
> if that makes sense.

Unless your system has multiple IPs and you are binding certain sites only to certain IPs, NO, that doesn't make much sense. All you are doing is overcomplicating things.  
Binding to ALL IPs:port = Bind to IP#1:port [when only IP#1 exists]  
`*:80 = 10.11.12.13:80`

Moreso, when using IPs in the network 127.0.0.0/8, you run into the situation where they can't be reached from any IP outside of that network [i.e. Outside that system].

---

<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:** [January 9, 2023, 7:19pm UTC](https://community.letsencrypt.org/t/apache2-client-denied-by-server-configuration/188846/20 "2023-01-09T19:19:36Z")

</div>

Closed on January 9, 2023, 7:19pm UTC

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