[Support] Linuxserver.io - Nextcloud


4935 posts in this topic Last Reply

Recommended Posts

  • Replies 4.9k
  • 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

Hey thanks for getting back so quick. So i tried this but it didnt work. I copied and pasted that into ngnix proxy manager and then went to the advanced tab and pasted it there but still no luck 
I think in nginx proxy manager, on the advan Ed tab you need to wrap everything in
Location /{ everything here }

Sent from my Mi 10 Pro using Tapatalk

Link to post
On 5/9/2021 at 7:24 PM, skois said:

I think in nginx proxy manager, on the advan Ed tab you need to wrap everything in
Location /{ everything here }

Sent from my Mi 10 Pro using Tapatalk
 

so here is what i found out today. i can upload to my smb shares no issues with a file that is 1gb. but as soon as i try to download from the same smb share it shows network error. 

Link to post

Hi,

 

i enabled the External Storage plugin to access a unraid share via webdav. It works fine and I can access the folder via the nextcloud gui. But how do I find out the webdav url?   remote.php/dav/files/ ???

Link to post

Hello, I have LSIO Nextcloud Container installed on my Unraid 6.9.2.  I want my PhotoPrism Docker containers to be able to make INTERNAL HTTP calls across my local Docker network to the Nextcloud container's WebDav endpoint.

 

Currently the NextCloud and PhotoPrism docker containers can see/ping/curl each other internally, but all requests to unsecure http://<nextcloud_docker_container>/remote.php/dav/files/user/ is getting redirected to secure https://<nextcloud_docker_container>/remote.php/dav/files/user/ by Nextcloud Nginx config I think.

 

How do I allow LSIO Nextcloud container to receive unsecure HTTP requests from other internal docker containers?

Link to post
47 minutes ago, clusterbox said:

Hello, I have LSIO Nextcloud Container installed on my Unraid 6.9.2.  I want my PhotoPrism Docker containers to be able to make INTERNAL HTTP calls across my local Docker network to the Nextcloud container's WebDav endpoint.

 

Currently the NextCloud and PhotoPrism docker containers can see/ping/curl each other internally, but all requests to unsecure http://<nextcloud_docker_container>/remote.php/dav/files/user/ is getting redirected to secure https://<nextcloud_docker_container>/remote.php/dav/files/user/ by Nextcloud Nginx config I think.

 

How do I allow LSIO Nextcloud container to receive unsecure HTTP requests from other internal docker containers?

 

Looks like I resolved my own issue by cloning the Nginx 443 block to the 80 block.  I did not expose port 80 to the internet but now it allows me to make insecure HTTP calls internally between my docker containers.

Link to post

Hello all,

I've been using nextcloud and absolutely love it!

Recently I have been forced to switch router to one that doesn't  support hairpinning / loopback. As a result I cannot access my nextcloud server from within my LAN. I followed spaceinvader's video tutorial on setting up nextcloud and reverse proxy via let's encrypt and duckdns.

When I hit up the nextcloud ip my.local.ip:444, I get rerouted to my unraid server ui. Is there a way to make nextcloud accept local connections?

If this has been mentioned before, excuse my question and point me in the right direction

 

thank you for you time!

Link to post
3 hours ago, avpap said:

Hello all,

I've been using nextcloud and absolutely love it!

Recently I have been forced to switch router to one that doesn't  support hairpinning / loopback. As a result I cannot access my nextcloud server from within my LAN. I followed spaceinvader's video tutorial on setting up nextcloud and reverse proxy via let's encrypt and duckdns.

When I hit up the nextcloud ip my.local.ip:444, I get rerouted to my unraid server ui. Is there a way to make nextcloud accept local connections?

If this has been mentioned before, excuse my question and point me in the right direction

 

thank you for you time!

One solution would be to edit your hosts file in each computer in home

Link to post

Hello, 

I am missing something.... I've installed the container and set up everything , right now I can access the webGUI but it feels kinda slow. Then I go to the desktop app and check the speed and a LAN sync is going at around 400 Kbps...

 

What could I do? I've tried to modify my www2.conf parameters (the pm. stuff), changed the http2 flags in Nginx Proxy Manager. I have no custom config in the NPM.

 

 

Link to post
On 5/13/2021 at 1:19 PM, skois said:

One solution would be to edit your hosts file in each computer in home

I added the line

 

192.168.2.11 mynextcloudserver.duckdns.org

 

when I hit up 192.168.2.11 from my browser, nothing happens. Is there something wrong with my syntax? I opened the file with notepad as administrator and then saved it. I ran on the command prompt ipconig /flushdns and restarted my pc. Nothing.

what am I doing wrong?

Link to post
Posted (edited)

Hi guys,

 

running Unraid and Nextcloud now for one year and it has become an important tool for my so I don't wanna drop it.

 

But now I can't get nextcloud to work. I'm using the nextcloud-Docker-Container from linuxserver with the SWAG-Container as Reverse Proxy and DuckDNS.

 

In the log of the nextcloud-Container I found the following errors:

 

Brought to you by linuxserver.io
-------------------------------------

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid: 99
User gid: 100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
chown: cannot read directory '/config/www/nextcloud/core': I/O error
chmod: cannot read directory '/config/www/nextcloud/core': I/O error
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 40-config: executing...
[cont-init.d] 40-config: exited 0.
[cont-init.d] 50-install: executing...
[cont-init.d] 50-install: exited 0.
[cont-init.d] 60-memcache: executing...
[cont-init.d] 60-memcache: exited 0.
[cont-init.d] 70-aliases: executing...
[cont-init.d] 70-aliases: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.

 

 

So  I did check the core on the nextcloud console with the command "occ integrity:check-core" with this result (just the last few lines, because the list is very long):

 

- current:
    - core/vendor/zxcvbn/dist/zxcvbn.js:
      - expected: 4d994c18563dc4a8f7f2dff99b617327e44cfda0f96a53070dedbaa7499850ca021791bb89b7c751020bab4a903d5df096c9c2c0bf933d134ae2f21618b3a451
      - current:
    - core/webpack.test.js:
      - expected: 9e4bb245226e24e15239416bf8fa8544bfd5b0e75e7054a15c41b834479dae9b256a511d0d4721da0b5824d4776090f0f138c73f37e123d7933d723622a10fdb
      - current:
root@85de9c98265e:/#

 

Then I stopped the container and set new permissions to the nextcloud share via the Unraid Menu.

 

I guess, the problem is, that when nextcloud tries to change user and persmissions to www-data as the webserver user the I/O-erros happens...

 

The log of the SWAG-Container has no errors in it and states the server ready.

 

Anyone a glue how to fix this...

Edited by unrno.spam
Link to post
14 minutes ago, unrno.spam said:

Hi guys,

 

running Unraid and Nextcloud now for one year and it has become an important tool for my so I don't wanna drop it.

 

But now I can't get nextcloud to work. I'm using the nextcloud-Docker-Container from linuxserver with the SWAG-Container as Reverse Proxy and DuckDNS.

 

In the log of the nextcloud-Container I found the following errors:

 


Brought to you by linuxserver.io
-------------------------------------

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid: 99
User gid: 100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
chown: cannot read directory '/config/www/nextcloud/core': I/O error
chmod: cannot read directory '/config/www/nextcloud/core': I/O error
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 40-config: executing...
[cont-init.d] 40-config: exited 0.
[cont-init.d] 50-install: executing...
[cont-init.d] 50-install: exited 0.
[cont-init.d] 60-memcache: executing...
[cont-init.d] 60-memcache: exited 0.
[cont-init.d] 70-aliases: executing...
[cont-init.d] 70-aliases: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.

 

 

So  I did check the core on the nextcloud console with the command "occ integrity:check-core" with this result (just the last few lines, because the list is very long):

 


- current:
    - core/vendor/zxcvbn/dist/zxcvbn.js:
      - expected: 4d994c18563dc4a8f7f2dff99b617327e44cfda0f96a53070dedbaa7499850ca021791bb89b7c751020bab4a903d5df096c9c2c0bf933d134ae2f21618b3a451
      - current:
    - core/webpack.test.js:
      - expected: 9e4bb245226e24e15239416bf8fa8544bfd5b0e75e7054a15c41b834479dae9b256a511d0d4721da0b5824d4776090f0f138c73f37e123d7933d723622a10fdb
      - current:
root@85de9c98265e:/#

 

Then I stopped the container and set new permissions to the nextcloud share via the Unraid Menu.

 

I guess, the problem is, that when nextcloud tries to change user and persmissions to www-data as the webserver user the I/O-erros happens...

 

The log of the SWAG-Container has no errors in it and states the server ready.

 

Anyone a glue how to fix this...

There is no www-data user in our container.

The I/O error is most likely something wrong with your disk/controller and not an issue in the container. So check the drive and filesystem for errors. Of you find errors, you should open a new thread in the general forum the get help as it's not container related.

Link to post
Posted (edited)

Having an interesting one, so i have the docker installed and all is working fine with the connectivity in Bridge mode (running on port 444). This is then forwarded with NGINX to nextcloud.mydomain.com on port 443

 

With the exception that all traffic goes out to the internet and back in again.  EG setting up a laptop/mobile where I want the connection to be to nextcloud.mydomain.com so that it works outside of the LAN the uploads goes out the internet and back in again, this isnt ideal for speed or bandwidth usage.

 

I tried setting up a DNS entry to point nextcloud.mydomain.com to the unraid server internal IP, but that fails due to the port mismatch (apps configured to use 443, service running on 444, and 443 being the unraid console).

 

I have tried reconfiguring the docker to use a custom network so it has its own IP  and can run fully on 443 with no port mapping but that doesnt seem to work (the next cloud service just fails with an internal server error.

 

Am I over complicating this?

 

Edited by tris203
Link to post
24 minutes ago, tris203 said:

Having an interesting one, so i have the docker installed and all is working fine with the connectivity in Bridge mode (running on port 444). This is then forwarded with NGINX to nextcloud.mydomain.com on port 443

 

With the exception that all traffic goes out to the internet and back in again.  EG setting up a laptop/mobile where I want the connection to be to nextcloud.mydomain.com so that it works outside of the LAN the uploads goes out the internet and back in again, this isnt ideal for speed or bandwidth usage.

 

I tried setting up a DNS entry to point nextcloud.mydomain.com to the unraid server internal IP, but that fails due to the port mismatch (apps configured to use 443, service running on 444, and 443 being the unraid console).

 

I have tried reconfiguring the docker to use a custom network so it has its own IP  and can run fully on 443 with no port mapping but that doesnt seem to work (the next cloud service just fails with an internal server error.

 

Am I over complicating this?

 

I fixed it for anybody wondering. The issue (stupid me) was that the docker config was set to not enable access to host networks for containers.

So by enabling this, that allowed me to run the docker on its own IP on the genuine port 443

Then i could add a internal dns entry for nextcloud.mydomain.com to point internally to the internal IP

 

There is currently a certificate error, but I think that can be fixed fairly easily

Link to post
15 hours ago, tris203 said:

I fixed it for anybody wondering. The issue (stupid me) was that the docker config was set to not enable access to host networks for containers.

So by enabling this, that allowed me to run the docker on its own IP on the genuine port 443

Then i could add a internal dns entry for nextcloud.mydomain.com to point internally to the internal IP

 

There is currently a certificate error, but I think that can be fixed fairly easily

No, the traffic doesn't go out and in again. Your router is doing hairpin nat. There is no reason to set it to host network mode.

Link to post

I am also having issues as of late as identifed by the File Activity tool, where Nextcloud is accessing an /appdata_{instanceId} directory and /files_encryption directory under /mnt/diskX/Nextcloud. This is causing a few of my disks to remain spun up. This did not use to be an issue.

I use Nextcloud as a target for Backup, so I cannot change the share to use the cache. The Container is correctly configured using /data => /mnt/user/Nextcloud and /config => /mnt/user/appdata/nextcloud

Link to post
10 minutes ago, Progeny42 said:

I am also having issues as of late as identifed by the File Activity tool, where Nextcloud is accessing an /appdata_{instanceId} directory and /files_encryption directory under /mnt/diskX/Nextcloud. This is causing a few of my disks to remain spun up. This did not use to be an issue.

I use Nextcloud as a target for Backup, so I cannot change the share to use the cache. The Container is correctly configured using /data => /mnt/user/Nextcloud and /config => /mnt/user/appdata/nextcloud

This does not seem to be a container issue anyway. Better to seek help in nextcloud forums

 

Link to post
Quote

Hi guys,

 

running Unraid and Nextcloud now for one year and it has become an important tool for my so I don't wanna drop it.

 

But now I can't get nextcloud to work. I'm using the nextcloud-Docker-Container from linuxserver with the SWAG-Container as Reverse Proxy and DuckDNS.

 

Today I replaced my Cache SSD since there were some uncorrectable blocks.

 

I deleted the docker image and re-installed all containers via the previous apps.

 

With my nextcloud conainer I'm facing now a strange behaviour. When I try to log in via Web-Ui I get an error message:

 

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.

 

But all nextcloud apps (Android and iOS) have full access and I can up- and download files. Synchronising calender and tasks is no problem at all. So nextcloud itaself with swag reverse-proxy and DuchDNS is working. Hence my guess is, that the web-login is broken and this was actually one of the last things I did in nextcloud - changing the Theme (without new grafix, just the displayed text was changed)

 

In the nextcloud.log I found hints to that:

 

Agent":"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0","version":"21.0.1.1"}
{"reqId":"OiW0ysdcsI9jtOXDRA5v","level":3,"time":"2021-05-19T06:29:53+00:00","remoteAddr":"207.180.213.38","user":"--","app":"core","method":"GET","url":"/login","message":{"Exception":"RuntimeException","Message":"image not found: image:favicon-mask.svg webroot: serverroot:/config/www/nextcloud","Code":0,"Trace":[{"file":"/config/www/nextcloud/lib/private/legacy/template/functions.php","line":238,"function":"imagePath","class":"OC\\URLGenerator","type":"->"},{"file":"/config/www/nextcloud/core/templates/layout.guest.php","line":20,"function":"image_path"},{"file":"/config/www/nextcloud/lib/private/Template/Base.php","line":178,"args":["/config/www/nextcloud/core/templates/layout.guest.php"],"function":"include"},{"file":"/config/www/nextcloud/lib/private/Template/Base.php","line":150,"function":"load","class":"OC\\Template\\Base","type":"->"},{"file":"/config/www/nextcloud/lib/private/legacy/OC_Template.php","line":180,"function":"fetchPage","class":"OC\\Template\\Base","type":"->"},{"file":"/config/www/nextcloud/lib/private/legacy/OC_Template.php","line":211,"function":"fetchPage","class":"OC_Template","type":"->"},{"file":"/config/www/nextcloud/lib/private/Template/Base.php","line":132,"function":"fetchPage","class":"OC_Template","type":"->"},{"file":"/config/www/nextcloud/lib/private/legacy/OC_Template.php","line":332,"function":"printPage","class":"OC\\Template\\Base","type":"->"},{"file":"/config/www/nextcloud/index.php","line":63,"function":"printExceptionErrorPage","class":"OC_Template","type":"::"}],"File":"/config/www/nextcloud/lib/private/URLGenerator.php","Line":238,"CustomMessage":"--"},"userAgent":"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0","version":"21.0.1.1"}
{"reqId":"Y5d1alsQkKVxzjJqTzUt","level":3,"time":"2021-05-19T09:19:34+00:00","remoteAddr":"ipxxx","user":"userxxx","app":"no app in context","method":"GET","url":"/ocs/v2.php/cloud/capabilities?format=json","message":{"Exception":"RuntimeException","Message":"image not found: image:logo/logo.svg webroot: serverroot:/config/www/nextcloud","Code":0,"Trace":[{"file":"/config/www/nextcloud/apps/theming/lib/ThemingDefaults.php","line":249,"function":"imagePath","class":"OC\\URLGenerator","type":"->"},{"file":"/config/www/nextcloud/apps/theming/lib/Capabilities.php","line":84,"function":"getLogo","class":"OCA\\Theming\\ThemingDefaults","type":"->"},{"file":"/config/www/nextcloud/lib/private/CapabilitiesManager.php","line":72,"function":"getCapabilities","class":"OCA\\Theming\\Capabilities","type":"->"},{"file":"/config/www/nextcloud/core/Controller/OCSController.php","line":107,"function":"getCapabilities","class":"OC\\CapabilitiesManager","type":"->"},{"file":"/config/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php","line":218,"function":"getCapabilities","class":"OC\\Core\\Controller\\OCSController","type":"->"},{"file":"/config/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php","line":127,"function":"executeController","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->"},{"file":"/config/www/nextcloud/lib/private/AppFramework/App.php","line":157,"function":"dispatch","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->"},{"file":"/config/www/nextcloud/lib/private/Route/Router.php","line":302,"function":"main","class":"OC\\AppFramework\\App","type":"::"},{"file":"/config/www/nextcloud/ocs/v1.php","line":63,"function":"match","class":"OC\\Route\\Router","type":"->"},{"file":"/config/www/nextcloud/ocs/v2.php","line":24,"args":["/config/www/nextcloud/ocs/v1.php"],"function":"require_once"}],"File":"/config/www/nextcloud/lib/private/URLGenerator.php","Line":238,"CustomMessage":"--"},"userAgent":"Mozilla/5.0 (Android) Nextcloud-android/3.15.1","version":"21.0.1.1"}
{"reqId":"yaRjpicZEQDPcXcfmEH2","level":3,"time":"2021-05-19T09:19:59+00:00","remoteAddr":"ipxxx","user":"userxxx","app":"PHP","method":"GET","url":"/index.php/apps/files/api/v1/thumbnail/256/256/SofortUpload/Camera/20210518_220152.jpg","message":"Allowed memory size of 536870912 bytes exhausted (tried to allocate 28672 bytes) at /config/www/nextcloud/lib/private/legacy/OC_Image.php#512","userAgent":"Mozilla/5.0 (Android) Nextcloud-android/3.15.1","version":"21.0.1.1"}
{"reqId":"yudw2flsHb9Ea7YQwfKH","level":3,"time":"2021-05-19T09:20:22+00:00","remoteAddr":"ipxxx","user":"userxxx","app":"no app in context","method":"GET","url":"/ocs/v2.php/cloud/capabilities?format=json","message":{"Exception":"RuntimeException","Message":"image not found: image:logo/logo.svg webroot: serverroot:/config/www/nextcloud","Code":0,"Trace":[{"file":"/config/www/nextcloud/apps/theming/lib/ThemingDefaults.php","line":249,"function":"imagePath","class":"OC\\URLGenerator","type":"->"},{"file":"/config/www/nextcloud/apps/theming/lib/Capabilities.php","line":84,"function":"getLogo","class":"OCA\\Theming\\ThemingDefaults","type":"->"},{"file":"/config/www/nextcloud/lib/private/CapabilitiesManager.php","line":72,"function":"getCapabilities","class":"OCA\\Theming\\Capabilities","type":"->"},{"file":"/config/www/nextcloud/core/Controller/OCSController.php","line":107,"function":"getCapabilities","class":"OC\\CapabilitiesManager","type":"->"},{"file":"/config/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php","line":218,"function":"getCapabilities","class":"OC\\Core\\Controller\\OCSController","type":"->"},{"file":"/config/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php","line":127,"function":"executeController","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->"},{"file":"/config/www/nextcloud/lib/private/AppFramework/App.php","line":157,"function":"dispatch","class":"OC\\AppFramework\\Http\\Dispatcher","type":"->"},{"file":"/config/www/nextcloud/lib/private/Route/Router.php","line":302,"function":"main","class":"OC\\AppFramework\\App","type":"::"},{"file":"/config/www/nextcloud/ocs/v1.php","line":63,"function":"match","class":"OC\\Route\\Router","type":"->"},{"file":"/config/www/nextcloud/ocs/v2.php","line":24,"args":["/config/www/nextcloud/ocs/v1.php"],"function":"require_once"}],"File":"/config/www/nextcloud/lib/private/URLGenerator.php","Line":238,"CustomMessage":"--"},"userAgent":"Mozilla/5.0 (Android) Nextcloud-android/3.15.1","version":"21.0.1.1"}

 

Am I guessing right and how can I fix that?

Link to post

Nextcloud icon when you create a share in windows client.

 

When you create a share with the client, it changes the icon to the nextcloud logo.  Is there a way to leave the default icon unchanged? eg the folder icon remains a standard folder icon.

 

Link to post

I was updating my Nextcloud docker today.  The update failed a couple times.  I retried a few times but it seems to have locked up.  When I go to the gui it says its in maintenance mode.   Do I have to reinstall the docker from scratch now?  I assume delete docker and appdata directory and reinstall?

Link to post
4 minutes ago, Gragorg said:

I was updating my Nextcloud docker today.  The update failed a couple times.  I retried a few times but it seems to have locked up.  When I go to the gui it says its in maintenance mode.   Do I have to reinstall the docker from scratch now?  I assume delete docker and appdata directory and reinstall?

I presume you are talking about updating nextcloud itself vs updating the docker in unraid.

I'm also going to guess you are going to v21 from 20

In unraid open a console from the nextcloud icon

Then run these commands one at a time.

sudo -u abc php /config/www/nextcloud/occ db:add-missing-indices
sudo -u abc php /config/www/nextcloud/occ db:convert-filecache-bigint

sudo -u abc php /config/www/nextcloud/occ db:add-missing-columns
sudo -u abc php /config/www/nextcloud/occ db:add-missing-primary-keys

 

Then

sudo -u abc php /config/www/nextcloud/occ maintenance:repair

then

sudo -u abc php /config/www/nextcloud/occ upgrade

then

sudo -u abc php /config/www/nextcloud/occ maintenance:repair

(again for good measure)

Then turn maintenance mode off

sudo -u abc php /config/www/nextcloud/occ maintenance:mode --off

Then see if you can get back to the logon screen

 

Link to post
26 minutes ago, Gragorg said:

I was updating my Nextcloud docker today.  The update failed a couple times.  I retried a few times but it seems to have locked up.  When I go to the gui it says its in maintenance mode.   Do I have to reinstall the docker from scratch now?  I assume delete docker and appdata directory and reinstall?

More on upgrading via the gui.

Start the upgrade.

For me, it usually times out during the backup process.

Back arrow button the browser to the settings screen.

The backup process is still happening. Wait for a bit, the press update again.

When ready, it should resume at the download step.

The same may happen again for download so go back and wait.

It will most likely go to almost the last step now.

Don't go back after it enters maintenance mode.

if you do, you will be going to the console to get it back.

If it times out on the last step, just wait a bit then retry.

When it is ready you should be able to proceed.

Link to post
Posted (edited)

Hello I am just starting using nextcloud and if there is any more information I should provide let me know.

 

I have been trying to setup nextcloud on UNRAID with a mariadb dabase and it was working fine with 21.0.1 but when I upgraded to 21.0.2 or even did a complete clean install there was some problems with the demo PDFs. I can include my own and they seem to work but I just don’t understand what to make of it.

 

Also when installing(fresh or upgrade) 21.0.2 I get an error on page below

https://index.php/core/apps/recommended

 

and it does not redirect me to the dashboard as it did in 21.0.1 when installing. Nextcloud seems to work but just have to manually navigate to it.

 

I have attached a picture of the error on the index page after install and how it displays the demo-PDFs.

 

 

Any input is very welcome and if you know some material that might be useful please let me know.

 

EDIT.

It seems to be an error with the current version(21.0.2)
- https://github.com/nextcloud/files_pdfviewer/issues/381

 

nextcloud_index_error.png

nextcloud_pdf_error.png

Edited by JustAnotherGuy1324
spelling
Link to post
3 hours ago, Jessie said:

More on upgrading via the gui.

Start the upgrade.

For me, it usually times out during the backup process.

Back arrow button the browser to the settings screen.

The backup process is still happening. Wait for a bit, the press update again.

When ready, it should resume at the download step.

The same may happen again for download so go back and wait.

It will most likely go to almost the last step now.

Don't go back after it enters maintenance mode.

if you do, you will be going to the console to get it back.

If it times out on the last step, just wait a bit then retry.

When it is ready you should be able to proceed.

Thanks @Jessie  your console commands fixed everything and updated to the latest version.  Do you normally update from the console or the gui?

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.