WARNING: Port 443 of computer does not appear to be accessible using hostname: <mydomain>.com. The issue is likely due to the domain resolving to an IP address that does not reach the machine where Discourse is being installed.
shibi has a site already running on <mydomain>.com and wants to run Discourse as <mydomain>.com/discourse, with the app running in front of a load balancer. italo suggests using a sub-domain by creating an A Record on the DNS provider, which would allow Discourse to run on a separate domain.
Discourse runs on port 80 by default. shibi is also experiencing issues with the Discourse setup erroring out, despite being able to reach the site using curl. italo recommends providing more details on the error.
Additionally, shibi asks if it’s okay to ignore mail setup, but italo advises against it, as it’s necessary for sending emails like invitations and account registration confirmations. italo provides a tutorial on setting up an SMTP service for email configuration.
shibi was able to solve most issues with the help of italo, but is currently stuck on mail configuration. pfaffman suggests starting over by removing the app.yml file and restarting the setup process.
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
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.
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.
By using the official cloud setup script, it will run on port 80 by default.
Could you please give more details on that?
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.
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.
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.
For the email setup you will need an SMTP service, this tutorial has a list of the ones Discourse recommend. Although Gmail, Outlook and Yahoo have an SMTP option, they don’t support transactional emails, which is needed.
