Serious error! nodebb.org is in redirect loop (which prevents admin plugins pages from loading)

[jongarrison]

I just upgraded to v1.2.1 and I cannot get to the admin plugins page. In my logs I am seeing a redirect loop with the nodebb.org server while it tries to get available plugin data. Unfortunately this error prevents me from even viewing the local installed plugins in the system:

Both:
https://packages.nodebb.org/api/v1/plugins?version=1.2.1
https://packages.nodebb.org/api/v1/plugins
are in a 301 redirect loop

Errors from my server logs:
(node:24228) Warning: Possible EventEmitter memory leak detected. 11 pipe listeners added. Use emitter.setMaxListeners() to increase limit
(node:24228) Warning: Possible EventEmitter memory leak detected. 11 end listeners added. Use emitter.setMaxListeners() to increase limit
(node:24228) Warning: Possible EventEmitter memory leak detected. 11 pipe listeners added. Use emitter.setMaxListeners() to increase limit
(node:24228) Warning: Possible EventEmitter memory leak detected. 11 end listeners added. Use emitter.setMaxListeners() to increase limit
9/11 18:13 [24228] - error: Error parsing plugins : Exceeded maxRedirects. Probably stuck in a redirect loop https://packages.nodebb.org/api/v1/plugins?version=1.2.1
9/11 18:13 [24228] - error: Error parsing plugins : Exceeded maxRedirects. Probably stuck in a redirect loop https://packages.nodebb.org/api/v1/plugins

Is anyone else seeing this? Any ideas?

[pichalite]

@jongarrison yeah getting the same error. Looks like nbbpm is having some issues.

[pichalite]

@jongarrison seems to be OK now.

[julian]

Sorry about that! Was doing some server migration on the nbbpm server earlier today, which may have affected the plugins page. As @pichalite says, should be better now.

[jongarrison]

@julian Thanks.

Should something be changed in the acp so that a remote error doesn't prevent management of NodeBB installs everywhere?

[julian]

NodeBB does gracefully handle when nbbpm is down. In this particular scenario, nbbpm was looping infinitely, and so the request never seemed to resolve

[jongarrison]

@julian Yikes!