This is a new problem for me that started a couple days ago. Using Jerboa and Firefox, I’m unable to post images on this instance. I am able to post images to the same communities using a different instance account. I am getting “network error” and Java errors (I’m unable to see the full error) while using Jerboa. On Firefox, I get an “image too large” error for 12 MB (edit: not GB, that’d be a huge image) images (not sure the limit) but “SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data” at smaller image sizes. I was able to post images on this instance before this. My Jerboa app is up to date. Any solution?

  • SalamanderM
    link
    fedilink
    21 year ago

    I recently changed the file size limit from 20 MB to 8 MB, maybe that caused the file size problem? I just changed it to 15 MB. But if your smaller file failed too, then I’m not so sure… Do others have this same issue?

    • cadamanteusOP
      link
      fedilink
      21 year ago

      Oooo I meant 12 MB for the image I was trying to upload earlier, not GB! That’d be a big image, haha.

      I am still getting “network error”/“timeout” errors on Jerboa when uploading smaller images. I can deal with the limit if I know what it is. Even my smallest images (255 KB) are getting this error on Jerboa.

      • SalamanderM
        link
        fedilink
        11 year ago

        I have checked and I get this error too in Jerboa when uploading to Mander but not Lemmy.ml… I will investigate, thanks.

        For the browser you only had the problem with the 12MB file, right?

          • SalamanderM
            link
            fedilink
            11 year ago

            Can you check again in Jerboa now? It seems to work now for me. I am not sure what the problem was, I just did a bit of a cleanup to make space and rebooted the server.

            • cadamanteusOP
              link
              fedilink
              11 year ago

              Seems to be fixed! Thanks! Is the limit under 10 MB now? I tried a couple things just over that, but then a sub-8 MB pic worked fine.

              • SalamanderM
                link
                fedilink
                21 year ago

                Yes, 10 MB at the moment. The reason is because I noticed several very large image files (~ 40 MB) being fetched through federation, and these are filling up the disk… So I set a smaller limit until I figure out how to avoid having the disk filled so quickly.

                • verde.viento
                  link
                  fedilink
                  21 year ago

                  This isn’t a solution to that problem, but perhaps it’s a good time to check in again and ask of there’s any material assistance that would be helpful from the community? You take on what must be increasing costs, and there are many here who appreciate the instance and would be glad to make a small towards additional drives or whatever else might be needed.

    • cadamanteusOP
      link
      fedilink
      11 year ago

      I’m having a different/similar issue today (didn’t try yesterday), both Jerboa and Firefox. I get the error “SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data” on Firefox and an error that looks similar to the “too big” error on Jerboa (though the full error doesn’t show). It’s happening with pretty small images. What’s up? 😅

      • SalamanderM
        link
        fedilink
        21 year ago

        Strange… Nothing should have changed (actually, I changed the settings back to 20 Mb), and space is fine. I’ve rebooted the server to see if that helps…

        • cadamanteusOP
          link
          fedilink
          21 year ago

          Seems to be resolved again, thanks, haha. Appreciate what you do!

          • SalamanderM
            link
            fedilink
            21 year ago

            Good! So this seems to be caused by a property that is built up over time, and cleared by rebooting the server… RAM, CPU, and disk space seemed fine when I checked before rebooting, so I am not sure what this might be. It could also have been that you tried to upload during a ‘CPU’ spike. Hopefully it doesn’t happen again to you!