starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

webfinger #1260

New issue

Closed

opened 2026-02-26 06:36:27 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 06:36:27 +03:00

Owner

Originally created by @casperghst42 on GitHub (Dec 27, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1689

Hi,

I'm trying to migrate away from swagger to nginx-proxy-manager, which primarily is hosting an nextcloud.

In my swagger I had:

location = /.well-known/webfinger {
  return 301 $scheme://$host:$server_port/index.php/.well-known/webfinger;
}
location = /.well-known/nodeinfo {
  return 301 $scheme://$host:$server_port/index.php/.well-known/nodeinfo;
}
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;
}

To fix a security issue (reported by nextcloud).

I have added the same both with typed out path (https://server.example.com:443) and as it is above.

I've added the code to the advanced section of the proxy server, but only carddav and caldav is recognized not the webfinger nor nodeinfo.

Looking in the proxy configuration file it is as it used to be with swagger - any idea why this is not working ?

Thanks.

Originally created by @casperghst42 on GitHub (Dec 27, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1689 Hi, I'm trying to migrate away from swagger to nginx-proxy-manager, which primarily is hosting an nextcloud. In my swagger I had: location = /.well-known/webfinger { return 301 $scheme://$host:$server_port/index.php/.well-known/webfinger; } location = /.well-known/nodeinfo { return 301 $scheme://$host:$server_port/index.php/.well-known/nodeinfo; } 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; } To fix a security issue (reported by nextcloud). I have added the same both with typed out path (https://server.example.com:443) and as it is above. I've added the code to the advanced section of the proxy server, but only carddav and caldav is recognized not the webfinger nor nodeinfo. Looking in the proxy configuration file it is as it used to be with swagger - any idea why this is not working ? Thanks.

kerem

2026-02-26 06:36:27 +03:00

closed this issue
added the
stale
label

kerem commented

2026-02-26 06:36:27 +03:00

Author

Owner

@paspo commented on GitHub (Feb 28, 2022):

Hi!
I just came across this issue and this is how I solved it.
As per this page, I put this into the advanced section of the proxy host:

location ^~ /.well-known {
        location = /.well-known/carddav { return 301 /remote.php/dav/; }
        location = /.well-known/caldav  { return 301 /remote.php/dav/; }
        location /.well-known/acme-challenge    { try_files $uri $uri/ =404; }
        location /.well-known/pki-validation    { try_files $uri $uri/ =404; }
        return 301 /index.php$request_uri;
}

@paspo commented on GitHub (Feb 28, 2022): Hi! I just came across this issue and this is how I solved it. As per [this page](https://docs.nextcloud.com/server/23/admin_manual/installation/nginx.html#nextcloud-in-the-webroot-of-nginx), I put this into the advanced section of the proxy host: ``` location ^~ /.well-known { location = /.well-known/carddav { return 301 /remote.php/dav/; } location = /.well-known/caldav { return 301 /remote.php/dav/; } location /.well-known/acme-challenge { try_files $uri $uri/ =404; } location /.well-known/pki-validation { try_files $uri $uri/ =404; } return 301 /index.php$request_uri; } ```

kerem commented

2026-02-26 06:36:27 +03:00

Author

Owner

@casperghst42 commented on GitHub (Mar 1, 2022):

Hi! I just came across this issue and this is how I solved it. As per this page, I put this into the advanced section of the proxy host:

Thank you, but in the mean time I changed to caddy.

@casperghst42 commented on GitHub (Mar 1, 2022): > Hi! I just came across this issue and this is how I solved it. As per [this page](https://docs.nextcloud.com/server/23/admin_manual/installation/nginx.html#nextcloud-in-the-webroot-of-nginx), I put this into the advanced section of the proxy host: Thank you, but in the mean time I changed to caddy.

kerem commented

2026-02-26 06:36:27 +03:00

Author

Owner

@BeWog commented on GitHub (Dec 10, 2022):

I have the same problem since many version of Nextcloud.
Currently, Nextcloud 25.0.2.

I check this configuration : https://docs.nextcloud.com/server/latest/admin_manual/installation/nginx.html
I don't know how to resolve it.

In french:

Votre serveur web n'est pas configuré correctement pour résoudre "/.well-known/webfinger". Plus d'informations peuvent être trouvées sur notre [documentation](https://nextcloud.toto.com/settings/admin/%7BdocLink%7D).
Votre serveur web n'est pas configuré correctement pour résoudre "/.well-known/nodeinfo". Plus d'informations peuvent être trouvées sur notre [documentation](https://nextcloud.toto.com/settings/admin/%7BdocLink%7D).

@BeWog commented on GitHub (Dec 10, 2022): I have the same problem since many version of Nextcloud. Currently, Nextcloud 25.0.2. I check this configuration : https://docs.nextcloud.com/server/latest/admin_manual/installation/nginx.html I don't know how to resolve it. In french: ``` Votre serveur web n'est pas configuré correctement pour résoudre "/.well-known/webfinger". Plus d'informations peuvent être trouvées sur notre [documentation](https://nextcloud.toto.com/settings/admin/%7BdocLink%7D). Votre serveur web n'est pas configuré correctement pour résoudre "/.well-known/nodeinfo". Plus d'informations peuvent être trouvées sur notre [documentation](https://nextcloud.toto.com/settings/admin/%7BdocLink%7D). ```

kerem commented

2026-02-26 06:36:27 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 28, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Feb 28, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 06:36:27 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 14, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Apr 14, 2025): Issue was closed due to inactivity.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#1260

No description provided.

Rows
Columns