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. Empty white page after installing and trying twice

Empty white page after installing and trying twice

Scheduled Pinned Locked Moved Mastodon
18 Posts 3 Posters 2.3k 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.
    • girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #9

      Reading this again, it's not clear to me: is Cloudflare proxying enabled or not? If you have it enabled, have you tried without Cloudflare proxying?

      M 1 Reply Last reply
      0
      • nebulonN Offline
        nebulonN Offline
        nebulon
        Staff
        wrote on last edited by
        #10

        Is it possible that your server runs out of memory? Or the mastodon app crashes out of memory?

        1 Reply Last reply
        0
        • girishG girish

          Reading this again, it's not clear to me: is Cloudflare proxying enabled or not? If you have it enabled, have you tried without Cloudflare proxying?

          M Offline
          M Offline
          masto77
          wrote on last edited by masto77
          #11

          @girish

          Thanks it’s already working I got your point cause with proxying ttl is auto.

          I wasn’t trying it without proxy.

          but hanged with not being able to image posts using official mastodon iOS app 61F2628B-9876-43A1-9491-5CC4AB3E5B2D.jpeg

          The web works

          @nebulon

          No such reports I have extended memory up to 3GB and the server has 4GB

          1 Reply Last reply
          0
          • nebulonN Offline
            nebulonN Offline
            nebulon
            Staff
            wrote on last edited by
            #12

            Maybe there is some language barrier, but it might help to give more detailed background information so we can help you.

            I assume the 502 error is now something different to your initial issue. Do you see any errors in the app logs or browser console or something?

            M 1 Reply Last reply
            0
            • nebulonN nebulon

              Maybe there is some language barrier, but it might help to give more detailed background information so we can help you.

              I assume the 502 error is now something different to your initial issue. Do you see any errors in the app logs or browser console or something?

              M Offline
              M Offline
              masto77
              wrote on last edited by masto77
              #13

              @nebulon

              I just googled this issue I’m not sure if it is specific to uploading image through iOS mastodon app

              These google references I found says nginx buffer needs to be increased I have no idea how to do it while at cloudron

              This happens only on official mastodon app to me, I tried using metatext app it works fine

              1 Reply Last reply
              0
              • nebulonN Offline
                nebulonN Offline
                nebulon
                Staff
                wrote on last edited by
                #14

                This further indicates that something is rather on the client side or how that specific client of yours interacts with the server. Do you see any errors in the server side app logs which might give any indication? Without more detailed information from your side, this is mostly guesswork on our end.

                M 2 Replies Last reply
                0
                • nebulonN nebulon

                  This further indicates that something is rather on the client side or how that specific client of yours interacts with the server. Do you see any errors in the server side app logs which might give any indication? Without more detailed information from your side, this is mostly guesswork on our end.

                  M Offline
                  M Offline
                  masto77
                  wrote on last edited by
                  #15
                  This post is deleted!
                  1 Reply Last reply
                  0
                  • nebulonN nebulon

                    This further indicates that something is rather on the client side or how that specific client of yours interacts with the server. Do you see any errors in the server side app logs which might give any indication? Without more detailed information from your side, this is mostly guesswork on our end.

                    M Offline
                    M Offline
                    masto77
                    wrote on last edited by masto77
                    #16

                    @nebulon

                    I found this from google no idea how to do it?
                    and this is marked as a solution

                    https://discourse.joinmastodon.org/t/502-bad-gateway-connection-refused-while-connecting-to-upstream/3396

                    “”
                    It seems you forgot to run the bundle exec rails assets:precompile step or it failed.””

                    nebulonN 1 Reply Last reply
                    0
                    • M masto77

                      @nebulon

                      I found this from google no idea how to do it?
                      and this is marked as a solution

                      https://discourse.joinmastodon.org/t/502-bad-gateway-connection-refused-while-connecting-to-upstream/3396

                      “”
                      It seems you forgot to run the bundle exec rails assets:precompile step or it failed.””

                      nebulonN Offline
                      nebulonN Offline
                      nebulon
                      Staff
                      wrote on last edited by
                      #17

                      @masto77 actually we do run that step in the image building https://git.cloudron.io/cloudron/mastodon-app/-/blob/master/Dockerfile#L44

                      We also have a lot of mastodon installations amongst our users who don't seem to face that issue, which makes me even more think, that this is something related to your specific mastodon client.

                      I do not have any iOS devices to test this with, but maybe other can comment if they face the same or a similar issue?

                      Have you looked at the server side app logs yet? You can find the logviewer as described at https://docs.cloudron.io/apps/#log-viewer

                      M 1 Reply Last reply
                      0
                      • nebulonN nebulon

                        @masto77 actually we do run that step in the image building https://git.cloudron.io/cloudron/mastodon-app/-/blob/master/Dockerfile#L44

                        We also have a lot of mastodon installations amongst our users who don't seem to face that issue, which makes me even more think, that this is something related to your specific mastodon client.

                        I do not have any iOS devices to test this with, but maybe other can comment if they face the same or a similar issue?

                        Have you looked at the server side app logs yet? You can find the logviewer as described at https://docs.cloudron.io/apps/#log-viewer

                        M Offline
                        M Offline
                        masto77
                        wrote on last edited by
                        #18

                        @nebulon

                        Thanks!

                        I found this too may be it’s related which states to increase the buffer I have no idea where to find this or how to do it ?

                        “
                        A possible fix for this is to modify the nginx conf to increase the proxy buffer. The following worked for me:

                        proxy_buffers 4 16k;
                        proxy_buffer_size 16k;
                        proxy_busy_buffers_size 32k;
                        

                        “

                        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