I had my NC Server running for 3 months through VB on an Ubuntu 22.04 host with no real issues. I downloaded it from Index of /aio-vm
To keep disk usage low I did not unminimize it. If I needed a command that wasnât there I have been installing it. If you want me to run a command for testing, please include the commands necessary to install the command incase I donât have it.
I have an SSL cert from LetsEncrypt. I used the certbot. No SSL issues.
I was syncing folders into a nextcloud share and everything was ine, then I started getting red Xs on everything. I shut it down and rebooted and it never came back up. I didnât check status of containers before rebooting. I went into the AIO and saw everything running excep for Apache and Nextcloud which were stuck on Starting.
I tried to create new doc in the folder and on the web interface and nothing was syncing; I was also getting the same pop up error on everything saying the file could not sync due to an error.
My research hasnât come up with anything helpful but I will post what I can
chrome will not open these links becasue they are not SSL, but you can view them through MS Edge. I donât know about firefox.
Link to results of sudo docker inspect nextcloud-aio-apache: http://nextme.ddns.net:8020/logs/docker.txt
I couldnt run these commands as ncadmin so i did sudo su, which Iâve done many times but this time I got this message:
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin âxcbâ in ââ even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
root@nextcloud:/mnt/ncdata# docker logs nextcloud-aio-apache
Waiting for Nextcloud to startâŚ
Waiting for Nextcloud to startâŚ
Waiting for Nextcloud to startâŚ
It displays so many of these lines that I can't see the beginning. I tried to redirect to a file
root@nextcloud:/mnt/ncdata# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/ubuntu-vg/ubuntu-lv during curtin installation
/dev/disk/by-id/dm-uuid-LVM-Go2c6FQtJct0RcUMGt59JOVirRS9ftcQc75HYXafYAAPPZn85dfmUwPwzi00n3Eu / ext4 defaults 0 1
# /boot was on /dev/sda2 during curtin installation
/dev/disk/by-uuid/0ceee2f6-3004-4acd-9529-8314584a9980 /boot ext4 defaults 0 1
# /boot/efi was on /dev/sda1 during curtin installation
/dev/disk/by-uuid/B75A-BE99 /boot/efi vfat defaults 0 1
/swap.img none swap sw 0 0
//192.168.1.1/storage /mnt/ncdata cifs vers=1.0,uid=www-data,gid=www-data,credentials=/mnt/.credentials,iocharset=utf8 0 0
//192.168.1.1/nextcloudbackup /mnt/backup cifs vers=1.0,uid=www-data,gid=www-data,credentials=/mnt/.credentials,iocharset=utf8 0 0
root@nextcloud:/mnt/ncdata#
Is the network drive still mounted? Can you reboot the VM and afterwards run sudo -ls /mnt/ncdata and check if the container has access to the mountpoint afterwards again?
I see. Please run sudo docker stop nextcloud-aio-apache then and reload the AIO interface. Then you should have the option to stop them and afterwards you should be able to start them again.