Installer Collabora avec Nextcloud

Aleks nous a proposé de créer une page de documentation dans ce post

Mais pour le moment il n’y pas eu de volontaire ou une personne avec les compétences pour le faire.

1 Like

J’ai le même souci que Jaxom, le message “c’est embarassant”, puis après avoir relancé le service Docker, j’ai “502 Bad Gateway”. J’ai pas encore essayé de rebooter…

et voilà !! => https://github.com/YunoHost/doc/pull/848

Salut,
Où on en est avec les app collabora ? Il y a 2 app pour yunohost :

  • https://github.com/aymhce/collaboradocker_ynh : utilise docker, a fonctionné un temps pour moi mais je n’arrive plus à la faire marcher depuis un moment. J’ai cru comprendre que c’était compliqué d’utiliser docker… est-ce que cette app est encore en vie ? Est-ce qu’elle est laissée tombée pour la 2ème ?
  • https://github.com/YunoHost-Apps/collaboraonline_ynh : sans docker, mais elle n’a pas l’air de fonctionner pour le moment. Pareil, est-ce qu’elle est active ?

Ou est-ce qu’il n’y a juste personne qui a le temps/la motivation pour bosser dessus ?
Collabora couplé avec Nextcloud est super pratique, je m’y étais habitué, du coup je suis un peu frustré de ne plus l’avoir… Même si j’imagine bien le boulot que c’est à packager.

Salut je viens de faire l’install NEXCLOUD puis collaboraonline sur mon instance en 3.3.4
Tout fonctionne, donc je dirais pas besoin de docker.

ah , bah je viens de tenter, ça s’installe pas sur mon serveur en 3.4.2.2 ;
quant à la version docker, je ne tente meme pas , dernière fois que j’ai tenter un docker truc sur mon serveur ça a tout cassé

T’as bien le sous domaine dédié? collabora.mondomaine avec le let’s encrypt?
et fait le redémarrage pour finir l’install de nextcloud?
Non car d’habitude chaque nouvelle appli j’ai que des pines et pour une fois j’ai réussi à me débrouiller.

Salut à tous, j’ai forké mon projet sur Yunohost-apps pour une meilleure maintenance (je n’ai pas trop le temps de m’y consacrer) : https://github.com/YunoHost-Apps/collaboradocker_ynh

1 Like

@homerc : ouep un sous domaine dédié, LE OK
quant à nextcloud il tourne depuis plusieurs années déjà,
j’ai une action à faire dessus ?
en fait l’install freeze au moment de la validation des ports qui sont déjà ouvert, je peux recommencer et te poser le log si tu veux

Bon pas sûr que je puisse t’aider mais dans tous les cas un oeil extérieur c’est jamais mauvais.

hey ! Par ici ca marche pas :s quand j’essiae d’ouvrir un document dans nextcloud, il y a une icone de chargement qui tourne à l’infini.

docker à l’air de fonctionner. Voici ce qui semble étrange dans nginx :

  1. /var/log/nginx/collabora.qlfacab.noho.st-error.log
    2019/02/26 19:56:06 [error] 1496#1496: *32 peer closed connection in SSL handshake while SSL handshaking to upstream, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "POST /lool/convert-to/png HTTP/1.1", upstream: "https://127.0.0.1:31000/lool/convert-to/png", host: "collabora.qlfacab.noho.st"
    2019/02/26 19:56:06 [error] 1496#1496: *33 upstream prematurely closed connection while reading response header from upstream, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "POST /lool/convert-to/png HTTP/1.1", upstream: "https://[::1]:31000/lool/convert-to/png", host: "collabora.qlfacab.noho.st"
    2019/02/26 19:56:06 [error] 1496#1496: *33 no live upstreams while connecting to upstream, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "POST /lool/convert-to/png HTTP/1.1", upstream: "https://localhost/lool/convert-to/png", host: "collabora.qlfacab.noho.st"
    2019/02/26 19:56:06 [error] 1496#1496: *32 peer closed connection in SSL handshake (104: Connection reset by peer) while SSL handshaking to upstream, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "POST /lool/convert-to/png HTTP/1.1", upstream: "https://[::1]:31000/lool/convert-to/png", host: "collabora.qlfacab.noho.st"
    2019/02/26 19:56:07 [error] 1499#1499: *41 peer closed connection in SSL handshake (104: Connection reset by peer) while SSL handshaking to upstream, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/discovery HTTP/1.1", upstream: "https://127.0.0.1:31000/hosting/discovery", host: "collabora.qlfacab.noho.st"
    2019/02/26 19:56:07 [error] 1499#1499: *41 peer closed connection in SSL handshake (104: Connection reset by peer) while SSL handshaking to upstream, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/discovery HTTP/1.1", upstream: "https://[::1]:31000/hosting/discovery", host: "collabora.qlfacab.noho.st"
    2019/02/26 19:56:08 [error] 1496#1496: *44 peer closed connection in SSL handshake (104: Connection reset by peer) while SSL handshaking to upstream, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/discovery HTTP/1.1", upstream: "https://127.0.0.1:31000/hosting/discovery", host: "collabora.qlfacab.noho.st"
    2019/02/26 19:56:08 [error] 1496#1496: *44 no live upstreams while connecting to upstream, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/discovery HTTP/1.1", upstream: "https://localhost/hosting/discovery", host: "collabora.qlfacab.noho.st"
    2019/02/26 19:56:44 [error] 1496#1496: *63 open() "/usr/share/nginx/html/favicon.ico" failed (2: No such file or directory), client: 2a01:cb04:6d4:3500:d8cd:87f8:94fb:714c, server: collabora.qlfacab.noho.st, request: "GET /favicon.ico HTTP/2.0", host: "collabora.qlfacab.noho.st"
    2019/02/26 20:00:04 [error] 1499#1499: *86 open() "/usr/share/nginx/html/hosting/capabilities" failed (2: No such file or directory), client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities HTTP/1.1", host: "collabora.qlfacab.noho.st"
    2019/02/26 20:11:42 [error] 1544#1544: *54 peer closed connection in SSL handshake (104: Connection reset by peer) while SSL handshaking to upstream, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "POST /lool/convert-to/png HTTP/1.1", upstream: "https://127.0.0.1:31000/lool/convert-to/png", host: "collabora.qlfacab.noho.st"
    2019/02/26 20:11:42 [error] 1544#1544: *54 peer closed connection in SSL handshake (104: Connection reset by peer) while SSL handshaking to upstream, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "POST /lool/convert-to/png HTTP/1.1", upstream: "https://[::1]:31000/lool/convert-to/png", host: "collabora.qlfacab.noho.st"
    2019/02/26 20:33:56 [error] 11045#11045: *214 directory index of "/usr/share/nginx/html/hosting/capabilities/" is forbidden, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities/ HTTP/1.1", host: "collabora.qlfacab.noho.st"
    2019/02/26 21:03:22 [error] 4811#4811: *91 directory index of "/usr/share/nginx/html/hosting/capabilities/" is forbidden, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities/ HTTP/1.1", host: "collabora.qlfacab.noho.st"
    2019/02/26 21:27:37 [error] 3994#3994: *44 directory index of "/usr/share/nginx/html/hosting/capabilities/" is forbidden, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities/ HTTP/1.1", host: "collabora.qlfacab.noho.st"
    2019/02/26 21:33:50 [error] 1551#1551: *111 open() "/usr/share/nginx/html/favicon.ico" failed (2: No such file or directory), client: 82.123.19.216, server: collabora.qlfacab.noho.st, request: "GET /favicon.ico HTTP/2.0", host: "collabora.qlfacab.noho.st"
    2019/02/26 21:45:06 [error] 11195#11195: *353 directory index of "/usr/share/nginx/html/hosting/capabilities/" is forbidden, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities/ HTTP/1.1", host: "collabora.qlfacab.noho.st"
    2019/02/26 23:00:04 [error] 1495#1495: *880 directory index of "/usr/share/nginx/html/hosting/capabilities/" is forbidden, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities/ HTTP/1.1", host: "collabora.qlfacab.noho.st"
    2019/02/27 00:15:05 [error] 1507#1507: *1279 directory index of "/usr/share/nginx/html/hosting/capabilities/" is forbidden, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities/ HTTP/1.1", host: "collabora.qlfacab.noho.st"
    2019/02/27 01:30:04 [error] 1502#1502: *2125 directory index of "/usr/share/nginx/html/hosting/capabilities/" is forbidden, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities/ HTTP/1.1", host: "collabora.qlfacab.noho.st"
    2019/02/27 02:45:04 [error] 1507#1507: *2614 directory index of "/usr/share/nginx/html/hosting/capabilities/" is forbidden, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities/ HTTP/1.1", host: "collabora.qlfacab.noho.st"
    2019/02/27 04:00:05 [error] 1507#1507: *3084 directory index of "/usr/share/nginx/html/hosting/capabilities/" is forbidden, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities/ HTTP/1.1", host: "collabora.qlfacab.noho.st"
    2019/02/27 05:15:03 [error] 1507#1507: *3557 directory index of "/usr/share/nginx/html/hosting/capabilities/" is forbidden, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities/ HTTP/1.1", host: "collabora.qlfacab.noho.st"
    2019/02/27 06:15:05 [error] 1502#1502: *3938 directory index of "/usr/share/nginx/html/hosting/capabilities/" is forbidden, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities/ HTTP/1.1", host: "collabora.qlfacab.noho.st"
    2019/02/27 07:30:05 [error] 1507#1507: *4405 directory index of "/usr/share/nginx/html/hosting/capabilities/" is forbidden, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities/ HTTP/1.1", host: "collabora.qlfacab.noho.st"
    2019/02/27 08:45:04 [error] 1497#1497: *4872 directory index of "/usr/share/nginx/html/hosting/capabilities/" is forbidden, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities/ HTTP/1.1", host: "collabora.qlfacab.noho.st"
    2019/02/27 09:45:05 [error] 1497#1497: *5112 directory index of "/usr/share/nginx/html/hosting/capabilities/" is forbidden, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities/ HTTP/1.1", host: "collabora.qlfacab.noho.st"
    2019/02/27 11:00:04 [error] 1502#1502: *5407 directory index of "/usr/share/nginx/html/hosting/capabilities/" is forbidden, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities/ HTTP/1.1", host: "collabora.qlfacab.noho.st"
    2019/02/27 12:15:04 [error] 1497#1497: *5420 directory index of "/usr/share/nginx/html/hosting/capabilities/" is forbidden, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities/ HTTP/1.1", host: "collabora.qlfacab.noho.st"
    2019/02/27 13:15:05 [error] 1502#1502: *5431 directory index of "/usr/share/nginx/html/hosting/capabilities/" is forbidden, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities/ HTTP/1.1", host: "collabora.qlfacab.noho.st"
    2019/02/27 14:30:04 [error] 1502#1502: *5432 directory index of "/usr/share/nginx/html/hosting/capabilities/" is forbidden, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities/ HTTP/1.1", host: "collabora.qlfacab.noho.st"
    2019/02/27 15:45:04 [error] 1502#1502: *5434 directory index of "/usr/share/nginx/html/hosting/capabilities/" is forbidden, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities/ HTTP/1.1", host: "collabora.qlfacab.noho.st"
    2019/02/27 17:00:04 [error] 1495#1495: *5459 directory index of "/usr/share/nginx/html/hosting/capabilities/" is forbidden, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities/ HTTP/1.1", host: "collabora.qlfacab.noho.st"
    2019/02/27 18:15:04 [error] 1507#1507: *5594 directory index of "/usr/share/nginx/html/hosting/capabilities/" is forbidden, client: 2001:41d0:8:782f::1, server: collabora.qlfacab.noho.st, request: "GET /hosting/capabilities/ HTTP/1.1", host: "collabora.qlfacab.noho.st" ```
    
    

Pour résoudre la première erreur, j’ai créé le fichier capabilities et j’ai fait chown www-data capabilities puis chmod 700 capabilities

  1. /var/log/nginx/error.log
src/store/memory/memstore.c:1616: nchan_store_exit_worker: Assertion `0' failed.
2019/02/26 20:44:30 [alert] 1538#1538: worker process 11978 exited on signal 6
2019/02/26 20:44:30 [alert] 1538#1538: shared memory zone "memstore" was locked by 11978
2019/02/26 20:44:28 [error] 11979#11979: MEMSTORE:05: my procslot not found! I don't know what to do!
ker process is shutting down: /build/nginx-0TiIP5/nginx-1.10.3/debian/modules/nchan/src/store/memory/memstore.c:1616: nchan_store_exit_worker: Assertion `0' failed.
2019/02/26 20:44:30 [alert] 1538#1538: worker process 11979 exited on signal 6
2019/02/26 20:44:30 [alert] 1538#1538: shared memory zone "memstore" was locked by 11979
2019/02/26 20:44:28 [error] 11980#11980: MEMSTORE:06: my procslot not found! I don't know what to do!
ker process is shutting down: /build/nginx-0TiIP5/nginx-1.10.3/debian/modules/nchan/src/store/memory/memstore.c:1616: nchan_store_exit_worker: Assertion `0' failed.
2019/02/26 20:44:30 [alert] 1538#1538: worker process 11980 exited on signal 6
2019/02/26 20:44:30 [alert] 1538#1538: shared memory zone "memstore" was locked by 11980
2019/02/26 20:45:38 [info] 686#686: Using 32768KiB of shared memory for nchan in /etc/nginx/nginx.conf:64
2019/02/26 20:49:18 [notice] 3582#3582: signal process started
2019/02/26 20:58:50 [notice] 4800#4800: signal process started
2019/02/26 21:05:26 [info] 748#748: Using 32768KiB of shared memory for nchan in /etc/nginx/nginx.conf:64
2019/02/26 21:12:54 [info] 636#636: Using 32768KiB of shared memory for nchan in /etc/nginx/nginx.conf:64
2019/02/26 21:15:12 [notice] 3440#3440: signal process started
2019/02/26 21:16:24 [notice] 3600#3600: signal process started
2019/02/26 21:18:24 [info] 692#692: Using 32768KiB of shared memory for nchan in /etc/nginx/nginx.conf:64
2019/02/26 21:26:43 [notice] 3967#3967: signal process started
2019/02/26 21:28:50 [info] 794#794: Using 32768KiB of shared memory for nchan in /etc/nginx/nginx.conf:64
2019/02/26 21:38:39 [notice] 5808#5808: signal process started
2019/02/26 21:42:54 [notice] 11169#11169: signal process started
2019/02/26 21:48:16 [error] 11196#11196: MEMSTORE:03: my procslot not found! I don't know what to do!
ker process is shutting down: /build/nginx-0TiIP5/nginx-1.10.3/debian/modules/nchan/src/store/memory/memstore.c:1616: nchan_store_exit_worker: Assertion `0' failed.
2019/02/26 21:48:16 [alert] 1535#1535: worker process 11196 exited on signal 6
2019/02/26 21:48:16 [alert] 1535#1535: shared memory zone "memstore" was locked by 11196
2019/02/26 21:48:16 [error] 11195#11195: MEMSTORE:02: my procslot not found! I don't know what to do!
ker process is shutting down: /build/nginx-0TiIP5/nginx-1.10.3/debian/modules/nchan/src/store/memory/memstore.c:1616: nchan_store_exit_worker: Assertion `0' failed.
2019/02/26 21:48:16 [alert] 1535#1535: worker process 11195 exited on signal 6
2019/02/26 21:48:16 [alert] 1535#1535: shared memory zone "memstore" was locked by 11195
2019/02/26 21:48:16 [error] 11197#11197: MEMSTORE:08: my procslot not found! I don't know what to do!
ker process is shutting down: /build/nginx-0TiIP5/nginx-1.10.3/debian/modules/nchan/src/store/memory/memstore.c:1616: nchan_store_exit_worker: Assertion `0' failed.
2019/02/26 21:48:16 [alert] 1535#1535: worker process 11197 exited on signal 6
2019/02/26 21:48:16 [alert] 1535#1535: shared memory zone "memstore" was locked by 11197
2019/02/26 21:49:18 [info] 769#769: Using 32768KiB of shared memory for nchan in /etc/nginx/nginx.conf:64
2019/02/27 00:06:02 [error] 1507#1507: 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/27 01:26:57 [error] 1495#1495: 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/27 02:07:41 [error] 1502#1502: 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/27 07:07:41 [error] 1507#1507: 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/27 08:08:17 [error] 1497#1497: 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/27 08:55:35 [crit] 1497#1497: *4938 SSL_do_handshake() failed (SSL: error:1417D18C:SSL routines:tls_process_client_hello:version too low) while SSL handshaking, client: 208.93.152.17, server: 0.0.0.0:443
2019/02/27 10:12:45 [error] 1495#1495: 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/27 10:49:47 [error] 1502#1502: 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/27 10:53:57 [crit] 1502#1502: *5406 SSL_do_handshake() failed (SSL: error:1417D18C:SSL routines:tls_process_client_hello:version too low) while SSL handshaking, client: 198.108.66.240, server: 0.0.0.0:443
2019/02/27 16:39:45 [crit] 1502#1502: *5437 SSL_do_handshake() failed (SSL: error:1417D18C:SSL routines:tls_process_client_hello:version too low) while SSL handshaking, client: 216.218.206.67, server: 0.0.0.0:443
2019/02/27 17:34:27 [error] 1497#1497: 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/27 18:26:52 [error] 1507#1507: 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/27 18:39:56 [error] 1497#1497: 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/27 19:27:06 [error] 1507#1507: ocsp.int-x3.letsencrypt.org could not be resolved (110: Operation timed out) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org
  1. /var/log/nginx/qlfacab.noho.st-error.log
2019/02/26 21:45:14 [error] 11197#11197: *187 open() "/var/www/nextcloud//apps/richdocuments/js/templates.js" failed (2: No such file or directory), client: 2a01:cb04:6d4:3500:d8cd:87f8:94fb:714c, server: qlfacab.noho.st, request: "GET /nextcloud/apps/richdocuments/js/templates.js?v=44084e92-9 HTTP/2.0", host: "qlfacab.noho.st"
2019/02/26 21:48:16 [error] 11197#11197: *187 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 2a01:cb04:6d4:3500:d8cd:87f8:94fb:714c, server: qlfacab.noho.st, request: "GET /nextcloud/ocs/v2.php/apps/notifications/api/v2/notifications HTTP/2.0", upstream: "fastcgi://unix:/var/run/php/php7.0-fpm-nextcloud.sock:", host: "qlfacab.noho.st"
2019/02/26 21:53:10 [error] 1507#1507: *1 open() "/var/www/nextcloud//apps/richdocuments/js/templates.js" failed (2: No such file or directory), client: 2a01:cb04:6d4:3500:d8cd:87f8:94fb:714c, server: qlfacab.noho.st, request: "GET /nextcloud/apps/richdocuments/js/templates.js?v=44084e92-9 HTTP/2.0", host: "qlfacab.noho.st"
2019/02/26 21:55:25 [error] 1507#1507: *110 open() "/var/www/nextcloud//apps/richdocuments/js/templates.js" failed (2: No such file or directory), client: 2a01:cb04:6d4:3500:d8cd:87f8:94fb:714c, server: qlfacab.noho.st, request: "GET /nextcloud/apps/richdocuments/js/templates.js?v=44084e92-9 HTTP/2.0", host: "qlfacab.noho.st"
2019/02/26 21:57:34 [error] 1502#1502: *159 open() "/var/www/nextcloud//apps/richdocuments/js/templates.js" failed (2: No such file or directory), client: 2a01:cb04:6d4:3500:9ddf:f861:32:137f, server: qlfacab.noho.st, request: "GET /nextcloud/apps/richdocuments/js/templates.js?v=44084e92-9 HTTP/2.0", host: "qlfacab.noho.st"
2019/02/27 00:12:46 [error] 1507#1507: *1184 open() "/var/www/nextcloud//apps/richdocuments/js/templates.js" failed (2: No such file or directory), client: 2a01:cb04:6d4:3500:9ddf:f861:32:137f, server: qlfacab.noho.st, request: "GET /nextcloud/apps/richdocuments/js/templates.js?v=44084e92-9 HTTP/2.0", host: "qlfacab.noho.st"
2019/02/27 17:34:21 [error] 1502#1502: *5461 open() "/var/www/nextcloud//apps/richdocuments/js/templates.js" failed (2: No such file or directory), client: 82.226.14.246, server: qlfacab.noho.st, request: "GET /nextcloud/apps/richdocuments/js/templates.js?v=44084e92-9 HTTP/2.0", host: "qlfacab.noho.st"
2019/02/27 18:29:48 [error] 1507#1507: *5595 open() "/var/www/nextcloud//apps/richdocuments/js/templates.js" failed (2: No such file or directory), client: 82.226.14.246, server: qlfacab.noho.st, request: "GET /nextcloud/apps/richdocuments/js/templates.js?v=44084e92-9 HTTP/2.0", host: "qlfacab.noho.st"
2019/02/27 18:39:36 [error] 1507#1507: *5595 open() "/var/www/nextcloud//apps/richdocuments/js/templates.js" failed (2: No such file or directory), client: 82.226.14.246, server: qlfacab.noho.st, request: "GET /nextcloud/apps/richdocuments/js/templates.js?v=44084e92-9 HTTP/2.0", host: "qlfacab.noho.st"
2019/02/27 19:21:39 [error] 1497#1497: *5859 open() "/var/www/nextcloud//apps/richdocuments/js/templates.js" failed (2: No such file or directory), client: 82.226.14.246, server: qlfacab.noho.st, request: "GET /nextcloud/apps/richdocuments/js/templates.js?v=44084e92-9 HTTP/2.0", host: "qlfacab.noho.st"
2019/02/27 19:22:48 [error] 1497#1497: *5859 open() "/var/www/nextcloud//apps/richdocuments/js/templates.js" failed (2: No such file or directory), client: 82.226.14.246, server: qlfacab.noho.st, request: "GET /nextcloud/apps/richdocuments/js/templates.js?v=44084e92-9 HTTP/2.0", host: "qlfacab.noho.st"
2019/02/27 19:23:18 [error] 1497#1497: *5859 open() "/var/www/nextcloud//apps/richdocuments/js/templates.js" failed (2: No such file or directory), client: 82.226.14.246, server: qlfacab.noho.st, request: "GET /nextcloud/apps/richdocuments/js/templates.js?v=44084e92-9 HTTP/2.0", host: "qlfacab.noho.st"

Voilààà si quelqu’un a une idée o/ Je suis sur un serveur ovh 64bit avec yunohost à jour.

ps : merci de ouf pour intégrer collabora à yunohost. Si c’est bien intégré un jour, on pourra remplacer touuutes la suite goole avec yunohost en deux clics :open_mouth: trop bien :smiley:

J’ai malheureusement la même erreur que @Petitminion :frowning:
J’ai essayé les mêmes manips, mais sans succès non plus.

Peut-être qu’il y a des fichiers non servis à cause de la config de nginx mais je ne trouve pas quoi malheureusement !

ps @Petitminion , dans tes logs, l’erreur vient peut-être du double slash :

/var/www/nextcloud//apps/richdocuments/js/templates.js

tu as pu trouver?
J’ai le même soucis et non ne trouve pas :confused:

Non malheureusement :frowning:

Ce qui est frustrant c’est que j’ai suivi les tutos là https://www.c-rieger.de/nextcloud-and-collabora-nginx/ et que ça fonctionne sur une installation basique de nextcloud (sans yunohost donc).

J’essaye de checker un peu les différences et que ça ne saute pas aux yeux pour l’instant :frowning:

Je vais rester sans yunohost pour l’instant, il faut que je réinstalle la VM pour tester les différentes confs avant de la mettre sur un serveur “de prod” :slight_smile:

Je présume que le soucis provient d’une conf nginx, mais je ne trouve pas pour l’instant.

Merci pour ton retour.
je continu de regarder, là il y a des MAJ NGINX et docker donc je viens de tout lancer.
Si ça marche je te remet un message. Ce qui m’ennuie c’est que ça a fonctionné avant des MAJ sur Yuno, mais comme ces MAJ touchent un peu tout c’est difficile de trouver le “problème”

1 Like

@gtrdblt1Bon ben ça n’a rien changé…A suivre…

Salut,
Grâce à @ljf, j’ai réussi à installer collabora avec Nextcloud, comme ça :

sudo yunohost app install https://github.com/YunoHost-Apps/collabora_ynh/tree/testing --debug --no-remove-on-failure

Ça installe la version testing, dont l’installation foire à cause d’un service qui ne se lance pas du premier coup à la fin du script, donc le --no-remove-on-failure permet d’éviter que le script ne la désinstalle à cause de cette erreur. Ensuite il suffit d’installer l’application collabora sur nextcloud, et ça marche.
Bien sûr, à utiliser à vos risques et périls sur un serveur en prod…

4 Likes

Merci je vais faire les sauvegarde qui vont bien désinstaller et réinstaller comme ça.

Slt,

Je suis bien intéressé par ta méthode mais je viens de tester ça ne fonctionne pas chez moi …
Est ce qu’on peut lancer le script comme ça ou ça nécessite de faire quelque chose avant (ajout de domaine ou autre…)

Il faut bien installer l’application collabora sur un domaine dédié, donc par exemple ajouter un sous-domaine dans l’interface yunohost (collabora.domaine.truc), et installer collabora dessus.