[Support] Linuxserver.io - Nextcloud


5008 posts in this topic Last Reply

Recommended Posts

3 minutes ago, discojon said:

The config folder is located in your Nextcloud data location.  

 

 

The only options I'm presented with when updating in the container are stable and beta.  I don't have an option to upgrade to next version

The nextcloud web updater should offer you newer versions or you can cli into the container and run `updater.phar`

Link to post
  • Replies 5k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Application Name: Nextcloud Application Site: https://nextcloud.com/ Docker Hub: https://hub.docker.com/r/linuxserver/nextcloud/ Github: https://github.com/linuxserver/docker-nextcl

Here's my list of instructions....    Use them at your own risk.....   If upgrading to v12 please see here:   ##Turn on maintenance mode docker exec -it nextcloud occ m

I replaced these lines in the '/mnt/cache/appdata/nextcloud/nginx/site-confs/default' file. (Adjust path to your appdata path, if it's different)   location = /.well-known/carddav { return

Posted Images

3 minutes ago, j0nnymoe said:

The nextcloud web updater should offer you newer versions or you can cli into the container and run `updater.phar`

So I just started my restored docker and got the same PHP error as before.

 

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

 

Current version is 17.0.9. CLI in and ran

 

docker exec -it nextcloud updater.phar

 

and it is trying to upgrade. "Update to Nextcloud 17.0.10 available. (channel: "stable")".  As with the webupdater, it errors out with this.

 

oot@Tower:~# docker exec -it nextcloud updater.phar
Nextcloud Updater - version: v16.0.3-3-ga0c2b25 dirty

Current version is 17.0.9.

Update to Nextcloud 17.0.10 available. (channel: "stable")
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-17.0.10.zip
Open changelog ↗

Steps that will be executed:
[ ] Check for expected files
[ ] Check for write permissions
[ ] Create backup
[ ] Downloading
[ ] Verify integrity
[ ] Extracting
[ ] Enable maintenance mode
[ ] Replace entry points
[ ] Delete old files
[ ] Move new files in place
[ ] Done

Start update? [y/N] y

Info: Pressing Ctrl-C will finish the currently running step and then stops the updater.

[✔] Check for expected files
[✔] Check for write permissions
[✔] Create backup

Update stopped. To resume or retry just execute the updater again.

 

Link to post
36 minutes ago, discojon said:

So I just started my restored docker and got the same PHP error as before.

 


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

 

Current version is 17.0.9. CLI in and ran

 


docker exec -it nextcloud updater.phar

 

and it is trying to upgrade. "Update to Nextcloud 17.0.10 available. (channel: "stable")".  As with the webupdater, it errors out with this.

 


oot@Tower:~# docker exec -it nextcloud updater.phar
Nextcloud Updater - version: v16.0.3-3-ga0c2b25 dirty

Current version is 17.0.9.

Update to Nextcloud 17.0.10 available. (channel: "stable")
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-17.0.10.zip
Open changelog ↗

Steps that will be executed:
[ ] Check for expected files
[ ] Check for write permissions
[ ] Create backup
[ ] Downloading
[ ] Verify integrity
[ ] Extracting
[ ] Enable maintenance mode
[ ] Replace entry points
[ ] Delete old files
[ ] Move new files in place
[ ] Done

Start update? [y/N] y

Info: Pressing Ctrl-C will finish the currently running step and then stops the updater.

[✔] Check for expected files
[✔] Check for write permissions
[✔] Create backup

Update stopped. To resume or retry just execute the updater again.

 

Looks like someone had the same issue here: https://github.com/nextcloud/mail/issues/2583

Seems related to the Mail app within nextcloud.

Link to post
2 minutes ago, j0nnymoe said:

Looks like someone had the same issue here: https://github.com/nextcloud/mail/issues/2583

Seems related to the Mail app within nextcloud.

I ended up nuking the old docker container, and installing fresh, then connecting to my old DB.  I had to make a new admin user as referenced above but everything else seems to be working, and I'm back in parity at v20.  Sorting out the reverseproxy now as it stopped working.

Link to post
On 1/16/2021 at 6:38 PM, skois said:

Access the console of the nextcloud docker. 
Try running. "updater.phar"
If this errors out, do "occ maintenance:mode --off" and try accessing nextcloud webui, go to Settings->Overview and see if there is any errors, (probably should be) errors will probably be about missing things on DB. there you will also see the commands you need to run to fix them. (run them on the nextcloud docker console.
Then try again to update either from WebUI or from console with "updater.phar"

 

I tried taking maintenance mode off however this takes me back to the updater in the Webui.

 

It appears the problem relates to "oc_filecache" in the database as this file is 46GB. My array is only 6TB of storage space so something has evidently gone wrong.

 

I have tried running "occ files:scan --all" however I get the following error

There are no commands defined in the "files" namespace.

 

Seems like I might need to adjust something in MariaDB directly?

Link to post

All,

Just upgraded to the latest Nextcloud and now I can’t get into the docker. Latest ver 20.

Running R710 Dell Server, 48 Gb ram, 30Tb space on Unraid.
Docker container is linuxserver.

See attached file.

 

Here is the text in case you can’t see it:

Internal Server Error
The server was unable to complete your request.

If this happens again, please send the technical details below to the server administrator.

More details can be found in the server log.

Technical details
Remote Address: 192.168.1.29
Request ID: VuYu7IeO7IvoqC2iKHZl

 

 

I’m stumped - I haven’t had any problems for over a year.

I have checked all the usual culprits maintenance mode off, checked the files etc using occ.

Looking for a direction to head in to solve this…

I suspect its probably something dumb I did - these things usually are…

 

Thanks in advance

Toolmanz

ksnip_20210117-130236.png

Edited by toolmanz
Link to post
1 hour ago, toolmanz said:

All,

Just upgraded to the latest Nextcloud and now I can’t get into the docker. Latest ver 20.

Running R710 Dell Server, 48 Gb ram, 30Tb space on Unraid.
Docker container is linuxserver.

See attached file.

 

Here is the text in case you can’t see it:

Internal Server Error
The server was unable to complete your request.

If this happens again, please send the technical details below to the server administrator.

More details can be found in the server log.

Technical details
Remote Address: 192.168.1.29
Request ID: VuYu7IeO7IvoqC2iKHZl

 

 

I’m stumped - I haven’t had any problems for over a year.

I have checked all the usual culprits maintenance mode off, checked the files etc using occ.

Looking for a direction to head in to solve this…

I suspect its probably something dumb I did - these things usually are…

 

Thanks in advance

Toolmanz

ksnip_20210117-130236.png

 

See my post above. Good luck trying to find the cause. I just nuked the Docker image , deleted the app dir and reinstalled from the Unraid Docker template. I was up and running in <15 min (although I spent an hour or two trying to "fix" it before that). My set up isn't fancy so I don't really know what all you may loose.

 

I feel like updating Nextcloud is like putting it all on red at the roulette table.

 

 

Link to post

Well a little more information on the problem .....

 

The docker is running and except for the webui seems to be functioning as expected.

 

I did all of the maintenance as I would normally do with files and indices through OCC ..... not a problem.

 

I checked the PHP version and it is up to date (Jan 7-2021) [php -v in terminal]

 

"PHP 7.4.14 (cli) (built: Jan  7 2021 11:46:25) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
    with Zend OPcache v7.4.14, Copyright (c), by Zend Technologies"

 

So thats not it .... I have had that problem before and fixed it with an update.

 

I can still access most of my files through the Nextcloud sync client in Windows so not a complete loss. 

 

It's got to be with the webui only.... but can't think what that would be since nothing else changed. 

 

I use reverse proxy for remote access but get the same error when I access locally - so that's not it....

 

I get the same error in Linux Mint when I try to use the webui ...at least its consistent🙄

 

Well I'll bump along and noodle on this some more....perhaps there are others that run into the same problem and will wake up the NC folks to the problem.

 

I left the same post on the NC support forum.

 

Ill post back if I find a solution ....🤔

 

Thanks for the responses .... we will figure this out .....

 

Cheers

 

Toolmanz

 

Link to post
8 hours ago, toolmanz said:

Well a little more information on the problem .....

 

The docker is running and except for the webui seems to be functioning as expected.

 

I did all of the maintenance as I would normally do with files and indices through OCC ..... not a problem.

 

I checked the PHP version and it is up to date (Jan 7-2021) [php -v in terminal]

 

"PHP 7.4.14 (cli) (built: Jan  7 2021 11:46:25) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
    with Zend OPcache v7.4.14, Copyright (c), by Zend Technologies"

 

So thats not it .... I have had that problem before and fixed it with an update.

 

I can still access most of my files through the Nextcloud sync client in Windows so not a complete loss. 

 

It's got to be with the webui only.... but can't think what that would be since nothing else changed. 

 

I use reverse proxy for remote access but get the same error when I access locally - so that's not it....

 

I get the same error in Linux Mint when I try to use the webui ...at least its consistent🙄

 

Well I'll bump along and noodle on this some more....perhaps there are others that run into the same problem and will wake up the NC folks to the problem.

 

I left the same post on the NC support forum.

 

Ill post back if I find a solution ....🤔

 

Thanks for the responses .... we will figure this out .....

 

Cheers

 

Toolmanz

 

You'll want to be checking your logs. nginx logs within the `/config` mount and also the nextcloud log itself in the root of your `/data` mount. That should give some sort of insight to what's happening.

Link to post

Hello everyone, I hope I'm doing this in the right place.

 

My issue is, that when I'm trying to set up OnlyOffice within Nextcloud, I'm getting:

Error when trying to connect (cURL error 7: Failed to connect to xxx.xxx.xx port 8443: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html))"

 

I've set up a cname for onlyoffice through cpanel, and connecting to onlyoffice directly from the web gives me a "Document server is running" message.

However, if I try to connect within the same network as the UnRaid server is in, I get an error. My guess is, that this is the reason why I can't connect to OnlyOffice through NextCloud? (NextCloud in itself doesn't work on the same network either, as my modem doesn't support hairpin / vlan unfortunately)

 

Trying to setup the demo Document Server everything works just fine. But obviously, this is not what I'm after.

 

I'm using SWAG (nginx) to reverse-proxy both NextCloud as well as the OnlyOffice docker, and like I've stated, both work nicely from outside of the network.

 

I've created a custom network within Unraid for all of these apps, so that they'd be able to talk with each other.

As for how I tried to setup the OnlyOffice, I followed Spaceinvader one's tutorial video. Before that, I tried to install Collabora with no luck (not getting any specific errors, but I'm suspecting the issue was the same) before giving up on that, and moving to OnlyOffice.

 

I haven't tested the Community Document Server directly from Nextcloud, but based on the reviews and things I've read online, I'm not too convinced I should even try that.

 

As for UnRaid, I only have OnlyOffice (named as "documentserver"), mariadb, nextcloud, and swag installed as dockers. (This server will be used as file server, Google Drive replacement, if you will, for our company)

I'm really new to servers, and networking in general (which you'll probably be able to tell), so there's a chance I've setup something very obvious incorrectly, but my knowledge of all this just seems to be not enough.

I'd really appreciate any help for this.

Edited by REllU
Adding more info
Link to post
15 hours ago, toolmanz said:

All,

Just upgraded to the latest Nextcloud and now I can’t get into the docker. Latest ver 20.

Running R710 Dell Server, 48 Gb ram, 30Tb space on Unraid.
Docker container is linuxserver.

See attached file.

 

Here is the text in case you can’t see it:

Internal Server Error
The server was unable to complete your request.

If this happens again, please send the technical details below to the server administrator.

More details can be found in the server log.

Technical details
Remote Address: 192.168.1.29
Request ID: VuYu7IeO7IvoqC2iKHZl

 

 

I’m stumped - I haven’t had any problems for over a year.

I have checked all the usual culprits maintenance mode off, checked the files etc using occ.

Looking for a direction to head in to solve this…

I suspect its probably something dumb I did - these things usually are…

 

Thanks in advance

Toolmanz

ksnip_20210117-130236.png

 

Had the same error.
Finally, for me the reason was "oc_filecache is corrupted".
Try to check the database tables for errors.

 

If also the table oc_filecache is corrupted try the following:

1. stop nextcloud container

 

2. clean database table

- truncate nextcloud.oc_filecache

- check table nextcloud.oc_filecache

(nextcloud is the database name and oc_ is the table name prefix, both of which are specified during setup and can differ on your system.)
This will delete the entire contents of the table, which is fine for oc_filecache, since it will be rebuilt by the server.

 

3. restart nextcloud container

Link to post
11 hours ago, j0nnymoe said:

You'll want to be checking your logs.

I had a look yesterday and the NC log shows all normal. 

 

I will do a deep dive into the logs as you suggest.

 

I'll post back the results. 

 

Also, a number of other paltforms are reporting similiar problems. It has to be something common to a number of platforms.

 

Thanks razoredge - will have a look around and see it that is the issue.

 

More later....

 

Cheers

 

Toolmanz

Edited by toolmanz
update
Link to post

I have uploaded the NGINX error.log and access.log.

 

I think I have removed any identifiable info and replaced with generic labels plus some notes.

 

It looks like this is where the problem is. 

 

nginx.server.error.lognginx.server.access.log

 

Let me know if there is something else I need to edit out (always nervous doing this....🥺)

 

I will visit the NC error log next but I think the above identifies the error.

 

Cheers

 

Toolmanz

Link to post
On 1/17/2021 at 3:17 PM, tillkrueger said:

I am also now getting the same error message as you, discojon, when starting the WebGUI of my Nextcloud Docker:

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


would you be able to let me know how exactly can I get it to work again?

Where exactly is this config folder where you edited versioncheck.php?

I had the same problem. My solution was manual upgrade to version 18.0.13 (from 17.0.x).

 

I did as described in first post of this thread, option 3. Manual upgrade using occ.

All commands are the same, except

docker exec -it nextcloud wget https://download.nextcloud.com/server/releases/latest.tar.bz2 -P /config

must be replaced with

docker exec -it nextcloud wget https://download.nextcloud.com/server/releases/latest-18.tar.bz2 -P /config

 

Reason for this is that you can't skip major versions (i.e. if your Nextcloud instance is on version 17.x, you must first upgrade to version 18.x).

 

Hope it helps.

Link to post
On 10/23/2020 at 3:29 PM, skois said:

After looking for almost a month how to install Face Recognition App on Nextcloud. I had found the install instructions but never was able to complete them. Because apt install wasn't working. But i was too stupid and today realised it was alpine underneath. So.. googled what package manager alpine uses and managed to get Face Rec working (ill have some results in some hours!). 

For anyone wanna install pdlib and try the Face Rec app, here is what i did to install it.

First, DO IT ON TESTING DOCKER NOT ON THE PRODUCTION DOCKER! 

Have some photos on your nextcloud (not on external storages, it won't work, been there)

Now the installation.
1 - Go to Dockers, Open console on your test nextcloud docker

Insert the following commands one line at a time.

Hopefully you won't have any errors.


apk add make cmake gcc g++ php7-dev libx11-dev openblas-dev

**RESTART DOCKER AFTER THE PREVIOUS LINE, open console on docker again and continue**

git clone https://github.com/davisking/dlib.git
cd dlib/dlib
mkdir build
cd build
cmake -DBUILD_SHARED_LIBS=ON ..
make
sudo make install

cd / 

git clone https://github.com/goodspb/pdlib.git
cd pdlib
phpize
PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig ./configure
make
sudo make install

* Now to go appdata folder /php/phplocal.ini and add on the end

 

[pdlib]
extension="pdlib.so"
 


2 - Restart NC Docker once again.

3 - Go to Apps and install/enable Face Recognition App
4 - Go to NC Docker console again and do "occ face:setup -m 1"

5 - Go to Settings > Face Recognition (on the lower menu)

6 - I don't know if its supposed to start automatically, mine was saying Analysis started but didn't seem to process any photo until i open the docker console again and do "occ face:background_job" EDIT* This command justs forces to start, if you want you can let it start automaticly via cron job
7 - Wait for results ( i'm also waiting. so i can't really tell you how it works yet)

*For more info for fine tuning check here https://github.com/matiasdelellis/facerecognition/wiki/Usage

*This is all info gathered around, so I can't be sure that i haven't messed any other module of NC while installing those packages. 
DO IT AT YOUR OWN RISK!

PS. As you can see i'm just good at googling! Not an expert. Hehe
 

Thank you soooo much! This is working for me, but I noticed anytime I apply a change to the docker it removes pdlib. Anyway to get this to retain? 

Link to post
Thank you soooo much! This is working for me, but I noticed anytime I apply a change to the docker it removes pdlib. Anyway to get this to retain? 
Only if you fork the lsio docker container and create an image that includes it already..

Sent from my Mi 10 Pro using Tapatalk

Link to post
1 hour ago, Kalembang said:

Thank you soooo much! This is working for me, but I noticed anytime I apply a change to the docker it removes pdlib. Anyway to get this to retain? 

You can make a folder called "custom-cont-init.d" in the /config folder location and put a script in there.

It gets executed during start/restart of the container.
This applies to Linuxserver containers only, that I know of.
Read more here, under "Custom Scripts".

  • Like 1
  • Thanks 1
Link to post
On 1/18/2021 at 12:55 PM, REllU said:

Hello everyone, I hope I'm doing this in the right place.

 

My issue is, that when I'm trying to set up OnlyOffice within Nextcloud, I'm getting:

Error when trying to connect (cURL error 7: Failed to connect to xxx.xxx.xx port 8443: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html))"

 

I've set up a cname for onlyoffice through cpanel, and connecting to onlyoffice directly from the web gives me a "Document server is running" message.

However, if I try to connect within the same network as the UnRaid server is in, I get an error. My guess is, that this is the reason why I can't connect to OnlyOffice through NextCloud? (NextCloud in itself doesn't work on the same network either, as my modem doesn't support hairpin / vlan unfortunately)

 

Trying to setup the demo Document Server everything works just fine. But obviously, this is not what I'm after.

 

I'm using SWAG (nginx) to reverse-proxy both NextCloud as well as the OnlyOffice docker, and like I've stated, both work nicely from outside of the network.

 

I've created a custom network within Unraid for all of these apps, so that they'd be able to talk with each other.

As for how I tried to setup the OnlyOffice, I followed Spaceinvader one's tutorial video. Before that, I tried to install Collabora with no luck (not getting any specific errors, but I'm suspecting the issue was the same) before giving up on that, and moving to OnlyOffice.

 

I haven't tested the Community Document Server directly from Nextcloud, but based on the reviews and things I've read online, I'm not too convinced I should even try that.

 

As for UnRaid, I only have OnlyOffice (named as "documentserver"), mariadb, nextcloud, and swag installed as dockers. (This server will be used as file server, Google Drive replacement, if you will, for our company)

I'm really new to servers, and networking in general (which you'll probably be able to tell), so there's a chance I've setup something very obvious incorrectly, but my knowledge of all this just seems to be not enough.

I'd really appreciate any help for this.

 

 

I think I got myself even more stuck now.

We replaced our modem today for a newer one, got everything set up for it, and everything seems to be working as usual. NextCloud can be accessed outside of the network, and so can OnlyOffice.

However, now I'm greeted with "Error when trying to connect (Bad healthcheck status)" within NextCloud when trying to save the settings of OnlyOffice.

Again, the demo server of OO works just fine.

I've tried to replace SWAG with NGinxProxyManager, I've copied the cert files (and tried without copying them), I've replaced the OnlyOffice docker from chvb's to the one from Siwat2545, but the only thing that changed from all this, is that now I'm no longer getting the green check mark when accessing onlyoffice.mydomain, but instead I'm getting the "welcome" screen of OnlyOffice. (Without copying the cert files, I get 502 Bad Gateway)

I know I'm in deep waters here (for me), so I'd be more than happy to compensate any help with some donations (if that's allowed here)

I'd really appreciate any help, or even just someone telling me that it doesn't work right now so I could stop banging my head against the wall.

Link to post
5 minutes ago, REllU said:

 

 

I think I got myself even more stuck now.

We replaced our modem today for a newer one, got everything set up for it, and everything seems to be working as usual. NextCloud can be accessed outside of the network, and so can OnlyOffice.

However, now I'm greeted with "Error when trying to connect (Bad healthcheck status)" within NextCloud when trying to save the settings of OnlyOffice.

Again, the demo server of OO works just fine.

I've tried to replace SWAG with NGinxProxyManager, I've copied the cert files (and tried without copying them), I've replaced the OnlyOffice docker from chvb's to the one from Siwat2545, but the only thing that changed from all this, is that now I'm no longer getting the green check mark when accessing onlyoffice.mydomain, but instead I'm getting the "welcome" screen of OnlyOffice. (Without copying the cert files, I get 502 Bad Gateway)

I know I'm in deep waters here (for me), so I'd be more than happy to compensate any help with some donations (if that's allowed here)

I'd really appreciate any help, or even just someone telling me that it doesn't work right now so I could stop banging my head against the wall.

I don't have OO right now, i use collabora which works fine. 
The crazy thing is before 10 minutes i was casually checking my logs. And saw this errors
 

Error	internet_connection_check	GuzzleHttp\Exception\RequestException: cURL error 56: Recv failure: Connection reset by peer (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)		2021-01-19T18:23:34+0200
Error	internet_connection_check	GuzzleHttp\Exception\RequestException: cURL error 56: Recv failure: Connection reset by peer (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)		2021-01-19T18:07:57+0200

But collabora still working fine. 
I haven't checked what this is yet. 

You see the bad healthcheck status on NC? Does it have any other info there?

Link to post
1 minute ago, skois said:

I don't have OO right now, i use collabora which works fine. 
The crazy thing is before 10 minutes i was casually checking my logs. And saw this errors
 


Error	internet_connection_check	GuzzleHttp\Exception\RequestException: cURL error 56: Recv failure: Connection reset by peer (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)		2021-01-19T18:23:34+0200
Error	internet_connection_check	GuzzleHttp\Exception\RequestException: cURL error 56: Recv failure: Connection reset by peer (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)		2021-01-19T18:07:57+0200

But collabora still working fine. 
I haven't checked what this is yet. 

You see the bad healthcheck status on NC? Does it have any other info there?

 

Hey there!

 

Yes, the healthcheck is indeed showing within NextCloud.

From NC's own logs, the opened up error is:

 

	Exception: Bad healthcheck status

    /config/www/nextcloud/apps/onlyoffice/controller/settingscontroller.php - line 168:

    OCA\Onlyoffice\DocumentService->checkDocServiceUrl(OC\URLGenerator {}, OCA\Onlyoffice\Crypt {})

    /config/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 169:

    OCA\Onlyoffice\Controller\SettingsController->SaveAddress("https://doc ... /", "", "", true, "", false)

    /config/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 100:

    OC\AppFramework\Http\Dispatcher->executeController(OCA\Onlyoffi ... {}, "saveAddress")

    /config/www/nextcloud/lib/private/AppFramework/App.php - line 152:

    OC\AppFramework\Http\Dispatcher->dispatch(OCA\Onlyoffi ... {}, "saveAddress")

    /config/www/nextcloud/lib/private/Route/Router.php - line 309:

    OC\AppFramework\App::main("SettingsController", "saveAddress", OC\AppFramew ... {}, { _route: "o ... "})

    /config/www/nextcloud/lib/base.php - line 1008:

    OC\Route\Router->match("/apps/onlyo ... s")

    /config/www/nextcloud/index.php - line 37:

    OC::handleRequest()



Should've put that into the original post, sorry >.>

Link to post
1 minute ago, REllU said:

 

Hey there!

 

Yes, the healthcheck is indeed showing within NextCloud.

From NC's own logs, the opened up error is:

 


	Exception: Bad healthcheck status

    /config/www/nextcloud/apps/onlyoffice/controller/settingscontroller.php - line 168:

    OCA\Onlyoffice\DocumentService->checkDocServiceUrl(OC\URLGenerator {}, OCA\Onlyoffice\Crypt {})

    /config/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 169:

    OCA\Onlyoffice\Controller\SettingsController->SaveAddress("https://doc ... /", "", "", true, "", false)

    /config/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 100:

    OC\AppFramework\Http\Dispatcher->executeController(OCA\Onlyoffi ... {}, "saveAddress")

    /config/www/nextcloud/lib/private/AppFramework/App.php - line 152:

    OC\AppFramework\Http\Dispatcher->dispatch(OCA\Onlyoffi ... {}, "saveAddress")

    /config/www/nextcloud/lib/private/Route/Router.php - line 309:

    OC\AppFramework\App::main("SettingsController", "saveAddress", OC\AppFramew ... {}, { _route: "o ... "})

    /config/www/nextcloud/lib/base.php - line 1008:

    OC\Route\Router->match("/apps/onlyo ... s")

    /config/www/nextcloud/index.php - line 37:

    OC::handleRequest()



Should've put that into the original post, sorry >.>

 

4 minutes ago, REllU said:

 

Hey there!

 

Yes, the healthcheck is indeed showing within NextCloud.

From NC's own logs, the opened up error is:

 


	Exception: Bad healthcheck status

    /config/www/nextcloud/apps/onlyoffice/controller/settingscontroller.php - line 168:

    OCA\Onlyoffice\DocumentService->checkDocServiceUrl(OC\URLGenerator {}, OCA\Onlyoffice\Crypt {})

    /config/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 169:

    OCA\Onlyoffice\Controller\SettingsController->SaveAddress("https://doc ... /", "", "", true, "", false)

    /config/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 100:

    OC\AppFramework\Http\Dispatcher->executeController(OCA\Onlyoffi ... {}, "saveAddress")

    /config/www/nextcloud/lib/private/AppFramework/App.php - line 152:

    OC\AppFramework\Http\Dispatcher->dispatch(OCA\Onlyoffi ... {}, "saveAddress")

    /config/www/nextcloud/lib/private/Route/Router.php - line 309:

    OC\AppFramework\App::main("SettingsController", "saveAddress", OC\AppFramew ... {}, { _route: "o ... "})

    /config/www/nextcloud/lib/base.php - line 1008:

    OC\Route\Router->match("/apps/onlyo ... s")

    /config/www/nextcloud/index.php - line 37:

    OC::handleRequest()



Should've put that into the original post, sorry >.>

I won't pretend i can understand any of the logs (i'm not so deep yet lol) 
Please post config.php of nextcloud (/mnt/user/appdata/nextcloud/www/nextcloud/config/config.php)
photos of the docker templates (OO and NC) 
swag configs for OO and NC
and if OO has any config file. this too.
I'll try to see if there is anything obvious that i can catch, otherwise someone here with better knowledge will help with all this info.

Just to recap. 
You can access onlyoffice.domain.com and nextcloud.domain.com (not those exactly but your cnames and domain) right?

Also you can open nextcloud console (right click on docker while you are in dashboard) and try "ping onlyoffice.domain.com" 
If it can ping it, swag confs and cnames should be fine. 
 

Link to post

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.