# Timeout on Multiple Self-Hosted Domains **URL:** \ **Category:** Help\ **Created:** [April 22, 2020, 1:37pm UTC](https://community.letsencrypt.org/t/timeout-on-multiple-self-hosted-domains/120380 "2020-04-22T13:37:14Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![grlucas](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/grlucas/32/39095_2.png) [@grlucas](https://community.letsencrypt.org/u/grlucas)\ **Post date:** [April 22, 2020, 1:37pm UTC](https://community.letsencrypt.org/t/timeout-on-multiple-self-hosted-domains/120380/1 "2020-04-22T13:37:14Z")
Sorry if this is an obvious issues, but I have searched for answers before posting. I’m having the same problems on several domains, but here is an example one. My domain is: [students.grlucas.net](http://students.grlucas.net) I ran this command: sudo letsencrypt --apache It produced this output: Obtaining a new certificate Performing the following challenges: http-01 challenge for [students.grlucas.net](http://students.grlucas.net) Waiting for verification… Cleaning up challenges Failed authorization procedure. [students.grlucas.net](http://students.grlucas.net) (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching [http://students.grlucas.net/.well-known/acme-challenge/uS2\_aimZxvFsAiS0PSu2sr1fEMP1WiQHgSmy1a0Cp9E:](http://students.grlucas.net/.well-known/acme-challenge/uS2_aimZxvFsAiS0PSu2sr1fEMP1WiQHgSmy1a0Cp9E:) Timeout during connect (likely firewall problem) My web server is (include version): Apache/2.4.38 (Raspbian) The operating system my web server runs on is (include version): Raspbian My hosting provider, if applicable, is: self-hosted I can login to a root shell on my machine (yes or no, or I don’t know): yes I’m using a control panel to manage my site (no, or provide the name and version of the control panel): no 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 I recently set up a reverse proxy with the following configuration: ``` ServerName students.grlucas.net ProxyPreserveHost On DocumentRoot /var/www/html ProxyPass /.well-known ! ProxyPass / http://10.0.1.21:80/ ProxyPassReverse / http://10.0.1.21:80/ ``` I notice there are no files written in ./well-known/acme-challenge. — should there be? I created the directories and gave the web server write permissions. I’m just not sure what else to try. TIA. ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [April 22, 2020, 1:48pm UTC](https://community.letsencrypt.org/t/timeout-on-multiple-self-hosted-domains/120380/2 "2020-04-22T13:48:22Z")
Hi @grlucas > [@grlucas](#): > > Failed authorization procedure. [students.grlucas.net](http://students.grlucas.net) (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching [http://students.grlucas.net/.well-known/acme-challenge/uS2\_aimZxvFsAiS0PSu2sr1fEMP1WiQHgSmy1a0Cp9E:](http://students.grlucas.net/.well-known/acme-challenge/uS2_aimZxvFsAiS0PSu2sr1fEMP1WiQHgSmy1a0Cp9E:) Timeout during connect (likely firewall problem) your port 80 doesn't answer. A working port 80 is required to create a certificate via http validation. Read > **[Challenge Types - Let's Encrypt](https://letsencrypt.org/docs/challenge-types/)** > > When you get a certificate from Let’s Encrypt, our servers validate that you control the domain names in that certificate using “challenges,” as defined by the ACME standard. Most of the time, this validation is handled automatically by your ACME... ---
**Author:** ![grlucas](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/grlucas/32/39095_2.png) [@grlucas](https://community.letsencrypt.org/u/grlucas)\ **Post date:** [April 22, 2020, 1:59pm UTC](https://community.letsencrypt.org/t/timeout-on-multiple-self-hosted-domains/120380/3 "2020-04-22T13:59:01Z")
Thanks for the reply. If port 80 doesn’t work, how come the site loads? Or is it not loading from outside my network? ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [April 22, 2020, 2:01pm UTC](https://community.letsencrypt.org/t/timeout-on-multiple-self-hosted-domains/120380/4 "2020-04-22T14:01:02Z")
> [@grlucas](#): > > If port 80 doesn’t work, how come the site loads? Or is it not loading from outside my network? It doesn't work. There is a check of your domain - [https://check-your-website.server-daten.de/?q=students.grlucas.net](https://check-your-website.server-daten.de/?q=students.grlucas.net) http has timeouts, https answers. ---
**Author:** ![grlucas](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/grlucas/32/39095_2.png) [@grlucas](https://community.letsencrypt.org/u/grlucas)\ **Post date:** [April 23, 2020, 5:07pm UTC](https://community.letsencrypt.org/t/timeout-on-multiple-self-hosted-domains/120380/5 "2020-04-23T17:07:49Z")
Ugh, yes, I see that now. For some reason port 80 was working for me for a while and it seems my ISP decided to block it. I should have checked that first. Thanks. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [May 23, 2020, 5:17pm UTC](https://community.letsencrypt.org/t/timeout-on-multiple-self-hosted-domains/120380/6 "2020-05-23T17:17:43Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.