did some test using a subfolder for the installation of nextcloud, can confirm it works.

I just had to put generate a .htaccess file at the root of the webfolder:

RewriteEngine on
RewriteRule ^\.well-known/webfinger https://test.pontapreta.net/nextcloud/public.php?service=webfinger [QSA,L]

It is not the cleanest solution as it does some redirection and this should be hidden with some proxy stuff, but it works™

For those using nginx try this in /sites-available/…
location = /.well-known/webfinger {
rewrite ^/.well-known/webfinger /public.php?service=webfinger last;

1 Like

Hello all,

I am getting this error and I’ve tried the following settings below but still failing. Could it be because I’m using self-signed certificate?

RewriteRule ^.well-known/webfinger /nextcloud/public.php?service=webfinger [QSA,L]
RewriteRule ^.well-known/webfinger https://${SERVER_NAME}/public.php?service=webfinger [QSA,L]

here’s part of my httpd.conf setting:
<Directory /var/www/nextcloud/>
Options +FollowSymlinks
AllowOverride All
Satisfy Any
Require all granted

Dav off

SetEnv HOME /var/www/nextcloud
SetEnv HTTP_HOME /var/www/nextcloud

that is also my problem.

carddav and caldav work fine

this is my nginx config:

  location = /.well-known/webfinger {
      rewrite ^/.well-known/webfinger /public.php?service=webfinger last;
  location = /.well-known/carddav {
      return 301 /remote.php/dav;
  location = /.well-known/caldav {
      return 301 /remote.php/dav;
  location / {
      include                     snippets.d/proxy_generic;
      proxy_pass        ;

I have also this problem :
Using Nginx with no problems on Cardav and Caldav :

 location = /.well-known/webfinger {
      rewrite ^/.well-known/webfinger /public.php?service=webfinger last;

hope someone can give us clues

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.

Log is giving me:
Exception: The requested uri(/.well-known/webfinger) cannot be processed by the script ‘/nextcloud/public.php’)

  1. /var/www/nextcloud/lib/private/AppFramework/Http/Request.php - line 808:OC\AppFramework\Http\Request->getRawPathInfo()
  2. /var/www/nextcloud/public.php - line 47:OC\AppFramework\Http\Request->getPathInfo()

Fixing “@user@localhost” didn’t help.

The app is simply not yet ready for production.

People releasing alpha software usually are eager to have bug reports.

1 Like

even after uninstalling it, still show this error. sillyness

I’m on a webhost installed on mydomain.com/nc and see the same after installing Social.
What I found:

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.

I have same problem here. Using apache. It happened after last update of nextcloud - together with occ memory hogging problem.

not working for me on nginx

The above rewrite rule has never worked for me.

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.

1 Like