Related

Ask About Billing Cost { Droplet Destroy and Make again } Question Question
i forget my putty password, how to reset it. Question Question

Question

Error when trying to start discourse could not find expected while scanning a simple key

Posted April 22, 2018 3.2k views
DigitalOcean 1-Click Apps MarketplaceUbuntu 16.04

Below is the error I am getting. I’ve manually installed lighttpd, which removed that error and manually installed rails but I still get this. I haven’t found much out there so i hope i’m not overlooking something simple. Thanks:

Please press enter when you are read to configure discourse.

Enter the email address to use for the Discourse admin account (ex. user@example.org) noreply@mg.thetines.org
Enter the domain or subdomain pointed to this Discourse instance (ex. forum.example.org): www.thetines.org
Enter the SMTP server to use to send email (ex: smtp.example.org): smtp.mailgun.org
SMTP Port (default 587):
SMTP Username (ex. user@example.org): postmaster@mg.thetines.org
SMTP Password:
Thanks! Your Discourse instance is now being configured....this can take a few minutes…

Synchronizing state of docker.service with SysV init with /lib/systemd/systemd-sysv-install…
Executing /lib/systemd/systemd-sysv-install enable docker

(<unknown>): could not find expected ’:’ while scanning a simple key at line 63 column 1 -e LANG=en_US.UTF-8
YAML syntax error. Please check your containers/*.yml config files.
Error response from daemon: No such container: rails

Discourse has now been configured. You may now finish setting up Discourse
by creating an account at:

Add a comment
jco42
By:
jco42

Related

Ask About Billing Cost { Droplet Destroy and Make again } Question Question
i forget my putty password, how to reset it. Question Question

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.

×
5 answers
intrepita February 14, 2019

Same problem… why publish a One-Click install that hasn’t been tested properly and doesn’t work?!?

Reply Report
  • jco42 February 15, 2019

    See the link from @xinbenlv above. It is for Ubuntu 18.04.

    Reply Report
    • intrepita February 15, 2019

      I followed your link to the 30 minute install and that works fine on 18.04

      Reply Report
      • intrepita February 15, 2019

        Solved!

        Hopefully this will help anyone else who has this same issue. If you actually use a strong password it breaks the installation script. The One-Click droplet works fine as long as you avoid special characters in your password.

        The One-Click droplet also cannot be installed using https by default in the same way the 30 min install link can. Pretty sure it can be added later, I’m just not there yet.

        Reply Report
ryanpq April 23, 2018

What process did you use to install Discourse?

Reply Report
nateinaction May 7, 2018

I used the 1 click droplet setup on the $10 plan. After the droplet was created I logged in to root via SSH, entered email, domain and sftp info. Then I received the following:

Thanks!  Your Discourse instance is now being configured....this can take a few minutes...

Synchronizing state of docker.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable docker
insserv: warning: current start runlevel(s) (empty) of script `docker' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `docker' overrides LSB defaults (0 1 6).

(<unknown>): did not find expected node content while parsing a block node at line 62 column 28 -e LANG=en_US.UTF-8
YAML syntax error. Please check your containers/*.yml config files.
Error response from daemon: No such container: rails

Discourse has now been configured. You may now finish setting up Discourse
by creating an account at:
    http://159.203.77.174

Curling the IP shows not accepting connections:

curl -IL http://159.203.77.174
curl: (7) Failed to connect to 159.203.77.174 port 80: Connection refused
Reply Report
joezela August 24, 2018

I too am having the same issue as described. Any solutions?

Reply Report
xinbenlv February 8, 2019

Got same problem

Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help