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

    Mastodon
    mastodon
    3
    16
    483
    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.
    • S
      smilebasti last edited by girish

      Hi, i just installed Mastodon successfully. After i created an user on the running server i tried to add the user the admin functions through the Terminal.

      The Terminal says: 'Connecting...' and 'If you resize the Window press cntrl+D....'.

      After that the screen switches to full black terminal. I have also tried recovery mode but nothing different. I also had a look in the logs but i found nothing..

      Thanks ahead for your help 🙂

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

        @smilebasti Usually, it will keep saying 'Connecting...' only when the app is not running. Maybe the app was just starting up? Does it say 'Running' in the apps view?

        S 1 Reply Last reply Reply Quote 0
        • S
          smilebasti @girish last edited by

          @girish Hi thanks for the fast reply.

          Yes the App in running mode.
          It is saying 'connecting...' only for a second or two with the screen size and then is all going black (terminal)

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

            @smilebasti Do you see this with all apps or just mastodon?

            1 Reply Last reply Reply Quote 0
            • S
              smilebasti last edited by

              @girish This is also with Nextcloud (all other)

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

                @smilebasti Could be one of two reasons:

                1. docker is not working for whatever reason. Can you check if you can do something like docker exec -ti mysql /bin/bash on the server ? Does it give you a shell? If not, this is a docker issue which we can debug further based on the error message.

                2. Maybe some browser issue. But this seems a bit unlikely. Can you try another browser just in case some extension is causing some problem?

                1 Reply Last reply Reply Quote 0
                • S
                  smilebasti last edited by

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

                  1. your command worked fine.
                    Anmerkung 2020-04-06 214445.png
                  1 Reply Last reply Reply Quote 0
                  • girish
                    girish Staff last edited by

                    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 Reply Quote 0
                    • S
                      smilebasti last edited by girish

                      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 Reply Quote 0
                      • S
                        smilebasti last edited by

                        This is the chrome console error

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

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

                          @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 Reply Quote 0
                          • girish
                            girish Staff last edited by

                            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 Reply Quote 1
                            • A
                              alwynispat @girish last edited by

                              @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

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

                                @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 Reply Quote 0
                                • A
                                  alwynispat @girish last edited by

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

                                  Find me at Mastodon

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

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

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

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