Etherpad-lite: ETIMEDOUT 104.130.77.39:443

[kingmook]

When attempting to access the plugin manager in admin I'm getting a timeout in the error log.

Error: connect ETIMEDOUT 104.130.77.39:443
    at Object.exports._errnoException (util.js:1026:11)
    at exports._exceptionWithHostPort (util.js:1049:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1081:14)

I believe 104.130.77.39:443 is the npm lookup for etherpad plugins. It has worked in the past with my production server, but today I don't seem to be able to ping. Is this service temporarily down or has this service been moved?

[Gared]

I know you're right. This service is temporarily down since yesterday. Hope I'll get it online again soon.

[kingmook]

Thanks for the quick check-in. I'm not hurting for it, and frankly happy it's not something on my end for a change.

[eviltel]

It seems to be the same problem with the plugin list link http://static.etherpad.org/plugins.html which I found on the Wiki page https://github.com/ether/etherpad-lite/wiki/Plugin,-a-list.
static.etherpad.org resolvs to the same address.

[Thireus]

Still down, is there another alternative?

[Gared]

@Thireus You can install those plugins on your cli:

npm install ep_PLUGINNAME

[Aur0r]

Just if someone didn't know: In the meanwhile if you can't figure out the name of a plugin there is a json blob that can be used to figure out the needed plugin names. I hope this one is up-to-date.

[Thireus]

Also, "https://www.npmjs.com/search?q=ep_" is where you get the plugin list. Anything starting with "ep_" should be for Etherpad.

[Gared]

The server is up again!

[theredfish]

Thank you for your work!

[dbareiro]

Hi!

It looks like the service is down again:

Jan  9 18:49:39 conference node[392]: #033[33m[2017-01-09 18:49:39.272] [WARN] console - #033[39m{ Error: connect ETIMEDOUT 104.130.77.39:443 
Jan  9 18:49:39 conference node[392]: at Object.exports._errnoException (util.js:1022:11) 
Jan  9 18:49:39 conference node[392]: at exports._exceptionWithHostPort (util.js:1045:20) 
Jan  9 18:49:39 conference node[392]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1087:14) 
Jan  9 18:49:39 conference node[392]: code: 'ETIMEDOUT', 
Jan  9 18:49:39 conference node[392]: errno: 'ETIMEDOUT', 
Jan  9 18:49:39 conference node[392]: syscall: 'connect', 
Jan  9 18:49:39 conference node[392]: address: '104.130.77.39', 
Jan  9 18:49:39 conference node[392]: port: 443 } 
Jan  9 18:49:39 conference node[392]: Error: connect ETIMEDOUT 104.130.77.39:443 
Jan  9 18:49:39 conference node[392]: at Object.exports._errnoException (util.js:1022:11) 
Jan  9 18:49:39 conference node[392]: at exports._exceptionWithHostPort (util.js:1045:20) 
Jan  9 18:49:39 conference node[392]: at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1087:14)

Kind regards,
Daniel

[Gared]

See #3092

[dbareiro]

Thanks for the prompt resply, Gared. I'll be watching the news on #3092.

Kind regards,
Daniel