The discussion revolves around the installation of Discourse and a problem with the hostname not being accessible. The user, Lxm, is unsure what their hostname should be and is seeking help.
Ghan explains that the hostname should be a DNS name that routes to the server where Discourse is being installed. To resolve the issue, Lxm needs to update their DNS settings or remove the existing forum and use the server to install Discourse.
Lxm is then advised by Ghan and pfaffman to create a DNS record for their server and ensure that their hostname resolves to their server IP address.
In the process of troubleshooting, Lxm encounters a PostgreSQL error, which they share in post 11. However, the discussion about the PostgreSQL error is not further addressed.
At the configuration I have tried the following to no avail:
discourse..org
host..org
www..org
What is my hostname supposed to be?
If someone goes to www..org now, the forum i am using with another forum host provider shows up.
Is that the problem?
Ideally, your hostname should be a DNS name that routes to the server where you’re trying to install Discourse. This configuration tells Discourse what URL name to respond to for requests.
If you are intending to replace your other forum provider with Discourse, then you’d need to first make sure that either the DNS has been updated to the server where you’re installing Discourse, or that you remove the existing forum and use that server to install Discourse.
Usually the server will have its own DNS record, yes. You would need to create that before installing Discourse. The installer does not know who your DNS provider is and has no standard way of doing this for you.
Right. Your host name needs to resolve to your server IP address. This is not secret information, as anyone who wants to access your server by its host name must necessarily be able to determine its ip address.
I also got a postgresql error on my last attempt to install
2020-05-27 21:27:14.782 UTC [64] FATAL: could not map anonymous shared memory: Cannot allocate memory
2020-05-27 21:27:14.782 UTC [64] HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory, swap space, or huge pages. To reduce the request size (currently 1399185408 bytes), reduce Pos tgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connect ions.
2020-05-27 21:27:14.783 UTC [64] LOG: database system is shut down