app was not started ! ./discourse-doctor may help diagnose the problem. ./discourse-setup: line 260: *0: syntax error: operand expected (error token is “*0”) Hostname for your Discourse? [discourse.example.com]: .com Checking your domain name . . . WARNING: Port 443 of computer does not appear to be accessible using hostname: .com. WARNING: Connection to http://.com (port 80) also fails. This suggests that .com resolves to some IP address that does not reach this machine where you are installing discourse. The first thing to do is confirm that .com 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 I have couple questions : I have .com and there is site already running . Now I want to run discourse as .com/discourse . The app is running in front of load balancer . But do i need to anything on discourse side what port discourse is running ? When i do curl I can reach to the site but why discourse setup is erroring out is it ok ignore mail setup

[image] Shibi Ns: .com That should be your actual domain name, not just a TLD.

Not sure if it was replaced , but value is mydomain.com . I placed it between

Hi there, Shibi I’m still new here, but I runned into a similar situation last week. The easiest way to use your domain for two different servers is by using a sub-domain. You can do that by creating an A Record on your DNS provider specifying the hostname as sub-domain.your-domain.com, or just the sub-domain, and then point out the IP of the discourse instance. This article may help with the above solution. [image] Shibi Ns: I have .com and there is site already running . Now I want to run discourse as .com/discourse . The app is running in front of load balancer . But do i need to anything on discourse side The solution I suggested above may help you with that. I think this way of using it as a resource for your other application may be harder to set up. [image] Shibi Ns: what port discourse is running ? By using the official cloud setup script, it will run on port 80 by default. [image] Shibi Ns: When i do curl I can reach to the site but why discourse setup is erroring out Could you please give more details on that? [image] Shibi Ns: is it ok ignore mail setup If you do so, you won’t be able to send any emails like invitations and account register confirmations. But probably you can’t ignore the smtp setup. [image] Shibi Ns: WARNING: Port 443 of computer does not appear to be accessible using hostname: .com. WARNING: Connection to http://.com (port 80) also fails. By the way, 443 is the HTTPS port, it is used to establish the encryption. This means your domain is probably not configured correctly and the Discourse setup is not being able to reach your server.

[image] Shibi Ns: I placed it between That’s the problem. Just type the full name with no spaces and no angle brackets. And now your app.yml is broken. The easiest thing will be to rm containers/app.yml and start over.

I suspect he meant he placed it between <> in the post when he replaced his actual domain (see https://meta.discourse.org/raw/272567/1)

[image] Shibi Ns: This suggests that .com resolves to some IP address that does not reach this He said he is using this domain for another application, I believe the best way to go is setting up a sub-domain. Otherwise one would have to manually set up Nginx to serve both the prior app and Discourse in a resource route.

Yes more thinking about solution thats Nginx , but wasn’t sure if its any internal config

WARNING: Port 443 of computer does not appear to be accessible using hostname: <mydomain>.com

Product Support Self-hosting

shibi (Shibi Ns) September 3, 2024, 7:16am 11

Thanks @italo . I was able to solve most of issues currently stuck at mail config

Topic		Replies	Views
WARNING: This server does not appear to be accessible at Self-hosting	11	2936	March 19, 2020
Troubleshooting Port Access Self-hosting	25	2062	August 18, 2020
⚠ Port 443 of this computer does not appear to be accessible using hostname: metabolism.logophilia.eu ---- Product Support	8	334	June 6, 2026
Setting up Discourse Self-hosting	15	1351	September 18, 2021
Misconfigured DNS preventing discourse-setup completion Self-hosting	13	2069	March 21, 2020

WARNING: Port 443 of computer does not appear to be accessible using hostname: <mydomain>.com

Related topics