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


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved Internal Server Error

    Nextcloud
    2
    4
    89
    Loading More Posts
    • 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
      ekevu123 last edited by

      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 Reply Quote 0
      • E
        ekevu123 @ekevu123 last edited by

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

        girish 1 Reply Last reply Reply Quote 1
        • girish
          girish Staff @ekevu123 last edited by

          @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 Reply Quote 0
          • E
            ekevu123 @girish last edited by

            @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 Reply Quote 1
            • Topic has been marked as a question  nebulon nebulon 
            • Topic has been marked as solved  nebulon nebulon 
            • First post
              Last post
            Powered by NodeBB