Eddie_B

I have run into an interesting problem. For reasons I can no longer remember, I had my nextcloud stuck to version 27.1.4-ls289 and I'm trying to upgrade it now. When I tried to change my repository to :latest, that didn't work due to being 2 versions behind. So, I attempted to change it to both 28.0.0-ls290 and 28.0.4-ls315 and got an error on the upgrade. Initializing nextcloud 28.0.0.11 (this can take a while) ... Upgrading nextcloud from 27.1.4.1 ... Setting permissions Nextcloud or one of the apps require upgrade - only a limited number of commands are available You may use your browser or the occ upgrade command to do the upgrade Setting log level to debug Turned on maintenance mode Updating database schema Exception: Database error when running migration 28000Date20231103104802 for app core An exception occurred while executing a query: SQLSTATE[42S02]: Base table or view not found: 1932 Table 'nextcloud.oc_files_versions' doesn't exist in engine Update failed Maintenance mode is kept active Resetting log level Initializing finished **** The following site-confs have extensions other than .conf **** **** This may be due to user customization. **** **** You should review the files and rename them to use the .conf extension or remove them. **** **** nginx.conf will only include site-confs with the .conf extension. **** /config/nginx/site-confs/default.conf.bak [custom-init] No custom files found, skipping... [ls.io-init] done. I checked the database, and the oc_files_versions table is actually in the database, so I have no idea why it's failing due to this table not existing.

About to start on the recreation, but I'm curious. Am I correct in assuming that nothing in the diagnostics looked out of sorts, so the next best guess is a corrupted docker image?

I was having some issues with dockers being very slow to respond so I restarted the server. Now, after the restart, I'm getting the Docker Service failed to start message wellspire-diagnostics-20240610-1149.zip

I am actually in the process of doing that now, thanks!

I had been working on editing a couple of html files in my swag container, then left my server alone for a while. I was later attempting to access nextcloud but it wouldn't load. Assuming that I had a problem with the html files I edited, I tried to change them back but got a message "rm: cannot create regular file 'index.html': Read-only file system" Now, after a restart, my dockers aren't functioning, they show as started but they don't respond when trying to use any of them. Fix common problems shows that my cache drive is either mounted read-only or completely full. wellspire-diagnostics-20231031-1423.zip

I just stopped my docker services, switched over to ipvlan, and restarted docker. I'll let it run like that for a couple of days and see how it goes. Thanks for the suggestion!

I've been having some issues with my server recently where it keeps crashing on me. After restarting, things will be fine for a little while, then it freezes up again. I've attached my diagnostics and would appreciate it if anyone can help me figure this out. wellspire-diagnostics-20231030-1202.zip

Unfortunately, booting in safe mode is giving the same results.

I have not tried that yet. I'll give it a shot in a little while and report back.

Anyone have any ideas here?

Somehow, at some point in the last couple of days, my Nextcloud docker started having issues. Monday morning things were fine, but at some point in the afternoon we started getting a 504 error. Nothing had been changed in Nextcloud or Unraid, so I'm at a loss as to what happened. Since the problem came up, I made sure that all of my dockers are up to date, as well as Unraid, I've restarted the server, but we're still seeing the problem.

For the last couple of days, my GUI has been running very slowly, and when I try to open the console from the GUI, I'm getting a 502 error. Opening consoles for my dockers has been hit & miss, but I can SSH in to the server. I don't know when the problem exactly started because the dockers, which is all we use the server for, had been running fine for a while. I started looking on the server when Nextcloud quit working for some, so far unknown, reason. Any help would be appreciated! wellspire-diagnostics-20230503-1229.zip

I'm having an issue with the forgot password feature. When I use the forgot password link, I can enter my email and it does send an email with a link, but when I use the link I get a warning about potential security risk. I accept, and it sends me to the "Welcome to your swag instance" page

I have attempted to wipe out Nextcloud and start over from scratch with it, but I am still running into the same issue. The collabora admin page, collabora root level page, hosting/discovery, and hosting/capabilities pages are all visible but every time I try to configure the app, I get the "Could not establish connection to the Collabora Online server." message.

Anyone got any ideas here?

I have previously set up both Nextcloud and Collabora on my personal Unraid server and it has been cranking along fine for quite some time. Recently my boss discovered Nextcloud and wanted it. We initially had it running on a Synology but between the limited resources on the Syno and some behind the scenes networking stuff, we made the move to Unraid. I was able to successfully move the database and all of the data over to our Unraid server and get it back up and running. Since I had not set Collabora up on the Synology, we were running without it on Unraid. I installed the Collabora docker, followed all of the same steps that I used on my personal server and I have been having all kinds of difficulty with it. When I try to enter the collabora address into the settings for Collabora Online in Nextcloud, it tells me that it could not establish a connection to the server. Looking at the nextcloud.log file, I found an error referring to the SSL certificate saying that it is a self signed certificate. Seeing as how I have both Nextcloud and Collabora sitting behind SWAG, this error doesn't make much sense to me, but I admit to not being an expert on this. I can access the Collabora admin page, and it does show that it is a secure connection verfied by LetsEncrypt.