For your information. I have also activated NFS and it works. I know it’s a security risk, but I’m not a bank and I need my videos. I added the following to the fstab and it works: XXX.XXX.XXX.XXX:/nfsshare /mnt/nfs/video nfs defaults 0 0
I was finally able to put my bare-metal server online for our association.
I analyze the way it is built and I try to understand how to administer it well (update of the Ubuntu base, Nextcloud and its applications, and docker images which are part of it).
I twice lost the link between Nextcloud and Collabora (.odt files would no longer open, with a connection error message, but why ?), but reinstalling Collabora fixed the problem.
Until this morning, when the “richdocuments” application went to 3.6.0, and the reinstallation of Collabora could not do anything.
After searching on this forum, I found the solution here
Adding the two lines indicated by ‘helge’ and relaunching Apache fixes the problem.
But I realized that, despite the fact that I did an Nextcloud update (at least I thought so) with the script: sudo bash /var/scripts/update.sh,
I didn’t see any changes in this scripts directory, in particular, the menu.sh script is not present, although it seems to be part of the scripts copied during the global installation.
Also, the versions of the scripts on my machine and on the master branch of git are not the same.
Is it possible to update the script directory to stay at the git level, and is there a script to do it?
Would relaunching a full installation do this job without breaking existing configuration items?
PS: I am an old retired IBM AIX sysadmin and I’m not very comfortable with docker
update.sh gets the latest nextcloud_update.sh and runs that, but it doesn’t download all the latest scripts from Github, New functions and scripts are only released in new versions of Nextcloud, and regarding menu.sh that’s not released until Nextcloud 19 or 18.0.5. You could download it manually though - it will run, and it will work with the current lib.sh file.
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.
You shouldn’t run the startup script for update. The fact that it’s still there tells me that something went wrong during the initial run, or you didn’t reboot the server properly. The last thing that happens is that the startup script is removed. but it only happens if you reboot.
The correct way of updating is using the update script: