For those using nginx try this in /sites-available/…
location = /.well-known/webfinger {
rewrite ^/.well-known/webfinger /public.php?service=webfinger last;
}
I have a similar problem as well
But when I put that into .htaccess in my cloud (nextcloud) subfolder it broke my nextcloud so I had to do a reinstall of it
Now I’m back at the start also when I click on the menu it doesn’t show anything eg user, settings
I’m running nextcloud 19.0.1 on ubuntu 20.04 with apache and php 7.4
Some photos
There must be someone that can help us with this?
I am also running NC on Ubuntu 20 with PHP7.4 and nginx. I have added the rewrite well-known to nextcloud.conf for nginx, but does not seem to work. When I navigate to https://my-domain.com/.well-known/webfinger?resource=acct:mark@my.domain.com I actually get 403 forbidden warning.
I would really love to start using social, so I am hoping someone can help me with this.
Hi, Also on ubuntu 20.04 with apache and php7.4 and I’m getting the same behaviour.
/nextcloud/index.php/settings/admin/overview sometimes tells me there are three .well-known links missing, othertimes it only tells me webfinger is missing.
Adding https://mydomain.com/ to the rewrites broke it more than fixed it. At least without it I get the pretty Internal Server Error. I get the same Internal Server Error when requesting the raw /webfinger and when I append my user account name.
pointing .whatever-else-than-wellknown RewriteRule ^\.whatever-else/webfinger nc/public.php?service=webfinger [QSA,L] and visiting https://mydomain.com/.whatever-else/webfinger gives me Nextcloud’s screen " Internal Server Error"
but pointing RewriteRule ^\.well-known/webfinger nc/public.php?service=webfinger [QSA,L] and visiting https://mydomain.com/.well-known/webfinger gives me my host’s 404.
The reason might be same as here - the managed server doesn’t allow my .htaccess to play around with exactly that folder.
So the proposed patches in .htaccess take no effect in my case.
Is there information documented on the public.php, index.php and remote.php and how webfinger, hostmeta, nodeinfo etc and the way they interact with the resource= or service= call. I have seen many different examples. The examples in the nextcloud website do not work. It would help with testing, and not having to dig through the code. Also I am curious if these calls are supposed to be ssl or http or both as I have seen that could be a problem.