Bonjour Mathieu,
Le nextcloud est rétabli oui, et la mise à jour jusqu’à la 19.0.4 est bien passée, merci beaucoup.
Par contre j’ai un message d’erreur sur les contacts depuis le téléphone
"sous Davx5 : erreur serveur HTTP 500 Internal server error. A server-side problem occured. Please contact your support avec un txt de rapport de debug
et dans l’interface admin, j’ai les messages suivants :
* a configuration du serveur web ne permet pas d’atteindre « /.well-known/caldav ». Vous trouverez plus d’informations dans la documentation.
* La configuration du serveur web ne permet pas d’atteindre « /.well-known/carddav ». Vous trouverez plus d’informations dans la documentation.
Je dois récupéré le fichier .htaccess et l’éditer via Notepad++ par exemple en intégrant les lignes indiqué ci-après ?
Merci
Sur la doc nextcloud il est indiqué :
Service discovery
Some clients - especially on iOS/macOS - have problems finding the proper sync URL, even when explicitly configured to use it.
If you want to use CalDAV or CardDAV clients or other clients that require service discovery together with Nextcloud it is important to have a correct working setup of the following URLs:
https://example.com/.well-known/carddav
https://example.com/.well-known/caldav
https://example.com/.well-known/webfinger
Those need to be redirecting your clients to the correct endpoints. If Nextcloud is running at the document root of your Web server the correct URL is:
`https://example.com/remote.php/dav` for CardDAV and CalDAV and
`https://example.com/public.php?service=webfinger`
and if running in a subfolder like nextcloud
:
`https://example.com/nextcloud/remote.php/dav`
`https://example.com/nextcloud/public.php?service=webfinger`
For the first case the .htaccess
file shipped with Nextcloud should do this work for you when you’re running Apache. You need to make sure that your Web server is using this file. Additionally, you need the mod_rewrite Apache module installed to process these redirects. When running Nginx please refer to Nginx configuration.
If your Nextcloud instance is installed in a subfolder called nextcloud
and you’re running Apache create or edit the .htaccess
file within the document root of your Web server and add the following lines:
RewriteEngine on RewriteRule ^.well-known/host-meta /nextcloud/public.php?service=host-meta [QSA,L] RewriteRule ^.well-known/host-meta.json /nextcloud/public.php?service=host-meta-json [QSA,L] RewriteRule ^.well-known/webfinger /nextcloud/public.php?service=webfinger [QSA,L] RewriteRule ^.well-known/carddav /nextcloud/remote.php/dav/ [R=301,L] RewriteRule ^.well-known/caldav /nextcloud/remote.php/dav/ [R=301,L]
Make sure to change /nextcloud to the actual subfolder your Nextcloud instance is running in.
If you are running NGINX, make sure location = /.well-known/carddav {
and location = /.well-known/caldav {
are properly configured as described in Nginx configuration, adapt to use a subfolder if necessary.
Now change the URL in the client settings to just use:
https://example.com
instead of e.g.
https://example.com/nextcloud/remote.php/dav/principals/username
.
There are also several techniques to remedy this, which are described extensively at the Sabre DAV website.