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


  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
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

Cloudron Forum

Apps | Demo | Docs | Install

Mastodon Terminal not starting

Scheduled Pinned Locked Moved Solved Mastodon
mastodon
16 Posts 3 Posters 519 Views
    • 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 girish
    #1

    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
    0
  • girishG Do not disturb
    girishG Do not disturb
    girish Staff
    wrote on last edited by
    #2

    @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
    0
  • S Offline
    S Offline
    smilebasti
    replied to girish on last edited by
    #3

    @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
    0
  • girishG Do not disturb
    girishG Do not disturb
    girish Staff
    wrote on last edited by
    #4

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

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

    @girish This is also with Nextcloud (all other)

    1 Reply Last reply
    0
  • girishG Do not disturb
    girishG Do not disturb
    girish Staff
    wrote on last edited by girish
    #6

    @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
    0
  • 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 Do not disturb
    girishG Do not disturb
    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 Do not disturb
    girishG Do not disturb
    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 Do not disturb
    girishG Do not disturb
    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
  • A Offline
    A Offline
    alwynispat
    replied to girish 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
  • girishG Do not disturb
    girishG Do not disturb
    girish Staff
    replied to alwynispat 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
  • A Offline
    A Offline
    alwynispat
    replied to girish 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
  • girishG Do not disturb
    girishG Do not disturb
    girish Staff
    replied to alwynispat 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

  • Login

  • Don't have an account? Register

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

  • Don't have an account? Register

  • Login or register to search.