[Support] Linuxserver.io - Nextcloud


Recommended Posts

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 comment
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

  • Like 1
Link to comment

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 comment

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 comment
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 comment

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. 

  • Like 2
Link to comment
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 comment
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 comment
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 comment
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 comment
1 hour ago, Tolete said:

Still no joy on nextcloud 21

waiting on update.

-anyone got the repository "linuxserver/nextcloud tag ?"

 

It doesn't help to use the tag as you have to update nextcloud inside the container.  Updating the container doesn't update nextcloud.

Link to comment
4 hours ago, skois said:

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"

Yea apologies - we just need to add the additional nginx bits to the site config file. Though if you've done it manually, all good 👍

Link to comment
Yea apologies - we just need to add the additional nginx bits to the site config file. Though if you've done it manually, all good
Because I'm not any good with nginx, do you have the bits on hand? Or do you know if the docker will be updated soon to include them?
Thanks!

Sent from my Mi 10 Pro using Tapatalk

Link to comment
5 hours ago, Tolete said:

thank you, what are the correct parameters to add it manually?

 

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 301 $scheme://$host:$server_port/remote.php/dav;
}
location = /.well-known/caldav {
  return 301 $scheme://$host:$server_port/remote.php/dav;
}
location = /.well-known/webfinger {
  return 301 $scheme://$host:$server_port/public.php?service=webfinger;
}
location = /.well-known/host-meta {
  return 301 $scheme://$host:$server_port/public.php?service=host-meta;
}
location = /.well-known/host-meta.json {
  return 301 $scheme://$host:$server_port/public.php?service=host-meta-json;
}

with these lines

# 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;
}

Then I restarted the Nextcloud docker and the error was gone.

  • Thanks 6
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.