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.
I am running NextCloud 21.0.0. These are the warnings on the Overview section (Security & setup warnings) on my server settings:
[Warning 1] * Your web server is not properly set up to resolve ā/.well-known/webfingerā. Further information can be found in the [documentation]
[Warning 2] * Your web server is not properly set up to resolve ā/.well-known/nodeinfoā. Further information can be found in the [documentation]
[Warning 3] * Your web server is not properly set up to resolve ā/.well-known/caldavā. Further information can be found in the [documentation]
[Warning 4] * Your web server is not properly set up to resolve ā/.well-known/carddavā. Further information can be found in the [documentation]
Let me label these warnings from Warning 1 to Warning 4.
Nextcloud resides in the subfolder /nextcloud on my Apache server and the DocumentRoot is set to āvar/www/html/nextcloudā in default-ssl.conf. I can confirm that these lines that allow .htaccess to override configurations in the Apache server help to get ride of Warning 1 and Warning 2. I did not have to add any RewriteRule line in .htaccess.
<Directory /var/www/html/nextcloud>
Options Indexes FollowSymLinks MultiViews
AllowOverride All
Order allow,deny
allow from all
</Directory>
Iām very much obliged to you! My ā/.well-known/webfingerā error lasted for several months. After seeing your message, I fixed my error and now I passed all the security scans. Thank you very much!
This works. Provided you remember to comment out (#) the already existing config for cardav and caldav. Iām a newbie and hadnāt done that initially. And it didnāt work. After commenting out, adding these lines worked for me.