NEXTCLOUD/COLLABORA ONLINE documents ne s'affiche plus suite montée de version


#1

Bonjour,

Suite à la montée de version de mon YUNOHOST en 3.4.2.2, je n’ai plus accès à mes documents collabora.
En gros ce sont des .odt qui fonctionnés hier, je ne peux pas les ouvrir/éditer en ligne j’ai un cercle qui boucle.
par contre je peux en créer des nouveaux sans les éditer ou les rapatrier pour travailler off line (pas vraiment mon but).
Quelqu’un a rencontré le problème?
Pas de log sur le serveur et sur le nextcloud j’ai trouvé ça

richdocuments	GuzzleHttp\Exception\RequestException: cURL error 60: SSL certificate problem: self signed certificate in certificate chain
GuzzleHttp\Exception\RequestException: cURL error 60: SSL certificate problem: self signed certificate in certificate chain

0. /var/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/RequestFsm.php - line 103: GuzzleHttp\Exception\RequestException wrapException(Object(GuzzleHttp\Message\Request), Object(GuzzleHttp\Ring\Exception\RingException))
1. /var/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/RequestFsm.php - line 132: GuzzleHttp\RequestFsm->__invoke(Object(GuzzleHttp\Transaction))
2. /var/www/nextcloud/3rdparty/react/promise/src/FulfilledPromise.php - line 25: GuzzleHttp\RequestFsm->GuzzleHttp\{closure}(*** sensitive parameters replaced ***)
3. /var/www/nextcloud/3rdparty/guzzlehttp/ringphp/src/Future/CompletedFutureValue.php - line 55: React\Promise\FulfilledPromise->then(Object(Closure), NULL, NULL)
4. /var/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/Message/FutureResponse.php - line 43: GuzzleHttp\Ring\Future\CompletedFutureValue->then(Object(Closure), NULL, NULL)
5. /var/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/RequestFsm.php - line 134: GuzzleHttp\Message\FutureResponse proxy(Object(GuzzleHttp\Ring\Future\CompletedFutureArray), Object(Closure))
6. /var/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/Client.php - line 165: GuzzleHttp\RequestFsm->__invoke(Object(GuzzleHttp\Transaction))
7. /var/www/nextcloud/3rdparty/guzzlehttp/guzzle/src/Client.php - line 125: GuzzleHttp\Client->send(Object(GuzzleHttp\Message\Request))
8. /var/www/nextcloud/lib/private/Http/Client/Client.php - line 138: GuzzleHttp\Client->get('https //collabo...', Array)
9. /var/www/nextcloud/apps/richdocuments/lib/WOPI/DiscoveryManager.php - line 84: OC\Http\Client\Client->get('https //collabo...')
10. /var/www/nextcloud/apps/richdocuments/lib/WOPI/Parser.php - line 41: OCA\Richdocuments\WOPI\DiscoveryManager->get()
11. /var/www/nextcloud/apps/richdocuments/lib/TokenManager.php - line 155: OCA\Richdocuments\WOPI\Parser->getUrlSrc('application/vnd...')
12. /var/www/nextcloud/apps/richdocuments/lib/Controller/DocumentController.php - line 184: OCA\Richdocuments\TokenManager->getToken(*** sensitive parameters replaced ***)
13. [internal function] OCA\Richdocuments\Controller\DocumentController->index('188')
14. /var/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 161: call_user_func_array(Array, Array)
15. /var/www/nextcloud/lib/private/AppFramework/Http/Dispatcher.php - line 91: OC\AppFramework\Http\Dispatcher->executeController(Object(OCA\Richdocuments\Controller\DocumentController), 'index')
16. /var/www/nextcloud/lib/private/AppFramework/App.php - line 115: OC\AppFramework\Http\Dispatcher->dispatch(Object(OCA\Richdocuments\Controller\DocumentController), 'index')
17. /var/www/nextcloud/lib/private/AppFramework/Routing/RouteActionHandler.php - line 47: OC\AppFramework\App main('OCA\\Richdocumen...', 'index', Object(OC\AppFramework\DependencyInjection\DIContainer), Array)
18. [internal function] OC\AppFramework\Routing\RouteActionHandler->__invoke(Array)
19. /var/www/nextcloud/lib/private/Route/Router.php - line 297: call_user_func(Object(OC\AppFramework\Routing\RouteActionHandler), Array)
20. /var/www/nextcloud/lib/base.php - line 999: OC\Route\Router->match('/apps/richdocum...')
21. /var/www/nextcloud/index.php - line 42: OC handleRequest()
22. {main}

Si ça parle à quelqu’un merci


#2

Visiblement le problème est lié aux certificats.

Est-ce que l’un des domaines en jeux utilise un certificat autosigné ?


#3

Salut @Aleks merci de ton aide.
J’ai vérifié tous les certificats ils étaient en let’s encrypt sauf celui de base domaine en .nohost ce qui me parait bizarre.
Je lui ai mis un let’s Encrypt même soucis.
J’ai modifié le domaine principale avec le domaine lié à mon nom de domaine pareil, le document semble charger mais n’apparait pas, par contre je n’ai pas de nouveau log


#4

@homerc Tu utilises quelle méthode d’installation pour collaboraonline ?

Avec l’app docker ou l’app utilisant le .deb ? Ou alors c’est une installation à la main ?

Si tu utilises le .deb peut être qu’il s’est mis à jour et qu’il faut mettre à jour la configuration nginx?


#5

Comme ça je dirais que ton fichier nginx qui configure le reverse proxy vers collabora devrait utiliser http et pas https, ce serait plus simple.

Ne pas oublier dans ce cas de passer la settings ssl.termination à true dans loolwsd.xml


#6

Salut @ljf
j’ai installé comme ça https://github.com/YunoHost-Apps/collaboraonline_ynh : sans docker
Après la de suite je ne comprend pas le reste de ton message je vais essayer de creuser pour te répondre et comprendre .
comment trouver la config de NGINX?
Merci en tout cas


#7

Dans /etc/nginx/nginx.conf ainsi que /etc/nginx/conf.d/TonDomaine.conf


#8

Merci


#9

Bon j’ai trouvé ça qui me semble pas mal comme point de départ

2019/02/08 00:03:26 [error] 1207#1207: ocsp.int-x3.letsencrypt.org could not be resolved (110: Operation timed out) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org
2019/02/08 03:52:36 [error] 1206#1206: ocsp.int-x3.letsencrypt.org could not be resolved (110: Operation timed out) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org

Ce que je comprend mais si quelqu’un me confirmer, c’est que mon certificat let’s encrypt ne passe plus pour valable
ocsp.int-x3.letsencrypt.org
C’est ça?

2019/02/08 05:20:12 [error] 1205#1205: ocsp.int-x3.letsencrypt.org could not be resolved (110: Operation timed out) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org
2019/02/08 05:59:57 [error] 1207#1207: ocsp.int-x3.letsencrypt.org could not be resolved (110: Operation timed out) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org
2019/02/08 08:36:39 [error] 1206#1206: ocsp.int-x3.letsencrypt.org could not be resolved (110: Operation timed out) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org
2019/02/08 08:36:44 [info] 30707#30707: Using 32768KiB of shared memory for nchan in /etc/nginx/nginx.conf:64
2019/02/08 08:36:44 [warn] 30707#30707: could not build optimal variables_hash, you should increase either variables_hash_max_size: 1024 or variables_hash_bucket_size: 64; ignoring variables_hash_bucket_size
2019/02/08 08:37:59 [error] 1207#1207: ocsp.int-x3.letsencrypt.org could not be resolved (110: Operation timed out) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org

Ah oui si je débranche collabora Online, je peux télécharger les docs, le modifier les déposer à nouveau


#10

L’app dont tu fournis l’url est à priori fonctionnel en testing mais pas sur la branche principale.

Il faut donc installer via cette url en ligne de commande https://github.com/YunoHost-Apps/collaboraonline_ynh/tree/testing

yunohost app install https://github.com/YunoHost-Apps/collaboraonline_ynh/tree/testing --debug


#11

Bon j’ai désinstallé ma version et tenté l’installation de la testing mais j’ai ça

2019-02-08 12:44:26,498: DEBUG - + local ‘shell=–shell /usr/sbin/nologin’
2019-02-08 12:44:26,498: DEBUG - + useradd --no-create-home --system --user-group collabora --shell /usr/sbin/nologin
2019-02-08 12:44:30,305: DEBUG - + cp -a …/conf/loolwsd.xml /etc/loolwsd
2019-02-08 12:44:30,305: DEBUG - + ynh_replace_string NEXTCLOUDDOMAIN iphodase.fr /etc/loolwsd/loolwsd.xml
2019-02-08 12:44:30,305: DEBUG - + local delimit=@
2019-02-08 12:44:30,306: DEBUG - + local match_string=NEXTCLOUDDOMAIN
2019-02-08 12:44:30,306: DEBUG - + local replace_string=iphodase.fr
2019-02-08 12:44:30,306: DEBUG - + local workfile=/etc/loolwsd/loolwsd.xml
2019-02-08 12:44:30,307: DEBUG - + match_string=NEXTCLOUDDOMAIN
2019-02-08 12:44:30,307: DEBUG - + replace_string=iphodase.fr
2019-02-08 12:44:30,307: DEBUG - + sudo sed --in-place s@NEXTCLOUDDOMAIN@iphodase.fr@g /etc/loolwsd/loolwsd.xml
2019-02-08 12:44:30,308: DEBUG - + ynh_replace_string PASSWORD ********** /etc/loolwsd/loolwsd.xml
2019-02-08 12:44:30,308: DEBUG - + local delimit=@
2019-02-08 12:44:30,308: DEBUG - + local match_string=PASSWORD
2019-02-08 12:44:30,309: DEBUG - + local replace_string=**********
2019-02-08 12:44:30,309: DEBUG - + local workfile=/etc/loolwsd/loolwsd.xml
2019-02-08 12:44:30,309: DEBUG - + match_string=PASSWORD
2019-02-08 12:44:30,310: DEBUG - + replace_string=‘*
2019-02-08 12:44:30,310: DEBUG - + sudo sed --in-place 's@PASSWORD@
******@g’ /etc/loolwsd/loolwsd.xml
2019-02-08 12:44:30,411: DEBUG - + systemctl start loolwsd
2019-02-08 12:44:30,411: WARNING - Job for loolwsd.service failed because the control process exited with error code.
2019-02-08 12:44:30,412: DEBUG - + ynh_exit_properly
2019-02-08 12:44:30,412: WARNING - See “systemctl status loolwsd.service” and “journalctl -xe” for details.
2019-02-08 12:44:30,412: DEBUG - + local exit_code=1
2019-02-08 12:44:30,413: WARNING - !!
2019-02-08 12:44:30,413: DEBUG - + ‘[’ 1 -eq 0 ‘]’
2019-02-08 12:44:30,414: WARNING - collabora’s script has encountered an error. Its execution was cancelled.
2019-02-08 12:44:30,414: DEBUG - + trap ‘’ EXIT
2019-02-08 12:44:30,414: WARNING - !!
2019-02-08 12:44:30,415: DEBUG - + set +eu
2019-02-08 12:44:30,415: WARNING -
2019-02-08 12:44:30,416: DEBUG - + echo -e ‘!!\n collabora’’‘s script has encountered an error. Its execution was cancelled.\n!!’
2019-02-08 12:44:30,416: DEBUG - + type -t ynh_clean_setup
2019-02-08 12:44:30,416: DEBUG - + ynh_clean_setup
2019-02-08 12:44:30,417: DEBUG - + true
2019-02-08 12:44:30,417: DEBUG - + ynh_die
2019-02-08 12:44:30,418: DEBUG - + echo ‘’
2019-02-08 12:44:30,418: DEBUG - + exit 1

Je n’ai pas mis li log avant car tout semble se dérouler normalement
Merci de l’aide


#12

Bon j’ai désinstallé collabora et refait l’install avec l’officiel
https://yunohost.org/#/collabora
J’ai maintenant des erreurs NGINX Collabora

2019/02/09 17:30:05 [error] 1149#1149: *6256 open() "/usr/share/nginx/html/hosting/capabilities" failed (2: No such file or directory), client: 2001:41d0:8:15ba::1, server: collabora.iphodase.fr, request: "GET /hosting/capabilities HTTP/1.1", host: "collabora.iphodase.fr"
2019/02/09 17:47:26 [error] 1153#1153: *6482 connect() failed (111: Connection refused) while connecting to upstream, client: 2001:41d0:8:15ba::1, server: collabora.iphodase.fr, request: "POST /lool/convert-to/png HTTP/1.1", upstream: "https://127.0.0.1:31000/lool/convert-to/png", host: "collabora.iphodase.fr"
2019/02/09 17:47:26 [error] 1153#1153: *6482 connect() failed (111: Connection refused) while connecting to upstream, client: 2001:41d0:8:15ba::1, server: collabora.iphodase.fr, request: "POST /lool/convert-to/png HTTP/1.1", upstream: "https://[::1]:31000/lool/convert-to/png", host: "collabora.iphodase.fr"
2019/02/09 17:47:29 [error] 1153#1153: *6488 no live upstreams while connecting to upstream, client: 2001:41d0:8:15ba::1, server: collabora.iphodase.fr, request: "GET /hosting/discovery HTTP/1.1", upstream: "https://localhost/hosting/discovery", host: "collabora.iphodase.fr"
2019/02/09 17:47:30 [error] 1153#1153: *6490 connect() failed (111: Connection refused) while connecting to upstream, client: 2001:41d0:8:15ba::1, server: collabora.iphodase.fr, request: "GET /hosting/discovery HTTP/1.1", upstream: "https://[::1]:31000/hosting/discovery", host: "collabora.iphodase.fr"
2019/02/09 17:47:30 [error] 1153#1153: *6490 connect() failed (111: Connection refused) while connecting to upstream, client: 2001:41d0:8:15ba::1, server: collabora.iphodase.fr, request: "GET /hosting/discovery HTTP/1.1", upstream: "https://127.0.0.1:31000/hosting/discovery", host: "collabora.iphodase.fr"
2019/02/09 17:53:51 [error] 1152#1152: *6598 open() "/usr/share/nginx/html/favicon.ico" failed (2: No such file or directory), client: 92.129.89.139, server: collabora.iphodase.fr, request: "GET /favicon.ico HTTP/2.0", host: "collabora.iphodase.fr"

NGINX tout court sur la même heure

2019/02/09 17:47:14 [error] 1151#1151: ocsp.int-x3.letsencrypt.org could not be resolved (110: Operation timed out) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org
2019/02/09 17:47:55 [info] 9411#9411: Using 32768KiB of shared memory for nchan in /etc/nginx/nginx.conf:64
2019/02/09 17:47:55 [warn] 9411#9411: could not build optimal variables_hash, you should increase either variables_hash_max_size: 1024 or variables_hash_bucket_size: 64; ignoring variables_hash_bucket_size

La différence c’est que maintenant j’ai un message dans NEXCLOUD

Erreur interne du serveur

Le serveur est incapable d’exécuter votre requête.

Si cela se reproduit, veuillez envoyer les détails techniques ci-dessous à l’administrateur du serveur.

Le fichier journal du serveur peut fournir plus de renseignements.

Renseignements techniques