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


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Discourse
  3. Starting error

Starting error

Scheduled Pinned Locked Moved Solved Discourse
10 Posts 4 Posters 1.4k Views 4 Watching
  • 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 Online
      M Online
      mononym
      wrote on last edited by
      #1

      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"

      girishG 1 Reply Last reply
      0
      • subvenS Offline
        subvenS Offline
        subven
        wrote on last edited by
        #2

        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
        0
        • N Offline
          N Offline
          ntnsndr
          wrote on last edited by
          #3

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

          1 Reply Last reply
          0
          • subvenS subven

            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 Online
            M Online
            mononym
            wrote on last edited by
            #4

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

            1 Reply Last reply
            0
            • M mononym

              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"

              girishG Offline
              girishG Offline
              girish
              Staff
              wrote on last edited by
              #5

              @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
              0
              • girishG girish

                @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 Offline
                N Offline
                ntnsndr
                wrote on last edited by
                #6

                @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."

                girishG 2 Replies Last reply
                0
                • N ntnsndr

                  @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."

                  girishG Offline
                  girishG Offline
                  girish
                  Staff
                  wrote on last edited by
                  #7

                  @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
                  0
                  • N ntnsndr

                    @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."

                    girishG Offline
                    girishG Offline
                    girish
                    Staff
                    wrote on last edited by
                    #8

                    @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
                    0
                    • girishG girish

                      @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 Offline
                      N Offline
                      ntnsndr
                      wrote on last edited by
                      #9

                      @girish Ah yes—working now. Thank you!

                      1 Reply Last reply
                      0
                      • girishG girish marked this topic as a question on
                      • girishG girish has marked this topic as solved on
                      • girishG girish

                        @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

                        M Online
                        M Online
                        mononym
                        wrote on last edited by
                        #10

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

                        1 Reply Last reply
                        0
                        Reply
                        • Reply as topic
                        Log in to reply
                        • Oldest to Newest
                        • Newest to Oldest
                        • Most Votes


                          • Login

                          • Don't have an account? Register

                          • Login or register to search.
                          • First post
                            Last post
                          0
                          • Categories
                          • Recent
                          • Tags
                          • Popular
                          • Bookmarks
                          • Search