A user papertrail-ai encountered a connection timeout while self-hosting Discourse on AWS, despite following setup instructions. schleifer suggested checking the security group, which was corrected to allow all traffic. The issue persisted, leading to the discovery that Docker was not properly installed due to insufficient instance memory. After resolving the memory issue, the container started successfully, and the site became accessible. Stephen and schleifer provided guidance throughout the troubleshooting process. The user confirmed the site was working the next morning papertrail-ai.
I have recently opted to do a self-host of discourse on aws.
I followed all the instructions on the github page. I receive a connection timeout error. The installation works fine. The DNS A record is set up correctly and my host has confirmed that it works.
On aws my instance is a Ubuntu Server 18.04 LTS (HVM), SSD Volume Type with 2GB and 1vCPU.
Every time I access the page I receive a connection timeout error.
Thanks so much. You guys lead me in the right direction.
The security group was wrong. Curl localhost was also not connecting. After which I released that the docker installation did not work correctly. The default memory size for my instance on aws was to small and as a result docker was not being installed correctly.
Curl localhost now shows
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx/1.17.4</center>
</body>
</html>
Docker process list shows the following:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
646fd4d2 local_discourse/app "/sbin/boot" 6 minutes ago Up 6 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp app