Error access Plugin ACP with 2.4.5

phenomlab

@DownPW I could be wrong here but after thinking about this last night, it could be related to an issue with the cookie domain

Session Mismatch

Hello to you both, The common causes for a session mismatch error are usually one of the following: 1. Mis-configured URL parameter in your config.json file ...

NodeBB Community (community.nodebb.org)

I encountered something similar when recovering the production database to a development instance.

Worth a try.

DownPW

@phenomlab

I will test on my VM
But I have a machine where is it an install fromScratch without any database restore or Cloudflare

phenomlab

@DownPW is this on the same machine as where the prod instance was ?

DownPW

yes and on my no prod VM

DownPW

here ./nodebb log

2022-08-29T14:18:57.409Z [4567/592] - error: [acp] Failed to fetch latest version
Error: ETIMEDOUT
    at Timeout.<anonymous> (/home/nodebb/nodebb/node_modules/request/request.js:848:19)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7)
2022-08-29T14:20:29.243Z [4567/592] - error: Error: getaddrinfo EAI_AGAIN packages.nodebb.org {"cause":{"code":"EAI_AGAIN","errno":-3001,"hostname":"packages.nodebb.org","syscall":"getaddrinfo"},"error":{"code":"EAI_AGAIN","errno":-3001,"hostname":"packages.nodebb.org","syscall":"getaddrinfo"},"name":"RequestError","options":{"json":true,"resolveWithFullResponse":false,"simple":true,"transform2xxOnly":false,"uri":"https://packages.nodebb.org/api/v1/plugins?version=2.4.5"},"stack":"RequestError: Error: getaddrinfo EAI_AGAIN packages.nodebb.org\n    at new RequestError (/home/nodebb/nodebb/node_modules/request-promise-core/lib/errors.js:14:15)\n    at Request.plumbing.callback (/home/nodebb/nodebb/node_modules/request-promise-core/lib/plumbing.js:87:29)\n    at Request.RP$callback [as _callback] (/home/nodebb/nodebb/node_modules/request-promise-core/lib/plumbing.js:46:31)\n    at self.callback (/home/nodebb/nodebb/node_modules/request/request.js:185:22)\n    at Request.emit (node:events:527:28)\n    at Request.onRequestError (/home/nodebb/nodebb/node_modules/request/request.js:877:8)\n    at ClientRequest.emit (node:events:527:28)\n    at TLSSocket.socketErrorListener (node:_http_client:454:9)\n    at TLSSocket.emit (node:events:527:28)\n    at emitErrorNT (node:internal/streams/destroy:157:8)"}
2022-08-29T14:20:29.244Z [4567/592] - error: Error: getaddrinfo EAI_AGAIN packages.nodebb.org {"cause":{"code":"EAI_AGAIN","errno":-3001,"hostname":"packages.nodebb.org","syscall":"getaddrinfo"},"error":{"code":"EAI_AGAIN","errno":-3001,"hostname":"packages.nodebb.org","syscall":"getaddrinfo"},"name":"RequestError","options":{"json":true,"resolveWithFullResponse":false,"simple":true,"transform2xxOnly":false,"uri":"https://packages.nodebb.org/api/v1/plugins"},"stack":"RequestError: Error: getaddrinfo EAI_AGAIN packages.nodebb.org\n    at new RequestError (/home/nodebb/nodebb/node_modules/request-promise-core/lib/errors.js:14:15)\n    at Request.plumbing.callback (/home/nodebb/nodebb/node_modules/request-promise-core/lib/plumbing.js:87:29)\n    at Request.RP$callback [as _callback] (/home/nodebb/nodebb/node_modules/request-promise-core/lib/plumbing.js:46:31)\n    at self.callback (/home/nodebb/nodebb/node_modules/request/request.js:185:22)\n    at Request.emit (node:events:527:28)\n    at Request.onRequestError (/home/nodebb/nodebb/node_modules/request/request.js:877:8)\n    at ClientRequest.emit (node:events:527:28)\n    at TLSSocket.socketErrorListener (node:_http_client:454:9)\n    at TLSSocket.emit (node:events:527:28)\n    at emitErrorNT (node:internal/streams/destroy:157:8)"}
2022-08-29T14:20:39.255Z [4567/592] - error: GET /api/admin/extend/plugins?_=1661782683297
RequestError: Error: getaddrinfo EAI_AGAIN packages.nodebb.org

PitaJ

How are you running NodeBB?

EAI_AGAIN is a DNS lookup timed out error, means it is a network connectivity error or proxy related error.

julian

Is it still happening? Might've been a transient error with our host... so far nothing alerted on our end, so maybe it's over?

DownPW

@julian said in Error access Plugin ACP with 2.4.5:

Is it still happening? Might've been a transient error with our host... so far nothing alerted on our end, so maybe it's over?

Sorry for my late response @PitaJ @julian I'm busier than usual right now

Yes I think it's better now.
I do think it's a DNS problem like said @PitaJ above.

I continue to watch.

Thank you very much.

julian

@DownPW Might be might not be. I see some failing tests on GitHub too, related to that particular route.

Might be the API needs some streamlining. Right now it's sending a payload of 1000+ packages every time you hit the plugins page

DownPW

yep @julian

the access of this page is longer than usual even if it works

<baris>

Let me know if it works better now, I have added a cache to the trending plugins since it was the slowest call in that api.

DownPW

@baris

Yes it's better !