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. Nextcloud
  3. Internal Server Error

Internal Server Error

Scheduled Pinned Locked Moved Solved Nextcloud
4 Posts 2 Posters 739 Views 2 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.
    • E Offline
      E Offline
      ekevu123
      wrote on last edited by
      #1

      I am getting an Internal Server Error on my Nextcloud instance.

      Version: Nextcloud 25.0.2

      Full error message when opening the domain:
      Internal Server Error

      The server encountered an internal error and was unable to complete your request.
      Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
      More details can be found in the server log.

      The app status in Cloudron is constantly "starting", before that I had "not responding". I tried restarting the app, that's why it changed.

      The issue started occuring after a server restart via Cloudron.

      The logs keep repeating this error message:

      Could not get appdata folder for js
      

      Not sure what to do with that?

      E 1 Reply Last reply
      0
      • E ekevu123

        I am getting an Internal Server Error on my Nextcloud instance.

        Version: Nextcloud 25.0.2

        Full error message when opening the domain:
        Internal Server Error

        The server encountered an internal error and was unable to complete your request.
        Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
        More details can be found in the server log.

        The app status in Cloudron is constantly "starting", before that I had "not responding". I tried restarting the app, that's why it changed.

        The issue started occuring after a server restart via Cloudron.

        The logs keep repeating this error message:

        Could not get appdata folder for js
        

        Not sure what to do with that?

        E Offline
        E Offline
        ekevu123
        wrote on last edited by
        #2

        The issue is that the base volume where Nextcloud has all its data didn't mount after the restart.

        girishG 1 Reply Last reply
        1
        • E ekevu123

          The issue is that the base volume where Nextcloud has all its data didn't mount after the restart.

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

          @ekevu123 do you mean the data directory did not mount i.e https://docs.cloudron.io/apps/#data-directory ?

          Also, did you get this sorted out or is this issue still pending? Does remounting the volume and then restart the container help?

          E 1 Reply Last reply
          0
          • girishG girish

            @ekevu123 do you mean the data directory did not mount i.e https://docs.cloudron.io/apps/#data-directory ?

            Also, did you get this sorted out or is this issue still pending? Does remounting the volume and then restart the container help?

            E Offline
            E Offline
            ekevu123
            wrote on last edited by
            #4

            @girish Hi, sorry, I wasn't clear, I sent the second message and wanted to indicate that I found the issue and resolved it. The volume wasn't mounted correctly in the fstab.

            1 Reply Last reply
            1
            • nebulonN nebulon marked this topic as a question on
            • nebulonN nebulon has marked this topic as solved on
            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