[Support] Linuxserver.io - Nextcloud


Recommended Posts

On 1/23/2021 at 3:29 AM, ps2sunvalley said:

Well I broke my NC docker.  Now getting the 


This version of Nextcloud is not compatible with > PHP 7.3.
You are currently running 7.4.14.

I tried the manual upgrade process via the terminal but it just does this:

 


Linux 4.19.107-Unraid.
Last login: Fri Jan 22 20:06:47 -0600 2021 on /dev/pts/0.
root@unRaidServer:~# docker exec -it nextcloud bash
root@5b88b245dc63:/# sudo -u abc php7 /config/www/nextcloud/occ maintenance:mode --on
This version of Nextcmv /config/www/nextcloud /config/www/nextcloud-backuprrently running 7.4.14.root@5b88b245dc63:/# mv /config/www/nextcloud /config/www/nextcloud-backup
root@5b88b245dc63:/# 

Any quick fixes or did I really jack this one up?

 

Hello, 

 

If you were running nextcloud 17; like me you didn't keep nextcloud up to date, version 17 is not officially compatible with php 7.4. By chance the upgrade scripts do run on php 7.4. (revert back to the previous version if you tried to pdate manually); 

 

If you are runnning an even earlier version of nextcloud, this will probably not work; 

 

You should do a backup of the database as well before attemting this, as if one of the upgrade scripts fails because of the php version your database will be in a strange half migrated state. So try this to your own risk. 

 

I did the following: 
 

docker exec -it nextcloud updater.phar

This updated my nextcloud to version 17. But it couldn't run the upgrade scripts. By chance the upgrade scripts of v17 works with php 7.4.

 

Open up appdata\nextcloud\www\nextcloud\lib\versioncheck.php and remove everything beside the <?php at the first line 

 

Now run the upgrade script

 

docker exec -it nextcloud occ upgrade

 

Disable maintenance mode 

 

docker exec -it nextcloud occ maintenance:mode --off

 

Now re-run, 

docker exec -it nextcloud occ upgrade

until there is no update left.

 

Hope it helps, ; 

The best way to actually do it, would be by changing the image to get an older version; then run the upgrades; then update the image again. I couldn't bother with that 

 

  • Like 1
  • Thanks 2
Link to comment
On 1/22/2021 at 3:30 PM, REllU said:

 

I'll look into this more, and try out using the certificates from cPanel!

Just to clarify though, I do have certificates from letsencrypt, and they seem to be working outside of the network just fine, as I'm able to get a secure connect to both, OnlyOffice server as well as NextCloud outside of the network.

 

I'll report back once I've tested cPanel certificates!

 

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.

 

Link to comment

Is there a simple way to fix this warning? In the Nextcloud Overview page.

 

"

There are some warnings regarding your setup.

Some columns in the database are missing a conversion to big int. Due to the fact that changing column types on big tables could take some time they were not changed automatically. By running 'occ db:convert-filecache-bigint' those pending changes could be applied manually. This operation needs to be made while the instance is offline. For further details read the documentation page about this.

filecache_extended.fileid

"

Link to comment



By running 'occ db:convert-filecache-bigint' those pending changes could be applied manually.


It says it right there.
occ maintenance:mode --on
occ db:convert-filecache-bigint
occ maintenance:mode --off

Done

Sent from my Mi 10 Pro using Tapatalk

Link to comment

A few days ago, after updating it in the usual way (update in the docker tab) and I also got the "This version of Nextcloud is not compatible with > PHP 7.3.
You are currently running 7.4.14." issue, like more people in this thread.

A day earlier I suddenly couldn't access my Unraid UI anymore after updating some plugins and dockers, even though everything else worked (dockers, shares etc), so I had to reboot (after 266 days of uptime 😭) to fix it magically.

I also jumped over from Let'sEncrypt to Swag using SpaceInvaderOne's video, thinking that might've been the issue. During that I saw that where he changed the config.php of Nextcloud, mine doesn't have the "trusted_proxies" line. I doubt it is, but could this be related?

AFAIK I have the latest version of this docker. (had an update today)

Was anyone able to fix this issue?

 

Just for the nerd in me: The error mentions that nextcloud is incompatible with PHP 7.3 and that I'm running 7.4.14.. What is the problem then? I would understand it if I was running PHP 7.3, but it mentions a lower version then I'm running. Why would it not work? Is it a config-line somewhere that forces nextcloud to run in 7.3, while it isn't compatible with it?

Link to comment
1 hour ago, FooYoungHi said:

A few days ago, after updating it in the usual way (update in the docker tab) and I also got the "This version of Nextcloud is not compatible with > PHP 7.3.
You are currently running 7.4.14." issue, like more people in this thread.

A day earlier I suddenly couldn't access my Unraid UI anymore after updating some plugins and dockers, even though everything else worked (dockers, shares etc), so I had to reboot (after 266 days of uptime 😭) to fix it magically.

I also jumped over from Let'sEncrypt to Swag using SpaceInvaderOne's video, thinking that might've been the issue. During that I saw that where he changed the config.php of Nextcloud, mine doesn't have the "trusted_proxies" line. I doubt it is, but could this be related?

AFAIK I have the latest version of this docker. (had an update today)

Was anyone able to fix this issue?

 

Just for the nerd in me: The error mentions that nextcloud is incompatible with PHP 7.3 and that I'm running 7.4.14.. What is the problem then? I would understand it if I was running PHP 7.3, but it mentions a lower version then I'm running. Why would it not work? Is it a config-line somewhere that forces nextcloud to run in 7.3, while it isn't compatible with it?

What version of Nextcloud you running? 
Settings > Overview > Version

Link to comment
On 1/16/2021 at 11:10 PM, Loch said:

@BrunoVic@jmial  I've been running NC since like vers 12 or so and about every other time I upgrade it bonks totally. When I upgraded NC this time I ran into the same "internal Service Error". According to the NC forums that pretty much the generic error message. Instead of going through the logs I decided to just nuke the Docker image and delete the appdata directory. I was on vers 18 and was only really using it for file serving/backup which I have all going to a directory outside the appdata directory and Docker so I figured those files were all safe anyway. I tried deleting and starting from my back-up NC appdata folder but it gave me the same error.

 

After you delete the NC image and dir (I actually moved it instead for backup - although it doesn't work), you can just load your NC template and start from scratch. It will automatically install the newest version (v20) and recreate the appdata directory.

 

You will need to connect it to the old database so NOTE: If you want to keep your users/pw you will need to know your user/database/pw for your Nextcloud database on Maraidb (assuming you did the SpaceInvader video you can go there and maybe you used the same?? Fortunately I wrote mine down). O/w you will need to start fresh with a new db and users, etc :(

 

The issue I ran into here was it would not let me use the same admin account I used before so I had to create a new admin username/pw  and then use the old database. But with that, it set up and everything was still there including my upload history and such for other users. 

 

This is what worked for me. Good luck. But you may want to make back-ups of everything just in case.  I like Nextcloud and it has gotten much better over time, but it is still very temperamental! If it's not something easily googled, I just wipe it and start over.

 

 

Yeah that's basically the only thing I could do too. I had to start from scratch. Unfortunately there was no way to fix it from the state it was in. Despite what Skois says this wasn't some letsencrypt or 'overwritehost' => 'nc.domain.com' issue. Unfortunately I did find the logs the message was referencing but it didn't have any information. The logs were acting like the server was running normally. No errors what so ever. It looks like your strategy is the best we can do so far. I appreciate the response!

Edited by BrunoVic
Link to comment
8 minutes ago, skois said:

occ status

It gives me this:

"root@1af0fcd2c990:/# occ status
This version of Nextcloud is not compatible with > PHP 7.3.<br/>You are currently running 7.4.14.root@1af0fcd2c990:/#"

 

I've done some digging into SpaceInvaderOne's videos, and I notice he has a video about upgrading Nextcloud that I missed. I'm following the guide now and see if that fixes it. I assume I'm still at version 15..

 

Edit: He updates through Nextcloud itself, so I obviously can't do that anymore.

Edited by FooYoungHi
Link to comment
2 minutes ago, FooYoungHi said:

It gives me this:

"root@1af0fcd2c990:/# occ status
This version of Nextcloud is not compatible with > PHP 7.3.<br/>You are currently running 7.4.14.root@1af0fcd2c990:/#"

 

I've done some digging into SpaceInvaderOne's videos, and I notice he has a video about upgrading Nextcloud that I missed. I'm following the guide now and see if that fixes it. I assume I'm still at version 15..

Well that's it. If you upgrade docker, you must upgrade nextcloud also. So both of them keep up.
Here is the tags of the docker, you need to roll back. 

Update your nextcloud to v19,
update the docker to latest again.
update your nextcloud to v20.

 

This docker tag should let you access webui
linuxserver/nextcloud:19.0.3-ls100

 


https://hub.docker.com/r/linuxserver/nextcloud/tags?page=1&ordering=last_updated 

 

If you don't want to update NC instance. try the latest working tag for you.
And keep it. Latest tags are for the latest NC instances.

  • Thanks 1
Link to comment

Anyone else have issues with Two-Factor TOTP Provider since the update to 20.0.6? The app has disappeared from my list... Its not in my disabled list, active list nor am I able to download it from the apps section. Problem I have is that it was active prior to the update and nextcloud is still looking for 2FA but says it hasnt been configured, as shown. I have managed to disable it for now but id like to actually have it active. Anyone else experience/fix this? 

msedge_yoOdPbJjGF.png

Link to comment
24 minutes ago, skois said:

Well that's it. If you upgrade docker, you must upgrade nextcloud also. So both of them keep up.
Here is the tags of the docker, you need to roll back. 

Update your nextcloud to v19,
update the docker to latest again.
update your nextcloud to v20.

 

This docker tag should let you access webui
linuxserver/nextcloud:19.0.3-ls100

 


https://hub.docker.com/r/linuxserver/nextcloud/tags?page=1&ordering=last_updated 

 

If you don't want to update NC instance. try the latest working tag for you.
And keep it. Latest tags are for the latest NC instances.

Thanks!!

I'm back into NC again and updating as we speak.

Is this way of updating (where you basically need to update twice) very common with dockers?

Link to comment
22 minutes ago, FooYoungHi said:

Thanks!!

I'm back into NC again and updating as we speak.

Is this way of updating (where you basically need to update twice) very common with dockers?

Depends. Most dockers run an update script on startup. So it updates the containing app every time you start it.
But nextcloud is too complicated to update automatically.

Because some apps you use might not be updated yet, or other dependecies inside nextcloud app. So for this reason, you need to update it yourself.

If you stay one major version behind the latest stable on NC app, docker base packages will be fine. But if you stay too many behind, some base packages might get end of life, (like the php you had problem now.) If you had upgraded to 19 you wouldnt have any problems!


For some reason i believe my english in this post is very bad (not native), i'm tired, Sorry :D 

Link to comment
On 1/25/2021 at 6:41 PM, whitedwarf said:

 

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.

 

 

Sorry for the late response.

I wasn't able to find a line for "rejectUnauthorized" in the default.json file at all :(

 

Unfortunately, I don't have time anymore to really do any more trobleshooting with this, so I'll probably have to give up and continue using Google Docs/Sheets until our current project is done and I have a bit of time in my hands again.

 

I still feel like my issue has something to do with me not being able to connect to NextCloud within the same network. Not about the certificates, but how our network is setup. Again, the modem we have does not support hairpinning, and we don't have a way to create vlan:s at this point. Could someone confirm if someone else got OnlyOffice  or Collabora to work without hairpinning or setting up a vlan to their network?

Link to comment
23 minutes ago, REllU said:

 

Sorry for the late response.

I wasn't able to find a line for "rejectUnauthorized" in the default.json file at all :(

 

Unfortunately, I don't have time anymore to really do any more trobleshooting with this, so I'll probably have to give up and continue using Google Docs/Sheets until our current project is done and I have a bit of time in my hands again.

 

I still feel like my issue has something to do with me not being able to connect to NextCloud within the same network. Not about the certificates, but how our network is setup. Again, the modem we have does not support hairpinning, and we don't have a way to create vlan:s at this point. Could someone confirm if someone else got OnlyOffice  or Collabora to work without hairpinning or setting up a vlan to their network?

I don't think this is the problem here.. Because you connect to the openoffice through your external ip (domain), but again i might be wrong here.!

Link to comment
4 hours ago, tazire said:

Anyone else have issues with Two-Factor TOTP Provider since the update to 20.0.6? The app has disappeared from my list... Its not in my disabled list, active list nor am I able to download it from the apps section. Problem I have is that it was active prior to the update and nextcloud is still looking for 2FA but says it hasnt been configured, as shown. I have managed to disable it for now but id like to actually have it active. Anyone else experience/fix this? 

msedge_yoOdPbJjGF.png

 

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

Link to comment

So like many others, I got the below error.

 

Quote

This version of Nextcloud is not compatible with > PHP 7.3. You are currently running 7.4.14.

 

I was able to revert my docker image version by changing the repository under the container settings to linuxserver/nextcloud:20.0.2-ls107 from linuxserver/nextcloud.

 

This version allowed me to start NC.

 

Now going to Settings > Overview > Version, I can see I am running NC version 16.0.1.

 

So what is the proper way to update in order to use latest docker image?

Link to comment
So like many others, I got the below error.
 
This version of Nextcloud is not compatible with > PHP 7.3. You are currently running 7.4.14.
 
I was able to revert my docker image version by changing the repository under the container settings to linuxserver/nextcloud:20.0.2-ls107 from linuxserver/nextcloud.
 
This version allowed me to start NC.
 
Now going to Settings > Overview > Version, I can see I am running NC version 16.0.1.
 
So what is the proper way to update in order to use latest docker image?
Update nextcloud until you get to version 19
Change docker repo to the latest again
Update the nextcloud to v20

After that keep in mind you need to first update image and then nextcloud


Sent from my Mi 10 Pro using Tapatalk

Link to comment
13 hours ago, skois said:

I don't think this is the problem here.. Because you connect to the openoffice through your external ip (domain), but again i might be wrong here.!

 

My understanding here, is that while the domain does indeed has it's own IP (of the domain server), it does still redirect your browser to our public IP, where our UnRaid server is.

From there, it's supposed to be picked up by the proxy, and then re-directed to the correct local-ip.

 

However, it never reaches the proxy, since again, my modem doesn't support hairpinning, meaning that when it gets asked to redirect a website to the same IP address the modem itself has, it doesn't know what to do with it. (I'm sure there's a better explanation of this, but I don't have the understanding to really dig that deep into this)

So what ends up happening, is that my domain does redirect the request to our public IP, our modem gets the request, and doesn't know what to do with it from that point on. Proxy never gets the request to redirect it.

 

 

12 hours ago, whitedwarf said:

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) ?

 

I didn't set up my NextCloud with Spaceinvaderone's video, as that didn't seem to work for me. Instead, I used this guide to set everything up:

https://medium.com/@chrismorris_82249/setup-a-reverse-proxy-nextcloud-server-on-unraid-using-letsencrypt-831905d94f7d

 

Within that guide, it shows how to create your custom network within UnRaid, like so:

docker network create <networkname>

 

I did this, and the dockers are indeed within this same network.

I do remember seeing some more configurations being done to such a network in somewhere, on top of just creating one.

Link to comment
15 hours ago, whitedwarf said:

 

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

not just yet... but i havent actually sat down to try fix it. Ill keep you posted. 

Link to comment

Hi folks, I searched for high IO but couldn't find any references.

 

below is an image of my cache drive IO with nextcloud docker image on. I added several "external storage" locations as "local" in nextcloud but other than that there's really nothing ON nextcloud. I do believe it's indexing photos metadata or something but I'm trying to find out why my cache drive is at 300-800 MB/s for nearly 24 hours after I install nextcloud. When I stop the nextcloud container the IO goes back to normal. 

 

I do also have my mysql database on this cache drive too which is really only being used by nextcloud ATM. Any ideas on why such high IO?

image.thumb.png.2fc87141c1043954e844d929274263c6.png

 

Another thing to note, it's been writing at these speeds for nearly 24 hours, mover has not run, and yet, no major disk usage impact. The Used/free ratio really hasn't changed...any ideas here?

Link to comment

 

37 minutes ago, whitedwarf said:

 

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

 Yea im about to go through the manual process of installing the app now... just looking at the appdata for nextcloud it appears to have fully removed the app files from the app folder. I get that during install it may for whatever reason show the app as incompatible  with that version but im surprised it has disappeared from the app list as a download option! 

 

EDIT

No joy on first attempt....

docker exec -it nextcloud occ app:install twofactor_totp
Error: Could not download app twofactor_totp

 

EDIT 2

Solved it...

I downloaded the .tar file fully extracted it and put it in the apps folder in the appdata and restarted nextcloud. The app re appeared in the disabled list for me. Enabled it and seems to be working as before. Still held the same link to my Google Auth app too. Was expecting to have to set this up again and delete the old one but seems to be fine. 

Edited by tazire
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.