SKIP_CONNECTION_TEST does not work on install-discourse script

I’ve tried basically everything I can imagine and nothing is working so I can only infer that this is a bug.

Things I’ve tried:

  • SKIP_CONNECTION_TEST=1 ./install-discourse
  • export SKIP_CONNECTION_TEST=1; ./install-discourse
  • Commenting out the line in my local discourse-setup copy

yet it still whines that there is no port 443 (which is not an issue because I am under a reverse proxy):

root@discourse:~/discourse_docker# ./install-discourse 

Discourse One-Line Installer

→ Docker is already installed
==> Setting up Discourse Docker
→ Existing installation found at /var/discourse
→ Updating repository...
HEAD is now at 2ad96ec DEV: Remove ruby 3.4 build step (#1042)
→ Repository ready at /var/discourse
==> Starting Discourse Setup Wizard

→ Checking for setup wizard image updates...
release: Pulling from discourse/setup-wizard
Digest: sha256:7ca57ab89b6659bea41f78ed667876ef8f00d80f4addfea9ec7907f1bf5ad544
Status: Image is up to date for discourse/setup-wizard:release
docker.io/discourse/setup-wizard:release
→ Starting Discourse Setup Wizard...


 ___  _
|   \(_)___ __ ___ _  _ _ _ ___ ___
| |) | (_-</ _/ _ \ || | '_(_-</ -_)
|___/|_/__/\__\___/\_,_|_| /__/\___|
                       Setup Wizard


→ This wizard will help you configure your Discourse installation.
→ Press Ctrl+C at any time to cancel.

── System Checks ──

[1/5] Verifying system requirements
✓ Running as root
✓ Docker is available
✓ Memory: 33GB, CPU: 112 cores

── Configuration ──

[2/5] Preparing configuration
✓ Ports 80 and 443 are free for use
→ Creating new configuration...
→ Creating new configuration from template...

── Site Settings ──

[3/5] Enter your site details

Email address for admin account(s)?
[redacted]@proton.me▌

Do you have a domain name for your Discourse?
▸ Yes      No

Hostname for your Discourse?
discourse.pyxfluff.dev▌

Configure SMTP for sending emails? (Requires SMTP credentials)
  Yes    ▸ No


── Review Configuration ──


╭────────────────────────────────────────────╮
│                                            │
│  Hostname       discourse.pyxfluff.dev     │
│  Admin Email    [redacted]@proton.me        │
│  SMTP           (not configured)           │
│  Let's Encrypt  Enabled                    │
│                                            │
╰────────────────────────────────────────────╯


Does this look right?
▸ Yes      No
→ Found 33GB of memory and 112 CPU cores
→ Setting db_shared_buffers = 4096MB
→ Setting UNICORN_WORKERS = 8

── Network Validation ──

[4/5] Verifying domain configuration
→ Checking your domain name...
⚠ Port 443 of this computer does not appear to be accessible using hostname: discourse.pyxfluff.dev

✓ A connection to port 80 succeeds!
This suggests that your DNS settings are correct,
but something is keeping traffic to port 443 from getting to your server.
Check your networking configuration to see that connections to port 443 are allowed.

The first thing to do is confirm that discourse.pyxfluff.dev resolves to the IP address of this server.
You usually do this at the same place you purchased the domain.

If you are sure that the IP address resolves correctly, it could be a firewall issue.
A web search for "open ports YOUR CLOUD SERVICE" might help.

This tool is designed only for the most standard installations. If you cannot resolve
the issue above, you will need to edit containers/app.yml yourself and then type:

    ./launcher rebuild app


✗ DNS verification failed for discourse.pyxfluff.dev
root@discourse:~/discourse_docker# 

I can confirm the environment variable is properly set:

There isn’t much else I can do here, seems like I’m at a loss with this script at the moment which is a shame because I don’t want to have to use SMTP. Looks like it was made for cloud hosting and cloud hosting only (where having multiple services on one IP is not really a problem)

1 Like

I’ve used skip-connection-test before but I think it is a switch for the command like so

./install-discourse --skip-connection-test

I’m unsure of the exact syntax but I do remember it was not real easy to find in the documentation

2 Likes

Thanks this did work for me now. I still find it weird/unintended the environment variable didn’t work and a potential issue but I’ll let staff decide that

2 Likes

I was wondering why it was refusing connections and it seems like the script did not even try to configure the site.