Skip to content
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

NC 15.0.2: cannot resolve "/.well-known/caldav & carddav (NGINX Reverse Proxy) #14007

Closed
kangaroo72 opened this issue Feb 3, 2019 · 10 comments
Closed
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap bug

Comments

@kangaroo72
Copy link

kangaroo72 commented Feb 3, 2019

Hi,

I've setup a new system on a ARM64-ODROID C2.
NGINX 1.15.8, PHP 7.3.1 & NC 15.0.2

The german messages are ...

Dein Web-Server ist nicht richtig eingerichtet um "/.well-known/caldav" aufzulösen. Weitere Informationen findest Du in der Dokumentation.

and

Dein Web-Server ist nicht richtig eingerichtet um "/.well-known/carddav" aufzulösen. Weitere Informationen findest Du in der Dokumentation.

Actually I'm unable to fix it ... can you help me?

Here's my nextcloud.conf ... https://paste.escher.cc/view/b88e8a9a#L25

Thank you

@kangaroo72 kangaroo72 added 0. Needs triage Pending check for reproducibility or if it fits our roadmap bug labels Feb 3, 2019
@AndrStnz
Copy link

AndrStnz commented Feb 4, 2019

Well, same issue with traefik Load Balancer in front of nextcloud 15.0.2
Not that it creates any problems as far as I am concerned at the moment.

@kangaroo72
Copy link
Author

won a shirt now? :-D

@kangaroo72 kangaroo72 changed the title NC 15.0.2: cannot resolve "/.well-known/caldav & carddav (NGINX Reserve Proxy) NC 15.0.2: cannot resolve "/.well-known/caldav & carddav (NGINX Reverse Proxy) Feb 4, 2019
@j-ed
Copy link
Contributor

j-ed commented Feb 4, 2019

It might be worse to use the search function before opening new issue tickets 😉
This ticket sound similar to yours: #11789

@kangaroo72
Copy link
Author

yep - but was earlier NC-Version?!

@j-ed
Copy link
Contributor

j-ed commented Feb 4, 2019

I think the essential information is that the issue describes the .well-known link and NGINX problem. The NC version is more or less off relevance.

@AndrStnz
Copy link

AndrStnz commented Feb 4, 2019

won a shirt now? :-D

Just wanted to add that this is not an nginx exclusive thingy.... ;D

@kesselb
Copy link
Contributor

kesselb commented Feb 4, 2019

Ngnix: #11850 (comment)
Traefik: #11850 (comment)

I think we should add this information to https://github.com/nextcloud/documentation/blob/master/admin_manual/configuration_server/reverse_proxy_configuration.rst. @kangaroo72 @AndrewwHummer do you want to submit a pull request? 😀

@kesselb kesselb closed this as completed Feb 4, 2019
@kangaroo72
Copy link
Author

Nice idea ... maybe Andrew - I'm not so involved in these thinks - sorry - but thank you

@kesselb
Copy link
Contributor

kesselb commented Feb 4, 2019

image

It's easy! Just follow the link and click the pencil ;-)

@AndrStnz
Copy link

AndrStnz commented Feb 5, 2019

Adding this to the documentation is a great idea. Adding it to the list :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0. Needs triage Pending check for reproducibility or if it fits our roadmap bug
Projects
None yet
Development

No branches or pull requests

4 participants