Etherpad-lite plugins

Salut,

j’essaye depuis qlq heures d’augmenter mon etherpad via des plugin mais y’a rien a faire ça veut pas :confused:

j’ai d’abord essayé d’activer l’admin de etherpad en suivant ces infos : Etherpad Lite package
mais l’admin est “vide”, je ne peux rien faire dedans.

ensuite j’ai essayé d’installer des plugins via npm install dans /var/www/etherpadlite mais a chaque plugin mon pad devient inscessible avec une erreur bad gateway
ex:
npm install ep_copy_past_images systemctl restart etherpad-lite

les plugins que j’ai testé :

  • ep_copy_paste_images
  • ep_adminpads
  • ep_pad-lister

est-ce qu’il est au moins possible d’installer un plugin avec etherpad-lite sous YNH ou bien je perds mon temps ?

mes logs nginx au moment du redemarage du service etherpadlite et quand je tente d’accéder a un pad.

2016/03/11 19:28:18 [error] 11129#0: *315 upstream prematurely closed connection while reading response header from upstream, client: 82.230.62.145, server: esadhar.net, request: "GET /pad/socket.io/?EIO=3&transport=polling&t=1457720875507-14&sid=DDnd9UujYvXCdvpmAAAB HTTP/1.1", upstream: "http://127.0.0.1:9001/socket.io/?EIO=3&transport=polling&t=1457720875507-14&sid=DDnd9UujYvXCdvpmAAAB", host: "esadhar.net", referrer: "https://esadhar.net/pad/p/osp-usg-2016"

2016/03/11 19:28:18 [error] 11129#0: *315 connect() failed (111: Connection refused) while connecting to upstream, client: 82.230.62.145, server: esadhar.net, request: "POST /pad/socket.io/?EIO=3&transport=polling&t=1457720898902-15&sid=DDnd9UujYvXCdvpmAAAB HTTP/1.1", upstream: "http://127.0.0.1:9001/socket.io/?EIO=3&transport=polling&t=1457720898902-15&sid=DDnd9UujYvXCdvpmAAAB", host: "esadhar.net", referrer: "https://esadhar.net/pad/p/osp-usg-2016"

2016/03/11 19:28:20 [error] 11129#0: *315 connect() failed (111: Connection refused) while connecting to upstream, client: 82.230.62.145, server: esadhar.net, request: "GET /pad/socket.io/?EIO=3&transport=polling&t=1457720900076-16 HTTP/1.1", upstream: "http://127.0.0.1:9001/socket.io/?EIO=3&transport=polling&t=1457720900076-16", host: "esadhar.net", referrer: "https://esadhar.net/pad/p/osp-usg-2016"

2016/03/11 19:28:21 [error] 11129#0: *315 connect() failed (111: Connection refused) while connecting to upstream, client: 82.230.62.145, server: esadhar.net, request: "GET /pad/socket.io/?EIO=3&transport=polling&t=1457720901295-17 HTTP/1.1", upstream: "http://127.0.0.1:9001/socket.io/?EIO=3&transport=polling&t=1457720901295-17", host: "esadhar.net", referrer: "https://esadhar.net/pad/p/osp-usg-2016"

2016/03/11 19:28:26 [error] 11129#0: *315 connect() failed (111: Connection refused) while connecting to upstream, client: 82.230.62.145, server: esadhar.net, request: "GET /pad/socket.io/?EIO=3&transport=polling&t=1457720906337-18 HTTP/1.1", upstream: "http://127.0.0.1:9001/socket.io/?EIO=3&transport=polling&t=1457720906337-18", host: "esadhar.net", referrer: "https://esadhar.net/pad/p/osp-usg-2016"

2016/03/11 19:28:30 [error] 11129#0: *315 connect() failed (111: Connection refused) while connecting to upstream, client: 82.230.62.145, server: esadhar.net, request: "GET /pad/p/osp-usg-2016 HTTP/1.1", upstream: "http://127.0.0.1:9001/p/osp-usg-2016", host: "esadhar.net"

2016/03/11 19:28:54 [error] 11129#0: *315 connect() failed (111: Connection refused) while connecting to upstream, client: 82.230.62.145, server: esadhar.net, request: "GET /pad/p/osp-usg-2016 HTTP/1.1", upstream: "http://127.0.0.1:9001/p/osp-usg-2016", host: "esadhar.net"

qlq heures plus tard, toujours pas de succès

j’ai édité mon /etc/nginx/conf.d/domain.tld.d/etherpadlite.conf

location /pad/ {
       rewrite                ^/pad$ /pad/ permanent;
       #rewrite               /pad/(.*) /pad/$1 break;
       proxy_pass             http://localhost:9001/;
       proxy_redirect         / /pad/;
       proxy_set_header       Host $host;
       proxy_buffering off;
}

# trying here to make nginx running fine withe etherpad plugins
# https://github.com/ether/etherpad-lite/wiki/How-to-put-Etherpad-Lite-behind-a-reverse-Proxy#from-subdirectory-url
location /pad/socket.io {
      rewrite                /pad/socket.io/(.*) /socket.io/$1 break;
      proxy_pass             http://localhost:9001/;
      proxy_redirect          / /pad/;
      proxy_set_header       Host $host;
      proxy_buffering off;
      proxy_set_header X-Real-IP $remote_addr;  # http://wiki.nginx.org/HttpProxyModule
      proxy_set_header X-Forwarded-For $remote_addr; # EP logs to show the actual remote IP
      proxy_set_header Host $host;  # pass the host header
      proxy_http_version 1.1;  # recommended with keepalive connections
      # WebSocket proxying - from http://nginx.org/en/docs/http/websocket.html
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection $connection_upgrade;
      #proxy_set_header Connection "upgrade";

}

location /static {
      rewrite /static/(.*) /static/$1 break;
      proxy_pass http://localhost:9001/;
      proxy_set_header Host $host;
      proxy_buffering off;
}

et /etcnginx/conf.d/domain.tld.conf

# we're in the http context here
map $http_upgrade $connection_upgrade {
  default upgrade;
  ''      close;
}

j’ai aussi essayé de faire npm install ep_markdownify depuis /var/www/etherpadlite/src/
plutot que depuis /var/www/etherpadlite/

sans résultats

en passant l’admin ne marche pas non plus, je peux y accéder mais les pages sont vides. J’ai comme l’impression que c’est lié …

Salut,

Vérifie que les répertoires des plugins installés (dans /var/www/etherpadlite/node_modules/) ont bien le bon propriétaire (utilisateur www-data et non root).

J’ai installé ep_adminpads et ep_pad-lister et j’avais eu ce souci là également. :yum:

Par contre le panel admin ne fonctionne pas non plus chez moi. (Mais le panel d’ep_adminpads marche très bien !)

Super!
Merci SiM, c’était bien ça le problème. Tellement évident que je n’y ai pas pensé.
Par contre /pad/admin est maintenant inaccessible, pas le courage de me replonger dans la config nginx maintenant. Et plusieurs plugin ne fonctionne pas, notament a cause de la conf nginx, on vera ça plus tard.