Skip to content
This repository has been archived by the owner on Jun 8, 2024. It is now read-only.

Nextcloud/social self-check incorrect reports invalid webfinger setup #65

Closed
jernst opened this issue Oct 8, 2019 · 1 comment
Closed
Labels
Milestone

Comments

@jernst
Copy link
Member

jernst commented Oct 8, 2019

 .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.

@jernst jernst added this to the ubos-apps-20 milestone Nov 6, 2019
@jernst jernst added the verify label Nov 6, 2019
jernst added a commit that referenced this issue Nov 6, 2019
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
@jernst
Copy link
Member Author

jernst commented Nov 9, 2019

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.

Needs fixing upstream, see nextcloud/social#816.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant