# Can't Reach Site (Take 2)

**URL:** https://meta.discourse.org/t/cant-reach-site-take-2/225037
**Category:** Self-hosting
**Created:** [April 22, 2022, 1:45pm UTC](https://meta.discourse.org/t/cant-reach-site-take-2/225037 "2022-04-22T13:45:37Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![TheEngineer](https://avatars.discourse-cdn.com/v4/letter/t/48db29/32.png) [@TheEngineer](https://meta.discourse.org/u/TheEngineer)
#### Post date: [April 22, 2022, 1:45pm UTC](https://meta.discourse.org/t/cant-reach-site-take-2/225037/1 "2022-04-22T13:45:37Z")

</div>

Well, I find myself in a [similar predicament](https://meta.discourse.org/t/cant-reach-site/224774) as I did earlier in the week.

I had a typo in app.yml before that was preventing my site from being reached. I’m going through the [Change the Domain](https://meta.discourse.org/t/change-the-domain-name-or-rename-my-discourse/16098?replies_to_post_number=115) thread and the rake completed, but I can’t reach the site.

Thinking I did the same thing and made a typo, I double checked:

```
DISCOURSE_HOSTNAME: discourse.delawarereef.club

```

When running `./discourse-setup` to I get the same:

```
Checking your domain name . . .
WARNING: Port 443 of computer does not appear to be accessible using hostname: 443.
WARNING: Connection to http://443 (port 80) also fails.

```

It makes me think I still have a typo somewhere that I’m just not seeing.

Top of the app.yml:

```plaintext
templates:
    - templates/postgres.template.yml
    - templates/redis.template.yml
    - templates/web.template.yml
    - templates/web.ratelimited.template.yml
    - templates/web.ssl.template.yml
    - templates/web.letsencrypt.ssl.template.yml
expose:
    - '80:80'
    - '443:443'
params:
    db_default_text_search_config: pg_catalog.english
    db_shared_buffers: 128MB
    version: tests-passed
env:
    LANG: en_US.UTF-8
    UNICORN_WORKERS: 2
    DISCOURSE_HOSTNAME: discourse.delawarereef.club
    DISCOURSE_DEVELOPER_EMAILS: <MY EMAIL>
    DISCOURSE_SMTP_ADDRESS: smtp.ionos.com
    DISCOURSE_SMTP_PORT: 587
    DISCOURSE_SMTP_USER_NAME: site@brandywinereef.club
    DISCOURSE_SMTP_PASSWORD: <PASSWORD>
  #DISCOURSE_SMTP_DOMAIN: discourse.example.com # (required by some providers)
  #DISCOURSE_NOTIFICATION_EMAIL: nobody@discourse.example.com # (address to send notifications from)
    DISCOURSE_SMTP_ENABLE_START_TLS: true
    LETSENCRYPT_ACCOUNT_EMAIL: site@brandywinereef.club
  #DISCOURSE_MAXMIND_LICENSE_KEY: 1234567890123456
    #DISCOURSE_USE_S3: true
    DISCOURSE_S3_REGION: us-east-1
    DISCOURSE_S3_ACCESS_KEY_ID: <KEY>
    DISCOURSE_S3_SECRET_ACCESS_KEY: <KEY>
    DISCOURSE_S3_CDN_URL: 'https://d2hneyr8lp58j4.cloudfront.net'
    DISCOURSE_S3_BUCKET: brcuploads
    DISCOURSE_S3_BACKUP_BUCKET: brcuploads-backups
    DISCOURSE_BACKUP_LOCATION: s3

```

Am I missing something obvious again?

EDIT:  
I can ping the URL fine and it points to the right IP.

---

<div class="post-metadata">

### Author: ![TheEngineer](https://avatars.discourse-cdn.com/v4/letter/t/48db29/32.png) [@TheEngineer](https://meta.discourse.org/u/TheEngineer)
#### Post date: [April 22, 2022, 2:21pm UTC](https://meta.discourse.org/t/cant-reach-site-take-2/225037/2 "2022-04-22T14:21:35Z")

</div>

OK, did a second rebuild manually and it just came up.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [May 22, 2022, 2:22pm UTC](https://meta.discourse.org/t/cant-reach-site-take-2/225037/3 "2022-05-22T14:22:30Z")

</div>

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