-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
.well-known check behind proxy using path is requesting a wrong URL #16817
Labels
Comments
tikoflano
added
0. Needs triage
Pending check for reproducibility or if it fits our roadmap
bug
labels
Aug 20, 2019
tikoflano
changed the title
.well-known check behind proxy using path
.well-known check behind proxy using path is requesting a wrong URL
Aug 20, 2019
Thanks, maybe this should be added to de docs? |
Sure. You can use the Edit on Github link on the page above to suggest changes. It might be good to have some general information about .well-known or a link to https://en.wikipedia.org/wiki/List_of_/.well-known/_services_offered_by_webservers there. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
The .well-known check tries to check at https://my.domain.com/.well-known/carddav when my installation is behind a proxy at https://my.domain.com/nextcloud, it should make the request to https://my.domain.com/nextcloud/.well-known/carddav.
If I try to check manually the configuration (redirection) is ok. I'm using Traefik as reverse proxy.
Right now my solution is to skip this checks with
occ config:system:set check_for_working_wellknown_setup --value=false
but I would like to have the checks working.It looks like the issue is that the URLs at https://github.com/nextcloud/server/blob/master/settings/js/admin.js#L251 are hard coded.
The text was updated successfully, but these errors were encountered: