Hello world, I’m trying to get my first Discourse forum running, and I need some help… I recently set up a 1G instance on Lightsail and followed these install instructions: github.com/discourse/discourse/blob/master/docs/INSTALL-cloud.md I set up an account with Mailgun and added that info in du…

What you essentially need is the public IP address of the lightsail vps and then choose to manage your dns wherever you like. If you’d like to manage those through amazon, you can use route53 and it will give you nameservers that you can update in your domain’s settings at registrar (i.e. google) O…

I’m not very sure about Lightsail but in case of AWS, when a domain is not pointing to their IP properly, 90% of the time, security groups are to be blamed. Can you try opening the necessary ports (80,443,587 etc) in the AWS security group for your vps?

[imagen] itsbhanusharma: 587 Thanks for your reply. I opened up these ports (443 and 587 were closed) and rebuilt the app, but still no luck. I suspect it’s something on the DNS side, but I’m not sure what else to change. I don’t currently have becomeachiron.com set up, just the subdomain. Se…

How did You set up just the subdomain ?

We have recently moved to discourse and Amazon lightsail (so I have little expertize) I have exactly that config and I could install discourse with no problem at all. I have installed the official Debian AMI from amazon first. Then configured the hostname to my domain ( discourse.becomeachiron.co…

[imagen] PensiveCyborg: set the subdomain discourse.becomeachiron.com to the public IP of my instance. It doesn’t look like you’ve set up the domain: pfaffman@balloon:~$ dig +short discourse.becomeachiron.com @NS-1041.AWSDNS-02.ORG returns nothing. This link will test for propagation, but…

There is no record because it seems he is not using Amazon DNS, he says it is working with google dns. So he has to configure it in google. discourse.becomeachiron.com resolves right now to 99.79.192.57

Thank you all for your replies. Ideally, I would host Discourse on the domain - not the subdomain, but every set of instructions I can find insists on a subdomain. Is this a necessity?

I’m also hacking away at all this right now :slight_smile:

I have read it is possible to use the plain domain with no www or discourse subdomain. But it is not the default config and it seems it is not so easy, perhaps it is better to try first the default way, as you did. I insist: Have you configures a static ip address for your lightsail instance? By …

Here’s where I am now: in Lightsail created a static IP and attached it to my instance (thanks, fernando) created a DNS zone in Google Domains updated the name servers to those from the DNS zone created a subdomain and pointed it to the static IP Discourse is set up properly - I can access it…

Instalación de Discourse en Lightsail

Soporte

itsbhanusharma (Bhanu Sharma) 27 Septiembre, 2019 16:41 19

Parece que estás usando AWS Route53 para gestionar tu DNS.

Para el dominio principal, sigue estos pasos:

Crea un registro Alias (A) para el dominio principal (indicado por @) apuntando a la IP de tu Lightsail.
Edita tu archivo app.yml para usar el dominio principal.
Reconstruye.
Ejecuta un remapeo de Discourse.

Eso es todo lo que tienes que hacer.

Tema		Respuestas	Vistas
Install Discourse on Amazon Web Services (AWS) with Lightsail, SES, and Route 53 Sysadmins how-to , install	4	2984	7 Agosto 2024
Discourse deploy on lightsail: "connection refused" Self-hosting	12	1494	22 Agosto 2022
Misconfigured DNS preventing discourse-setup completion Self-hosting	13	1834	21 Marzo 2020
WARNING: This server does not appear to be accessible at Self-hosting	11	2744	19 Marzo 2020
WARNING: Port 443 of computer does not appear to be accessible using hostname: <mydomain>.com Self-hosting	11	1661	3 Septiembre 2024

Instalación de Discourse en Lightsail

Temas relacionados