Interesting, that would be unexpected but I’ll give that a go and see.
Okay – Update:
Running the setup didn’t change anything. I simply prompted me for the host and adjusted some minor settings. So far still no go. Same error on rebuild. I also tried running the doctor to no avail.
The setup did complain that the host was unreachable on the given port which isn’t true.
I am serving via nginx proxy:
location / {
error_page 502 =502 /errors/discourse-offline.html;
proxy_intercept_errors on;
proxy_headers_hash_max_size 1024;
proxy_headers_hash_bucket_size 128;
proxy_pass http://unix:/var/discourse/shared/standalone/nginx.http.sock:;
proxy_set_header Host $http_host;
proxy_http_version 1.1;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto https;
proxy_set_header X-Real-IP $remote_addr;
}
}
That might need some tweaking potentially but If it’s failing to build it shouldn’t even be a web server issue yet.