DigitalOcean Kubernetes: new control plane is faster and free, enable HA for 99.95% uptime SLA

Question

err_connection_timed_out (discourse)

I thought my one-click discourse download was okay. but when I try to connect at my domain, i found this error in my browser -> err_connection_timed_out

couldn’t see discourse’s congratulation screen

reopening console, there was some texts with “no mail”…

**can you help me? I wanna know about my droplet’s problem. **

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Sign up now

Bobby Iliev • May 11, 2020

Hi there @mapal,

What you need to do after deploying the Discourse Droplet is to SSH to the Droplet and add the following details:

  • Email Address for the Discourse Admin Account
  • The hostname (domain or subdomain) you will use for Discourse
  • Details for the SMTP server your Discourse install will use to send email
  • Email Address to use if you wish to set up a LetsEncrypt SSL certificate

Once you’ve done that then you will be able to visit your domain name and see your Discourse installation.

If you have already done this, I would recommend checking if the Apache Docker container is running, you can do that by connecting to your server via SSH, and running this command:

  1. sudo docker ps -a

If it is not running, I would recommend trying to start it and checking the logs.

To try and start the container run:

  1. sudo docker start container_id_here

And then to check the logs run:

  1. sudo docker logs container_id_here

Hope that this helps! Regards, Bobby

Try DigitalOcean for free

Click below to sign up and get $100 of credit to try our products over 60 days!

Sign up