My site is down after I installed a plugin

I went to install a plugin and it started to give this following error in the part where I do the ./launcher rebuild app

i use ./discourse-doctor but dont solve

FAILED
--------------------
Pups::ExecError: if [ -z "$LETSENCRYPT_ACCOUNT_EMAIL" ]; then echo "LETSENCRYPT_ACCOUNT_EMAIL ENV variable is required and has not been set."; exit 1; fi failed with return #<Process::Status: pid 2296 exit 1>
Location of failure: /usr/local/lib/ruby/gems/2.7.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn'
exec failed with the params {"cmd"=>["if [ -z \"$LETSENCRYPT_ACCOUNT_EMAIL\" ]; then echo \"LETSENCRYPT_ACCOUNT_EMAIL ENV variable is required and has not been set.\"; exit 1; fi", "/bin/bash -c \"if [[ ! \\\"$LETSENCRYPT_ACCOUNT_EMAIL\\\" =~ ([^@]+)@([^\\.]+) ]]; then echo \\\"LETSENCRYPT_ACCOUNT_EMAIL is not a valid email address\\\"; exit 1; fi\""]}
bootstrap failed with exit code 1
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.
324b6cc40db917188cb3d87640ff1a1c23142c551b71bc55b0f33ccd88e88af7

now show this

root@ForumPandex:/var/discourse# ./launcher rebuild app
x86_64 arch detected.
Ensuring launcher is up to date
Fetching origin
Launcher is up-to-date
(<unknown>): could not find expected ':' while scanning a simple key at line 67 column 3 -e LANG=en_US.UTF-8
YAML syntax error. Please check your containers/*.yml config files.

It looks like you may have a typo in your app.yml.

The first error message would point to your let’sencrypt email, but the second is suggesting you have a missing colon. Can you see anything obvious you may have accidentally addded/deleted while editing to add the plugin?

3 Likes
ger.git
          - git clone https://github.com/discourse/discourse-spoiler-alert.git
          - git clone https://github.com/discourse/discourse-yearly-review.git
          - git clone https://github.com/mondiscourse/discourse-formatting-toolbar.git
          - git clone https://github.com/techapj/discourse-custom-topic-button.git
          - git clone https://github.com/discourse/discourse-chat.git
          - git clone https://github.com/discourse/discourse-adplugin.git
          - git clone https://github.com/communiteq/discourse-delete-unreplied-topics
          - git clone https://github.com/discourse/discourse-animated-avatars
          - git clone https://github.com/gnunicorn/discourse-plugin-replygif
          - git clone https://github.com/discourse/discourse-gamification
          - git clone https://github.com/discourse/discourse-reactions.git
          - git clone https://github.com/discourse/docker_manager.git
          - git clone https://github.com/discourse/discourse-spoiler-alert.git
          - git clone https://github.com/discourse/discourse-yearly-review.git
          - git clone https://github.com/mondiscourse/discourse-formatting-toolbar.git
          - git clone https://github.com/techapj/discourse-custom-topic-button.git
          - git clone https://github.com/discourse/discourse-chat.git
          - git clone https://github.com/discourse/discourse-adplugin.git
          - git clone https://github.com/communiteq/discourse-delete-unrepl>
          - git clone https://github.com/discourse/discourse-animated-avata>
          - git clone https://github.com/gnunicorn/discourse-plugin-replygif
          - git clone https://github.com/discourse/discourse-gamification
          - git clone https://github.com/discourse/discourse-reactions.git
          - git clone https://github.com/discourse/docker_manager.git
          - git clone https://github.com/discourse/discourse-spoiler-alert.>

## Any custom commands to run after building
run:
  - exec: echo "Beginning of custom commands"
  ## If you want to set the 'From' email address for your first registration, uncomment and change:
  ## After getting the first signup email, re-comment the line. It only needs to run once.
  #- exec: rails r "SiteSetting.notification_email='info@unconfigured.discourse.org'"
  - exec: echo "End of custom commands"

@JammyDodger is right about the typo. I see at least three:

4 Likes

That, and all your plugins are in there twice.

4 Likes

actually, when I created it I copied it wrong, is there any way to copy everything at once from the prompt?

Guys, I don’t even know what I did anymore, I just know that the site is still down, how can I know what I did wrong?

agora o discourse doctor says it

======================================== ERROR ========================================
                                    UNEXPECTED ERROR

Timeout to open TCP connection to email-smtp.us-east-1.amazonaws.com:25 (exceeds 5 seconds)

====================================== SOLUTION =======================================
This is not a common error. No recommended solution exists!

Please report the exact error message above to https://meta.discourse.org/
(And a solution, if you find one!)
=======================================================================================
Replacing: SMTP_PASSWORD
Replacing: LETSENCRYPT_ACCOUNT_EMAIL
Replacing: DEVELOPER_EMAILS
Replacing: DISCOURSE_DB_PASSWORD
Replacing: Sending mail to

==================== DONE! ====================
Would you like to serve a publicly available version of this file? (Y/n)```

You should be able to restart the old container with

./launcher start app

Then you need to straighten out your yml.

Oh, discourse doctor should have restatred the old container.

still bad
i’m desperate

The easiest thing to do might be to rename your app.yml to broken.yml, then run ./discourse-setup. That will create a new app.yml, but don’t delete your existing data.

8 Likes

i try it and now show it

Checking your domain name . . .
WARNING: Port 443 of computer does not appear to be accessible using hostname:  www.dexforum.com.br].
WARNING: Connection to http://www.dexforum.com.br] (port 80) also fails.

This suggests that www.dexforum.com.br] resolves to some IP address that does not reach this
machine where you are installing discourse.

The first thing to do is confirm that www.dexforum.com.br] resolves to the IP address of this server.
You usually do this at the same place you purchased the domain.

If you are sure that the IP address resolves correctly, it could be a firewall issue.
A web search for "open ports YOUR CLOUD SERVICE" might help.

This tool is designed only for the most standard installations. If you cannot resolve
the issue above, you will need to edit containers/app.yml yourself and then type

./launcher rebuild app

well, now I managed to do the discourse setup, but when rebuilding, this appears

(<unknown>): mapping values are not allowed in this context at line 98 column 12 -e LANG=en_US.UTF-8
YAML syntax error. Please check your containers/*.yml config files.

Did you edit the app.yml by hand, to, say, ,add a plugin?

Yep, that’s where the after_code hooks for plugins are.

@Danielabc if you want us to help you then you need to provide feedback on the steps we provide, ideally without coloring outside the lines. Installing plugins will come after we help you rebuild a working instance.

1 Like

I managed to solve it, but do you know what I found strange, was that all the .yml that Discourse created had the wrong formatting? Is this possible? I didn’t do anything, I didn’t even edit it, but the .yml was always created with the wrong formatting.

I used https://www.yamllint.com/ which I found on google, it helped me with the right formatting, and finally I was able to do a rebuild

but I never took into account that the .yml file could be being badly formatted by the system, this left me confused

1 Like

Discourse-setup hasn’t been changed in about six months.

The only way I can think that it could produce poorly-formed yaml is through the responses to the prompts.

Did you copy and paste the responses, or enter them by hand?

2 Likes

That bracket should not be there.

I just generated a command to create a new .yml, but I didn’t change anything in the new .yml, I just did the rebuild which gave an error due to bad formatting