-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: nginx configuration flags webfinger / nodeinfo issue #38035
Comments
Are you running NC out of a subdirectory of your webroot (i.e. |
Thank you for taking the time to report a problem 👍 As this seems to be a setup issue I would like to ask you to raise your question at https://help.nextcloud.com |
As this doesn't address the RC (incorrect content on the web site), I am going to open another issue so this can be addressed and tracked. |
I assume you added trusted_proxies because you are using a reverse proxy. Did you read https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/reverse_proxy_configuration.html? Likely Nextcloud does not know how to route your request due the subdirectory. And the next time, go to https://help.nextcloud.com/. |
Unfortunately the link you referred to results in a "File not found" web page :-( Perhaps another opportunity for optimising the website? :-) And if the proxy setup was incorrect the instance would not be working in general. Fun fact: Removing this from config.php doesn't make a difference. :-) |
One - and certainly both - of these scenarios means that the If you have a reverse proxy in front then it is intercepting requests to anything If you're able to find where that 404 is being logged I suspect it'll lead you to the root cause of the matter. Momentarily commenting out |
The 404 comes back from the FPM invocation according to the rewrite debug logs. In contrast to this, the Apache invocation gives back "method not supported" (as it should), although the URL rewrites are equivalent:
|
Same issue here: NC 27. Rewrite rules are working (i.e. redirecting to /index.php/.well-known/webfinger using a 301 response) this URL only reults in 404 with nginx. |
I placed this here for future generations.
|
What about updating the main documentation (although community-maintained)? |
@PolishTanker
|
Bug description
The nginx configuration as documented in https://docs.nextcloud.com/server/latest/admin_manual/installation/nginx.html causes NC (v25.0.6) to flag these issues. A 404 is returned proper but instead of
{"message":"webfinger not supported"}
I'm gettingMore than happy to provide more info as required.
Steps to reproduce
Expected behavior
Expected
{"message":"webfinger not supported"}
Installation method
Community Manual installation with Archive
Nextcloud Server version
25
Operating system
Debian/Ubuntu
PHP engine version
PHP 7.4
Web server
Nginx
Database engine version
SQlite
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 22.2.3 to 22.2.4)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: