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. Mastodon
  3. Mastodon Terminal not starting

Mastodon Terminal not starting

Scheduled Pinned Locked Moved Solved Mastodon
mastodon
16 Posts 3 Posters 2.6k Views 3 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.
  • S Offline
    S Offline
    smilebasti
    wrote on last edited by
    #7

    @girish Ok the 2. thing is also not working.

    1. your command worked fine.
      Anmerkung 2020-04-06 214445.png
    1 Reply Last reply
    0
    • girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #8

      Can you tail -f /home/yellowtent/platformdata/logs/box.log and see if there is some crash/error when you open the terminal view? Any errors in the browser console?

      1 Reply Last reply
      0
      • S Offline
        S Offline
        smilebasti
        wrote on last edited by girish
        #9

        Thats the Error i get when i am starting the terminal

        <I deleted the image because it showed the domain name - girish>

        1 Reply Last reply
        0
        • S Offline
          S Offline
          smilebasti
          wrote on last edited by
          #10

          This is the chrome console error

          90ffabd6-0d6e-4032-8fd0-95b09922df10-image.png
          website erased

          1 Reply Last reply
          0
          • girishG Offline
            girishG Offline
            girish
            Staff
            wrote on last edited by
            #11

            @smilebasti Indeed, there is a crash in cloudron in quite a strange place. That function should always be defined. Can you send us a mail to support@cloudron.io after enabling ssh access (Support -> enable remote support)?

            1 Reply Last reply
            0
            • girishG Offline
              girishG Offline
              girish
              Staff
              wrote on last edited by
              #12

              OK, we found that the issue was related to having a reverse proxy in front of Cloudron. This reverse proxy was not configured properly to forward web sockets.

              For nginx, we need something like this:

              map $http_upgrade $connection_upgrade {
                  default upgrade;
                  '' close;
              }
              
              server {
              
                  ....
              
                  proxy_set_header Upgrade $http_upgrade;
                  proxy_set_header Connection $connection_upgrade;
                  ...
              
              }
              

              For apache, we need something like this:

              
                RewriteEngine on
              
                RewriteCond ${HTTP:Upgrade} websocket [NC]
              
                RewriteCond ${HTTP:Connection} upgrade [NC]
              
                RewriteRule .* "wss:/192.168.20.12/$1" [P,L]
              

              For the moment, one can just use SSH to open a web terminal like this:

              docker ps -f label=fqdn=app.domain.com
              
              docker exec -ti <containerid_from_above> /bin/bash
              
              A 1 Reply Last reply
              1
              • girishG girish

                OK, we found that the issue was related to having a reverse proxy in front of Cloudron. This reverse proxy was not configured properly to forward web sockets.

                For nginx, we need something like this:

                map $http_upgrade $connection_upgrade {
                    default upgrade;
                    '' close;
                }
                
                server {
                
                    ....
                
                    proxy_set_header Upgrade $http_upgrade;
                    proxy_set_header Connection $connection_upgrade;
                    ...
                
                }
                

                For apache, we need something like this:

                
                  RewriteEngine on
                
                  RewriteCond ${HTTP:Upgrade} websocket [NC]
                
                  RewriteCond ${HTTP:Connection} upgrade [NC]
                
                  RewriteRule .* "wss:/192.168.20.12/$1" [P,L]
                

                For the moment, one can just use SSH to open a web terminal like this:

                docker ps -f label=fqdn=app.domain.com
                
                docker exec -ti <containerid_from_above> /bin/bash
                
                A Offline
                A Offline
                alwynispat
                wrote on last edited by
                #13

                @girish I have similar issues, I’m using the nginx proxy manager. Everything works but the app terminal. Already tried your config for ngix but didn’t work.

                Find me at Mastodon

                girishG 1 Reply Last reply
                0
                • A alwynispat

                  @girish I have similar issues, I’m using the nginx proxy manager. Everything works but the app terminal. Already tried your config for ngix but didn’t work.

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

                  @alwynispat Could be because websocket is not getting forwarded properly via the proxy manager. Does it work without the proxy manager?

                  A 1 Reply Last reply
                  0
                  • girishG girish

                    @alwynispat Could be because websocket is not getting forwarded properly via the proxy manager. Does it work without the proxy manager?

                    A Offline
                    A Offline
                    alwynispat
                    wrote on last edited by
                    #15

                    @girish found the culprit, NPM was not forwarding the web socket properly. Fixed that and the terminal works now.

                    Find me at Mastodon

                    girishG 1 Reply Last reply
                    1
                    • A alwynispat

                      @girish found the culprit, NPM was not forwarding the web socket properly. Fixed that and the terminal works now.

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

                      @alwynispat do you mean nginx? How is NPM involved here?

                      edit: oh, maybe you mean your nginx proxy manager?

                      1 Reply Last reply
                      2
                      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