Nextcloud/Mariadb/Swag Internal Server Error for WebUI


Ocman76

Recommended Posts

I have just followed Spaceinvaderone's tutorial on setting up Nextcloud on Unraid. After I finish setting everything up (and make the changes to address the 502 bad gateway error) I try to start the Nextcloud webui and get the following error:

 

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 webserver log.

 

There are multiple other Unraid forum threads on this issue and I have tried all the solutions with no luck, including:

 

  1. Change the mariadb docker repository to "linuxserver/mariadb:110.4.21mariabionic-ls31" and let it run.

    Then edit the docker repository again to "linuxserver/mariadb:latest" Source here.

  2. Opening a console on the mariadb docker and running the following commands:

    > cd /config/databases

    > rm ib_logfile0

    > rm ib_logfile1

    Then stopping and restarting both nextcloud and mariadb. Source here.

  3. Completing removing the mariadb docker and image and reinstalling from scratch.

 

I do not see any errors in the mariadb logs.

In the Nextcloud logs I see a repeated error: PHP Fatal error: Uncaught Error: Call to a member function getLogger() on null in /config/www/nextcloud/cron.php:192

In the Swag logs I see one warning: 2023-01-29 16:04:42,345 fail2ban.configreader [406]: WARNING 'allowipv6' not defined in 'Definition'. Using default one: 'auto'

 

Does anyone have any suggestions on how to fix this?

Edited by Ocman76
Spelling
Link to comment
  • Ocman76 changed the title to Nextcloud/Mariadb/Swag Internal Server Error for WebUI
  • 2 months later...
4 hours ago, itskamel said:

did you ever get this fixed? if so what was it?

I did not. I posted both here and on the Unraid reddit and got no responses. I ended up using Filebrowser instead which works for my purposes and was much easier to set up. The only tricky part was setting up the ports correctly with Swag. If helpful let me know and I can post the port configuration I ended up using to get it to to work.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.