[Support] Linuxserver.io - Nextcloud


4483 posts in this topic Last Reply

Recommended Posts

1 hour ago, jonasdegent said:

I did change that. I can't access it when I'm on my own network, even with the DNS. If I go outside my network, for example my phone on 4G, it works.

I read it as you used the IP locally. Your new router most likely doesn't support NAT hairpin or split DNS. That's what makes the domain work locally also.

Link to post
  • Replies 4.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

Thanks, fixed for me as well, and I also added this line add_header Referrer-Policy no-referrer always; to appdata/nextcloud/nginx/site-confs/default   And now I have a green

Posted Images

On 2/17/2021 at 9:23 PM, GGabs said:

Thank you so much. So I tried to set this docker with nextcloud and this is the error i see in the onlyoffice docker logs:

 

[2021-02-18T01:55:51.651] [ERROR] nodeJS - error downloadFile:url=https://nextcloud_local_IP:PORT/apps/onlyoffice/empty?doc=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJhY3Rpb24iOiJlbXB0eSJ9.k_tE7DNfNBVA9l62Ze27ISHoDOKGNGNThmrL1TZ-Ex0;attempt=3;code:DEPTH_ZERO_SELF_SIGNED_CERT;connect:null;(id=conv_check_1265043125_docx)
Error: self signed certificate

NOTE: I have removed my local nextcloud IP and port from above error

----------------------------------------------------------------

AND - I see this error in nextcloud when I click on "save" button after entering my document editing service address:

Error when trying to connect (Error occurred in the document service: Error while downloading the document file to be converted.) (version 5.4.2.46)

 

----------------------------------------------------------------

- I see no errors in nextcloud logs

 

is there a workaround or fix for this, seems like something to do with the cert?

 

- I am able to open up onlyoffice docker internally and externally with my domain url no issues using https. and page shows document server is running.

- I am using SWAG, i basically copied the key and crt files from SWAG/keys/ directory to onlyoffice/DocumentServer/data/certs/onlyoffice.crt onlyoffice.key

- I have renamed the onlyoffice docker to documentserver

- in SWAG changed the onlyoffice proxy confg file to the following:

# only office doc server


server {
    listen 443 ssl;

    server_name subdomain.*;   < --removed my actual subdomain

    include /config/nginx/ssl.conf;

    client_max_body_size 0;


    location / {
                include /config/nginx/proxy.conf;
                resolver 127.0.0.11 valid=30s;
                set $upstream_docs documentserver;
                proxy_pass https://$upstream_docs:443;
                proxy_redirect off;
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Host $server_name;
                proxy_set_header X-Forwarded-Proto $scheme;
        }
}

 

could someone please look at the details above and able to help me out. Please let me know if any other information is required.

I hope in near future there can be a simpler way to integrate these 2 together.

 

any opinions?

 

Also i have done in the docker console for onlyoffice wget command and oo docker can connect to nc.domain.com fine it seems, output bellow:

# wget https://nc.domain.com

--2021-02-18 23:13:40-- https://nc.domain.com/

Resolving nc.domain.com (nc.domain.com)... xxx.xx.xx.xx

Connecting to nc.domain.com (nc.domain.com)|xxx.xx.xx.xx|:443... connected.

HTTP request sent, awaiting response... 302 Found

Location: https://nc.domain.com/login [following]

--2021-02-18 23:13:40-- https://nc.domain.com/login

Reusing existing connection to nc.domain.com:443.

HTTP request sent, awaiting response... 200 OK

Length: 10301 (10K) [text/html]

Saving to: ‘index.html’

index.html 100%[====================================================>] 10.06K --.-KB/s in 0s

2021-02-18 23:13:40 (442 MB/s) - ‘index.html’ saved [10301/10301]

#

Link to post

so after 3 days of troubleshooting, integration is finally working. after surfing endless support pages on the internet a solution from 2018 on onlyoffice support forum worked. for anyone who runs into same error hope this helps:

 

changed value of "rejectUnauthorized": from true to false in /etc/onlyoffice/documentserver/default.json

restart OO docker and tried connecting again in NC and it worked right away.

 

cheers!

Edited by GGabs
Link to post
15 hours ago, saarg said:

I read it as you used the IP locally. Your new router most likely doesn't support NAT hairpin or split DNS. That's what makes the domain work locally also.

I started looking for this and my ISP indeed doesn't support NAT hairpin. So how can I access my Nextcloud installation locally? I notice when I use my local LAN ip for my Nextcould it always reroutes directly to the domain name one. Is there a way around this?

Link to post

UNRAID VER. 6.8.3 NEXTCLOUD VER. 15.0.2 UPDATE ISSUE. (SELF INDUCED)

 

Mistake 1

I thought that when I updated the nextcloud docker I was updating the Nextcloud Application. I was wrong. I am way behind in the version of nextcloud that i'm using.
I found a manual update method on one of "linuxserver.io" guides by using the unraid terminal and entered “docker exec -it nextcloud updater.phar”
It seems to have run…

 

Quote

Current version is 15.0.2.

Update to Nextcloud 16.0.11 available. (channel: “stable”)
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-16.0.11.zip

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
[] Downloading
[] Verify integrity
[] Extracting
[] Enable maintenance mode
[] Replace entry points
[] Delete old files
[] Move new files in place
[] Done

Update of code successful.

Should the “occ upgrade” command be executed? [Y/n] n
Please now execute “./occ upgrade” to finish the upgrade.
root@StorageBox:~#

 

Mistake 2

I didn’t answer Y to the question. “Should the “occ upgrade” command be executed? [Y/n]”

Now I can’t figure out how to get back to run this script.

Is all lost? Is there hope of recovery? Should I delete this docker and start over?

 

Any help would be appreciated.

Thank you.

Kopyguy

 

Also as a side question is the Maria Database falling behind too? I've only done the docker updates on it. 

Link to post
6 hours ago, jonasdegent said:

I started looking for this and my ISP indeed doesn't support NAT hairpin. So how can I access my Nextcloud installation locally? I notice when I use my local LAN ip for my Nextcould it always reroutes directly to the domain name one. Is there a way around this?

I'm not sure how to do that.

Link to post
7 hours ago, jonasdegent said:

I started looking for this and my ISP indeed doesn't support NAT hairpin. So how can I access my Nextcloud installation locally? I notice when I use my local LAN ip for my Nextcould it always reroutes directly to the domain name one. Is there a way around this?

Share your config.php.
probably need to remove overwritehost line, but i don't know if it will have impact when accessing from external.

Link to post
1 minute ago, skois said:

Share your config.php.
probably need to remove overwritehost line, but i don't know if it will have impact when accessing from external.

I thought about that, but wasn't sure if it messes up the external access.

Link to post
On 2/16/2021 at 11:22 PM, ICDeadPpl said:

Try with opening the Nextcloud console (click on Nextcloud icon on Docker page) and run this command: sudo -u abc php7 /config/www/nextcloud/occ maintenance:mode --off

 

THANK YOU! I'm back up and running!

Link to post
On 2/19/2021 at 11:42 PM, skois said:

Share your config.php.
probably need to remove overwritehost line, but i don't know if it will have impact when accessing from external.

I just commented my overwritehost line in the php file and it finally works locally. If I connect via 4G (so outside my network) it seems to work too.

Link to post
I just commented my overwritehost line in the php file and it finally works locally. If I connect via 4G (so outside my network) it seems to work too.
That's good, I would check with nextcloud forums also, if this opens up any security holes

Sent from my Mi 10 Pro using Tapatalk

Link to post

Hi all,

After a reinstall of Nextcloud, there is still an old entry from the former installation in "External storages" which can not be deleted. The link worked fine in the former installation, but doesn't anymore. How can i delete this entry? Thank you for help!

 

NC.thumb.png.1f2d6ff6081424d46018d29fb858ca5c.png

Link to post

Anyone else getting "/.well-known/webfinger" & "/.well-known/nodeinfo" with 21.0.0 ?

Along with "you've not specified a dialing code" ?

 

The latter is easily fixable with a quick amendment to config, but the former, despite the same syntax as the other webdav redirects, doesn't want to work for some reason.

Link to post
2 hours ago, boomam said:

Anyone else getting "/.well-known/webfinger" & "/.well-known/nodeinfo" with 21.0.0

 

I believe you need to add the following to your nginx config 

 

    # Make a regex exception for `/.well-known` so that clients can still
    # access it despite the existence of the regex rule
    # `location ~ /(\.|autotest|...)` which would otherwise handle requests
    # for `/.well-known`.
    location ^~ /.well-known {
        # The following 6 rules are borrowed from `.htaccess`

        location = /.well-known/carddav     { return 301 /remote.php/dav/; }
        location = /.well-known/caldav      { return 301 /remote.php/dav/; }
        # Anything else is dynamically handled by Nextcloud
        location ^~ /.well-known            { return 301 /index.php$uri; }

        try_files $uri $uri/ =404;
    }


See documentation  https://docs.nextcloud.com/server/21/admin_manual/installation/nginx.html and also https://docs.nextcloud.com/server/21/admin_manual/issues/general_troubleshooting.html#service-discovery

Link to post

So I've spent the better part of 3 hours on this tonight and I have 2 "errors" left in my Nextcloud setup. 

Fresh 21.0.0 install
Fresh SWAG install

Using duckdns.org and Spaceinvader's setup video. 

 

Quote

Your web server is not properly set up to resolve "/.well-known/webfinger". 
Your web server is not properly set up to resolve "/.well-known/nodeinfo". 



I can't for the life of me figure out what to edit and where. I see NGINX posts saying to edit something here, I see others saying to edit .htaccess files. None of the searches I've done here and abroad have lead to a concrete "edit this, do this here" answer.

At the end of my proverbial rope and patience. 

Link to post
4 hours ago, DayspringGaming said:

So I've spent the better part of 3 hours on this tonight and I have 2 "errors" left in my Nextcloud setup. 

Fresh 21.0.0 install
Fresh SWAG install

Using duckdns.org and Spaceinvader's setup video. 

 



I can't for the life of me figure out what to edit and where. I see NGINX posts saying to edit something here, I see others saying to edit .htaccess files. None of the searches I've done here and abroad have lead to a concrete "edit this, do this here" answer.

At the end of my proverbial rope and patience. 

Add this to the site config within the nextcloud container. We plan to add this soon.

Link to post
9 hours ago, Abzstrak said:

anyone getting the option to upgrade to 21?  Mine is at 20.0.7 and showing no updates available.  I tried beta, but that only offered 20.0.8 RC...

Curious how everyone updates their nextcloud with unraid.  Mine is still on 20.0.5 and I see 20.0.7 available in the admin panel.  I assumed the docker updates would also trigger the upgrades similar to plex, but I see from the first post there are 3 recommended options.

 

Which is the safest approach or is it all practically the same?

Link to post
11 hours ago, Abzstrak said:

anyone getting the option to upgrade to 21?  Mine is at 20.0.7 and showing no updates available.  I tried beta, but that only offered 20.0.8 RC...

You have to go to 20.0.8 RC1, and then it will offer 21.0.0 afterwards.

Once done, revert back to the stable channel.

Edited by boomam
Link to post

Well this news is pretty exciting. Apparently Nextcloud 21 is said to be twice as fast. Should we really expect to see these kind of results in real world use? I'd love to see faster load times. Although 2 X as fast means my text document load in 6 seconds instead of 12. Still an improvement!

 

https://www.zdnet.com/article/nextcloud-21-arrives-with-ten-times-better-performance/

Link to post
1 hour ago, adminmat said:

Well this news is pretty exciting. Apparently Nextcloud 21 is said to be twice as fast. Should we really expect to see these kind of results in real world use? I'd love to see faster load times. Although 2 X as fast means my text document load in 6 seconds instead of 12. Still an improvement!

 

https://www.zdnet.com/article/nextcloud-21-arrives-with-ten-times-better-performance/

In a QA after the release, they said, the performance wont be much noticable in small installations (2-10 users), but we will notice the instant notifications.

Link to post
6 hours ago, j0nnymoe said:

Add this to the site config within the nextcloud container. We plan to add this soon.

Could you please be more specific? What exactly to add?
Also I guess you mean to put "that" in the "/appdata/nextcloud/ngiong/site-confs/default"

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.