@kchan101, I tried index.php too, without luck. And Nextcloud docs say public.php.
Dav is working well, but webfinger and nodeinfo, not. https://www.mysite.com/.well-known/webfinger brings me to the dashboard of Nextcloud when I set the redirect to index.php. If I set it back to public.php, .well-known/webfinger redirects to: https://www.mysite.com/nextcloud/.well-known/webfinger.
But still a security warning in Nextcloud settings.
Does anyone with this kind of setup has got it working?
Ubuntu server, Apache, php7.4-fpm, Nextcloud 21 in subdir as conf-available /nextcloud.
The docs only seem to document entries for caldav/carddav. Besides using index.php rather than public.php, the format of the rewrite is also different. I have the following entries which got rid of the warnings:
Iām having the same problems, though with Docker, which for some reason has a different/older nginx.conf.
However, the approved solution (Miyamoto) works as far as nginx redirects are concerned, but https://my.nextcloud.com/index.php/.well-known/nodeinfo ALSO returns 403. Iāve looked elsewhere, and the checks seem to be looking for a HTTP 200. So, something else might be incorrect, but maybe not nginx.
I too am having this same issue. NC 21 on Ubuntu 20.04, proxied through a separate VM running Apache as a reverse proxy. Cannot figure out how to get rid of the webfinger error.
Canāt even install social, get an error message about extraction failing. Federation yes, but I tried disabling it and I still get the error message in admin
No, I get a white page that just says: {āmessageā:āi-am-the-wurst not supportedā}
I donāt have either enabled, and I think Social is broken right now. However, I am wondering if webfinger/nodeinfo is only enabled and active IF either Social or Federation is also enabled. Social definitely uses them, but not sure about Federation.
Why do I want Nextcloud to verify any phone numbers? Just let people turn of verification and the problem is solved. Now I set a region so that nc is happy, but the verification will still fail for users, who do not live in that region, which is very much possible, if you have a worldwide user base. So whatās the point?
P.S.: I have 3 SIM cards for 3 different countries. Thereās a very good reason why I donāt add a country code to some of my phone numbers. (I know, not a profile thing, but still - an explanation why it can make sense not to use a country code.)
I couldnāt agree more. Have three SIM for different countries. Users live in different countries.
It is become a disturbing trend that NC invents wheels and features just to implement something, which break design, alter established (very good) UX/UI and all this for what?! Sometimes I wish there would be a release/update channel, which would be based on 17 or 18 version only with security updatesā¦ And sometimes I even afraid to update NC installation to avoid such āfeaturesā like the problems on this thread
Yep, all the new āfeaturesā that came out in the last 3 versions, I deactivated right away. Iām not sure whoās steering the boat, but itās getting ridiculous.
It would be a lot better, if they were to finally fix pressing issues in the server core. Oh, and btw, the sync client still canāt do http2. In 2021. But at least they have a VFS that messes up normal sync operations. Just brilliant.