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. server upgrade and App Mastodon

server upgrade and App Mastodon

Scheduled Pinned Locked Moved Mastodon
17 Posts 5 Posters 2.2k Views 5 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.
  • jdaviescoatesJ Offline
    jdaviescoatesJ Offline
    jdaviescoates
    wrote on last edited by jdaviescoates
    #3

    Probably what you want to know is how to allocate more resources to the app.

    See https://docs.cloudron.io/apps/#memory-limit

    I use Cloudron with Gandi & Hetzner

    1 Reply Last reply
    0
    • BrutalBirdieB BrutalBirdie

      @redegelde
      Sorry but your question is very broad, I guess the answer is no you don't have to do anything with the app code?
      But since your question is broad and confusing I would advise asking it again with more detail and if English is the problem feel free to write in your native language.

      R Offline
      R Offline
      redegelde
      wrote on last edited by
      #4

      @BrutalBirdie sorry for that
      i mean i started the Mastodon app on vps server with 20GB storage
      Now on 40Gb vps and i did nothing with the app.
      f1506523-d48c-4523-a5c6-47f2e03ebd41-image.png

      does is expand automatically, i know that with gpart you can make disk space available for using.

      nebulonN 1 Reply Last reply
      0
      • R Offline
        R Offline
        redegelde
        wrote on last edited by
        #5

        reason i ask, experience this error lines in my log.

        Nov 09 11:30:00 box:janitor Cleaning up expired tokens
        Nov 09 11:30:00 box:disks checkDiskSpace: checking disk space
        Nov 09 11:30:00 box:janitor Cleaned up 0 expired tokens
        Nov 09 11:30:00 box:apphealthmonitor app health: 1 alive / 0 dead.
        Nov 09 11:30:00 box:disks checkDiskSpace: disk space checked. out of space: no
        Nov 09 11:30:10 box:apphealthmonitor app health: 1 alive / 0 dead.
        Nov 09 11:30:20 box:apphealthmonitor app health: 1 alive / 0 dead.
        Nov 09 11:30:30 box:apphealthmonitor app health: 1 alive / 0 dead.
        Nov 09 11:30:40 box:apphealthmonitor app health: 1 alive / 0 dead.
        Nov 09 11:30:50 box:apphealthmonitor app health: 1 alive / 0 dead.
        Nov 09 11:31:00 box:apphealthmonitor app health: 1 alive / 0 dead.
        Nov 09 11:31:10 box:apphealthmonitor app health: 1 alive / 0 dead.
        GET /well-known-handler/webfinger?resource=acct:redegelde@mastodon.education 404 Not Found No custom well-known config 0.811 ms - 71
        GET /well-known-handler/webfinger?resource=acct:redegelde@mastodon.education 404 Not Found No custom well-known config 0.857 ms - 71

        And from user side this
        aab5a380-17a6-4bf2-a5c9-1ab8a9de6087-image.png

        nebulonN 1 Reply Last reply
        0
        • R redegelde

          @BrutalBirdie sorry for that
          i mean i started the Mastodon app on vps server with 20GB storage
          Now on 40Gb vps and i did nothing with the app.
          f1506523-d48c-4523-a5c6-47f2e03ebd41-image.png

          does is expand automatically, i know that with gpart you can make disk space available for using.

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

          @redegelde it looks like the filesystem was already expanded to the new disk size, since it shows 42Gb there for sda2. Depending on your server provider this may be done by their reboot scripts. The app itself will have access to the whole available free disk space. In fact we currently do not have a way in Cloudron to limit disk usage by app even.

          1 Reply Last reply
          0
          • R redegelde

            reason i ask, experience this error lines in my log.

            Nov 09 11:30:00 box:janitor Cleaning up expired tokens
            Nov 09 11:30:00 box:disks checkDiskSpace: checking disk space
            Nov 09 11:30:00 box:janitor Cleaned up 0 expired tokens
            Nov 09 11:30:00 box:apphealthmonitor app health: 1 alive / 0 dead.
            Nov 09 11:30:00 box:disks checkDiskSpace: disk space checked. out of space: no
            Nov 09 11:30:10 box:apphealthmonitor app health: 1 alive / 0 dead.
            Nov 09 11:30:20 box:apphealthmonitor app health: 1 alive / 0 dead.
            Nov 09 11:30:30 box:apphealthmonitor app health: 1 alive / 0 dead.
            Nov 09 11:30:40 box:apphealthmonitor app health: 1 alive / 0 dead.
            Nov 09 11:30:50 box:apphealthmonitor app health: 1 alive / 0 dead.
            Nov 09 11:31:00 box:apphealthmonitor app health: 1 alive / 0 dead.
            Nov 09 11:31:10 box:apphealthmonitor app health: 1 alive / 0 dead.
            GET /well-known-handler/webfinger?resource=acct:redegelde@mastodon.education 404 Not Found No custom well-known config 0.811 ms - 71
            GET /well-known-handler/webfinger?resource=acct:redegelde@mastodon.education 404 Not Found No custom well-known config 0.857 ms - 71

            And from user side this
            aab5a380-17a6-4bf2-a5c9-1ab8a9de6087-image.png

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

            @redegelde not exactly sure about the /well-known-handler/ path but just to be sure, have you seen https://docs.cloudron.io/domains/#mastodon-server-location ?

            R 1 Reply Last reply
            0
            • nebulonN nebulon

              @redegelde not exactly sure about the /well-known-handler/ path but just to be sure, have you seen https://docs.cloudron.io/domains/#mastodon-server-location ?

              R Offline
              R Offline
              redegelde
              wrote on last edited by redegelde
              #8

              @nebulon i have set the bare domain on mastodon.education and it works until yesterday when this problems occurs.

              79c2aa16-5a94-4faa-a00c-b8b114f3fd9c-image.png

              nebulonN 1 Reply Last reply
              0
              • R redegelde

                @nebulon i have set the bare domain on mastodon.education and it works until yesterday when this problems occurs.

                79c2aa16-5a94-4faa-a00c-b8b114f3fd9c-image.png

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

                @redegelde it at seems fine actually if you are running the app on that domain and the DNS A record resolves fine to your server's IP. Do you have any issues besides those log lines which I don't think are an actual issue.

                R 2 Replies Last reply
                0
                • nebulonN nebulon

                  @redegelde it at seems fine actually if you are running the app on that domain and the DNS A record resolves fine to your server's IP. Do you have any issues besides those log lines which I don't think are an actual issue.

                  R Offline
                  R Offline
                  redegelde
                  wrote on last edited by
                  #10

                  @nebulon yes, yesterday did complete server and app restart and still got this error lines
                  290abbb1-39ea-4b23-b28e-377aa45fc0ff-image.png

                  1 Reply Last reply
                  0
                  • nebulonN nebulon

                    @redegelde it at seems fine actually if you are running the app on that domain and the DNS A record resolves fine to your server's IP. Do you have any issues besides those log lines which I don't think are an actual issue.

                    R Offline
                    R Offline
                    redegelde
                    wrote on last edited by
                    #11

                    @nebulon Wow, after my post got this,
                    f570f6ba-f876-4728-9036-dee639e6fa89-image.png

                    girishG 1 Reply Last reply
                    0
                    • R redegelde

                      @nebulon Wow, after my post got this,
                      f570f6ba-f876-4728-9036-dee639e6fa89-image.png

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

                      @redegelde I replied in another post but look into /var/log/nginx/error.log as to who is the originator of these requests. This is just a misconfigured client. The logs by itself does not indicate an issue. It is just saying a request was made that Cloudron does not handle (and rightly so, Cloudron is not a webfinger server).

                      R 1 Reply Last reply
                      0
                      • girishG girish

                        @redegelde I replied in another post but look into /var/log/nginx/error.log as to who is the originator of these requests. This is just a misconfigured client. The logs by itself does not indicate an issue. It is just saying a request was made that Cloudron does not handle (and rightly so, Cloudron is not a webfinger server).

                        R Offline
                        R Offline
                        redegelde
                        wrote on last edited by
                        #13

                        @girish hi, found this here https://docs.cloudron.io/apps/mastodon/

                        Changing LOCAL_DOMAIN
                        You can change the account domain name by using the File Manager and changing LOCAL_DOMAIN in /app/data/env.production. After that, you have to configure LOCAL_DOMAIN's web server to serve up .well-known/host-meta query.

                        If LOCAL_DOMAIN is an app on Cloudron, you can use Cloudron's Well Known URI support. Go to the Domains view and set the Mastodon domain in the Advanced settings:

                        nebulonN 1 Reply Last reply
                        0
                        • R redegelde

                          @girish hi, found this here https://docs.cloudron.io/apps/mastodon/

                          Changing LOCAL_DOMAIN
                          You can change the account domain name by using the File Manager and changing LOCAL_DOMAIN in /app/data/env.production. After that, you have to configure LOCAL_DOMAIN's web server to serve up .well-known/host-meta query.

                          If LOCAL_DOMAIN is an app on Cloudron, you can use Cloudron's Well Known URI support. Go to the Domains view and set the Mastodon domain in the Advanced settings:

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

                          @redegelde I don't think all this has anything to do with your domain setup. The log message you see is maybe not even really related to mastodon on your Cloudron.

                          Also note that this log comes in the main system logs not the mastodon app logs. As @girish mentiones, this looks more like someone with an outdated or non standard mastodon client tries to connect with your instance. But the well-known URI is not /well-known-handler/... but `/.well-known/... so again I am not sure what the issue here is at all. As mentioned in the other thread maybe try to restart with a fresh installation on the correct domain in the first place.

                          R 1 Reply Last reply
                          1
                          • nebulonN nebulon

                            @redegelde I don't think all this has anything to do with your domain setup. The log message you see is maybe not even really related to mastodon on your Cloudron.

                            Also note that this log comes in the main system logs not the mastodon app logs. As @girish mentiones, this looks more like someone with an outdated or non standard mastodon client tries to connect with your instance. But the well-known URI is not /well-known-handler/... but `/.well-known/... so again I am not sure what the issue here is at all. As mentioned in the other thread maybe try to restart with a fresh installation on the correct domain in the first place.

                            R Offline
                            R Offline
                            redegelde
                            wrote on last edited by
                            #15

                            @nebulon hi, do you have some advise for this newbe.
                            😉
                            server now does have enough space
                            fbc28aa6-4e70-4e86-95be-83be7cfa6780-image.png
                            But it looks like its not used by the Mastodon cloudron app.
                            Or do i see this wrong?
                            if so, what can i do so that the total GB would be used.
                            regards
                            Eric

                            nebulonN 1 Reply Last reply
                            0
                            • R redegelde

                              @nebulon hi, do you have some advise for this newbe.
                              😉
                              server now does have enough space
                              fbc28aa6-4e70-4e86-95be-83be7cfa6780-image.png
                              But it looks like its not used by the Mastodon cloudron app.
                              Or do i see this wrong?
                              if so, what can i do so that the total GB would be used.
                              regards
                              Eric

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

                              @redegelde I think it is all correct, mastodon simply only currently uses 33.8Gb thus far, but if it needs more it has plenty of space on disk left.

                              R 1 Reply Last reply
                              0
                              • nebulonN nebulon

                                @redegelde I think it is all correct, mastodon simply only currently uses 33.8Gb thus far, but if it needs more it has plenty of space on disk left.

                                R Offline
                                R Offline
                                redegelde
                                wrote on last edited by
                                #17

                                @nebulon thank you

                                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