You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 8, 2024. It is now read-only.
.well-known/webfinger isn't properly set up!
Social needs the .well-known automatic discovery to be properly set up. If Nextcloud is not installed in the root of the domain, it is often the case that Nextcloud can't configure this automatically. To use Social, the admin of this Nextcloud instance needs to manually configure the .well-known redirects: Open documentation ↗
However, accessing the respective URL produces the right response. Chances are that Nextcloud is expecting the redirect from their documentation, but they are getting the content directly. Might need a PR upstream.
The text was updated successfully, but these errors were encountered:
Add override hostname etc in config file, so social picks up the right hostname (I think) per #65
Point to docs when skip-upgrade of Nextcloud detected
Clean URLs per #48, and updated htaccess from upstream
Added postfix dependency per #53
Make upload size etc configurable per #58
According to the Nextcloud code here, they are looking for an HTTP OK on .../.well-known/webfinger but do not pass any parameters. This is not a very good check, and we don't pass it because we demand-assemble the response and return 404 if the resource does not exist.
However, accessing the respective URL produces the right response. Chances are that Nextcloud is expecting the redirect from their documentation, but they are getting the content directly. Might need a PR upstream.
The text was updated successfully, but these errors were encountered: