Well, I find myself in a similar predicament 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 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-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:
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: email@example.com DISCOURSE_SMTP_PASSWORD: <PASSWORD> #DISCOURSE_SMTP_DOMAIN: discourse.example.com # (required by some providers) #DISCOURSE_NOTIFICATION_EMAIL: firstname.lastname@example.org # (address to send notifications from) DISCOURSE_SMTP_ENABLE_START_TLS: true LETSENCRYPT_ACCOUNT_EMAIL: email@example.com #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?
I can ping the URL fine and it points to the right IP.