Elaborate on Service Discovery troubleshooting
- provide subsections for the different services and configurations
- provide command line
curlexamples to debug the redirects - provide example config for apache
.htaccessto redirect any well known service - consistently use
NGINXin headers, andnginxin text - fix some spelling/grammar
☑️ Resolves
- Does not resolve, but is related to https://github.com/nextcloud/server/issues/40387
🖼️ Screenshots
- /issues/general_troubleshooting.html#service-discovery-label
- /installation/nginx.html#troubleshooting
Happy to backport, once accepted.
May help with these issues:
- nextcloud/server#27865
- nextcloud/server#38035
Thank you :+1:
/backport to stable27
/backport to stable26
@kesselb Thanks for looking into this and approving.
I'm not sure I understand the last two comments correctly: does the bot do the backports or shall I provide them?
@martin-rueegg Bot does them. :) Or tries to. Succeeds more often than not as long as it's not a high traffic change area in the docs.
@martin-rueegg Bot does them. :) Or tries to. Succeeds more often than not as long as it's not a high traffic change area in the docs.
@kesselb Thanks for the clarification.
Will you accept PR's to backport it to older versions too?
It seems an issue that is confusing quite some people over the years and I think it would be great to have the docs updated on this issue. This will cause less tickets and forum questions.
Why is this DCO check so picky?! All commits are perfectly signed with my signature. It even shows verified in the entries above...
@rlew-is
fixed a couple of typos
Thank you. Appreciated and implemented.