Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved Starting error

    Discourse
    4
    10
    178
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mononym last edited by

      Hello. After the latest update my discourse app is stuck in the starting process because of this error:

      Sep 30 21:52:29 ==> Creating directories
      Sep 30 21:52:29 ==> Configuring discourse
      Sep 30 21:52:29 ==> Creating symlinks for built-in plugins
      Sep 30 21:52:29 ==> Enabling recvmail integration
      Sep 30 21:52:29 Error: Parsing expression: Lexer error: could not match text starting at 1:31 failing at 1:34.
      Sep 30 21:52:29 unmatched text: "for"

      girish 1 Reply Last reply Reply Quote 0
      • subven
        subven last edited by

        Seems like an error in the YAML syntax. Take a look at your env file and make sure that everything is valid (especially at line 31 to 34).

        M 1 Reply Last reply Reply Quote 0
        • N
          ntnsndr last edited by

          I am having this issue as well. What file is the error in? I can't tell.

          1 Reply Last reply Reply Quote 0
          • M
            mononym @subven last edited by

            @subven I restored to the version before the upgrade for now.

            1 Reply Last reply Reply Quote 0
            • girish
              girish Staff @mononym last edited by

              @mononym said in Starting error:

              Sep 30 21:52:29 ==> Enabling recvmail integration

              Maybe there is a bug when recvmail integration is getting enabled. Let me test.

              N 1 Reply Last reply Reply Quote 0
              • N
                ntnsndr @girish last edited by

                @girish And findings? And if I need to downgrade, how do I do that?

                I just saw there was an "update available," and I updated, but it still is "not responding."

                girish 2 Replies Last reply Reply Quote 0
                • girish
                  girish Staff @ntnsndr last edited by

                  @ntnsndr whoops, forgot to update here. I already pushed an update with a fix. Package v1.7.13-1 fixes it, can you update and please let me know?

                  1 Reply Last reply Reply Quote 0
                  • girish
                    girish Staff @ntnsndr last edited by

                    @ntnsndr said in Starting error:

                    I just saw there was an "update available," and I updated, but it still is "not responding."

                    Check for update again and you should see a new package. I am guessing it previously updated to 1.17.3 and not 1.17.3-1

                    N M 2 Replies Last reply Reply Quote 0
                    • N
                      ntnsndr @girish last edited by

                      @girish Ah yes—working now. Thank you!

                      1 Reply Last reply Reply Quote 0
                      • Topic has been marked as a question  girish girish 
                      • Topic has been marked as solved  girish girish 
                      • M
                        mononym @girish last edited by

                        New update was 1.17.3-1 and worked perfectly. Thx !

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Powered by NodeBB