whitedwarf

Fixed:

I have found this fix in another thread: Change the mariadb docker repository to "linuxserver/mariadb:110.4.21mariabionic-ls31" (without the " of course) and let it run. Then edit the docker repository again to "linuxserver/mariadb:latest" and it should run fine again.

Since last update I have the same error as you: 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. I think the update broke something but I have no idea what.

Don't know if it will help but I have the IP of my unraid server and the domain name of my nextcloud instance (nextcloud.mydomain.com) in the trusted domains. I would suggest you change that back and try to solve the other error.

@eubbenhadd That sounds messy. Have you tried to update directly from unraid command shell with the following command ? docker exec -it nextcloud updater.phar

First time I hear about this functionality, but it looks like my consumer grade modem has it. It's a shame you have to change it again.

Very strange. I had issues before upgrading (I was still on a 18.x version). The application tab was empty and I got the same message as you when trying via occ command. But it was solve with the update. Hopefully everything is in order now.

Ok I disabled the app before upgrading to 20.0.6 and enabled it afterwards without any issue.

I was about to upgrade when I saw your message. Were you able to solve the issue and have TOTP working back as normal ?

I have the same impression. It's probably more related to the reverse proxy setup. REllU, did you make sure all the related dockers are using the same "network type" (called proxynet in the video done by Spaceinvaderone) ?

FYI I just successfully reinstalled the OnlyOffice integration with nextcloud. I was getting an error when trying to connect to the Onlyoffice server in nextcloud. Looking at the OnlyOffice docker log I found out that it was due to a certificate error. Finally I was able to solve it by following these steps: 1. Open the console on the container 2. browse to /etc/onlyoffice/documentserver/default.json 3. Set 'rejectUnauthorized' to false Maybe it could solve your issue as well.

I followed this guide which is very complete. You can find the configuration file for Authelia as well as for the NginxProxyManager at the top and the page. https://github.com/ibracorp/authelia Just tell me if you need more info, I'll gladly share.

Nextcloud is a fantastic cloud storage with lots of options (I also use it to sync my agenda & contacts with my phone) but the office integration is too bad IMO. I spent hours trying to setup the integration of Collabora or OnlyOffice with my Nextcloud docker. I even got OnlyOffice working for a moment but then I updated a docker or changed something somewhere and it was over. I have not been able to make this integration work anymore. Instead of hitting my head against a wall I installed the CryptPad docker. OnlyOffice is integrated natively and you can easily import an existing document and export it when modified without creating an account. If you create an account you can benefit form its encrypted file storage but it is limited to compatible files only (you cannot use it to store something else than "pads"). In the end I could not find an ideal solution but I am quiet happy with that setup: nextcloud as a cloud service and CryptPad as a document editor.

I just wanted to give a positive feedback as I was able to install the docker on my server and to import 21k pictures & videos. For me the main missing feature is the lack of authentification. Basically anyone having access to your network can openly browse your pictures. To secure it I installed the Authelia docker, which works well with NginxProxyManager. It took me some time (had a short night afterwards ) but it is now secured and works flawlessly.

Thanks man. I had the same issue as you and didn't realize it was as easy as enabling the option in the proxy host configuration !