When I try to execute Amplify GraphiQL Explorer via npm run start, it works initially via browser. But when I execute the GraphQL query after for a few seconds I get the following error:
Error:
[0] CredentialsError: Missing credentials in config, if using AWS_CONFIG_FILE, set
AWS_SDK_LOAD_CONFIG=1
[0] at Timeout.connectTimeout [as _onTimeout]
(C:\Users\username\WebstormProjects\configurationservice\node_modules\serverless-plugin-
offline-dynamodb-stream\node_modules\aws-sdk\lib\http\node.js:69:15)
[0] at listOnTimeout (node:internal/timers:559:17)
[0] at processTimers (node:internal/timers:502:7)
[0]
[0] 1 deprecation found: run 'serverless doctor' for more details
[0] npm run local exited with code 1
I dont know the reason and I am concerned about whether I am supposed to use the parameter as well. Any help would be appreciated.
I found the problem. Credentials file in .aws folder should include [default] profile.
Related
I am trying to create a new react project, I tried using both npm and yarn but I am getting a server timeout error in both cases. I also tried reinstalling node but that didn't help. I also tried resetting registry but even that didn't help. This is my error:
Trace:
Error: https://registry.npmjs.org/create-react-app: ETIMEDOUT
at Timeout._onTimeout (/usr/share/yarn/lib/cli.js:141550:19)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7)
How should I solve this?
I have 230 tests and on my own machine its passed always, but on the github in github actions, tests is often falling with econnreset problem:
[0] 1) App [0] Get full search result [0] "before all" hook for "should search full list of collabraotions and users": [0] Error: connect ECONNRESET 127.0.0.1:36421 [0] at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16)
And I don't know how fix this, and I will be happy if someone tell me reason and how fix it.
My througts was, that it caused by wrong ports, but after change ports to hardcode 3000, problem not left
UPDATE: node version is 16.14 on my own computer and in workflow
I have a Node.js app on a shared hosting plan. I found out that when I login using the Firebase Authentication layer, I get a 401 error. While digging deeper, I found the following error message on the server:
Error: error:02016002:system library:stat:No such file or directory
at Sign.sign (internal/crypto/sig.js:103:29)
at Object.sign (/home/cp1183833p05/nodevenv/node-app/12/lib/node_modules/jsonwebtoken/node_modules/jwa/index.js:152:45)
at Object.jwsSign [as sign] (/home/cp1183833p05/nodevenv/node-app/12/lib/node_modules/jsonwebtoken/node_modules/jws/lib/sign-stream.js:32:24)
at Object.module.exports [as sign] (/home/cp1183833p05/nodevenv/node-app/12/lib/node_modules/jsonwebtoken/sign.js:204:16)
at ServiceAccountCredential.createAuthJwt_ (/home/cp1183833p05/nodevenv/node-app/12/lib/node_modules/firebase-admin/lib/auth/credential.js:103:20)
at ServiceAccountCredential.getAccessToken (/home/cp1183833p05/nodevenv/node-app/12/lib/node_modules/firebase-admin/lib/auth/credential.js:76:26)
at FirebaseAppInternals.getToken (/home/cp1183833p05/nodevenv/node-app/12/lib/node_modules/firebase-admin/lib/firebase-app.js:65:73)
at AuthorizedHttpClient.send (/home/cp1183833p05/nodevenv/node-app/12/lib/node_modules/firebase-admin/lib/utils/api-request.js:666:34)
at /home/cp1183833p05/nodevenv/node-app/12/lib/node_modules/firebase-admin/lib/auth/auth-api-request.js:1472:37
at processTicksAndRejections (internal/process/task_queues.js:97:5) {
opensslErrorStack: [
'error:0E07606D:configuration file routines:module_run:module initialization error',
'error:0E07B075:configuration file routines:ssl_module_init:ssl command section empty'
],
library: 'system library',
function: 'stat',
reason: 'No such file or directory',
code: 'ERR_OSSL_SYS_NO_SUCH_FILE_OR_DIRECTORY'
}
This error happens only when I restart the app and I sign in for the first time. Then, it happens at random occasion. How can I fix this?
NodeJS version 12.18.3
I contacted the hosting provider and found that the issues were tied to jsonwebtoken and firebase-admin packages.
After configuring as show in the Readme fit in Hyperledger explore and making md5 to trust I have managed to come this far. I am currently using an Ubuntu 18.04 LTS server.
Test explorerpg.sql for DDL statements syntax verification
✓ should read the file explorerpg.sql for ddl statements
TAP version 13
# Test Results
ok 1 DROP USER IF EXISTS testuser;
not ok 2 WITH PASSWORD 'password';
---
operator: fail
at: <anonymous> (/home/hrm/hrm-explorer/app/test/postgrespgtest.js:2:5157)
stack: |-
Error: WITH PASSWORD 'password';
at Test.assert [as _assert] (/home/hrm/hrm-explorer/app/test/node_modules/tape/lib/test.js:228:54)
at Test.bound [as _assert] (/home/hrm/hrm-explorer/app/test/node_modules/tape/lib/test.js:80:32)
at Test.fail (/home/hrm/hrm-explorer/app/test/node_modules/tape/lib/test.js:322:10)
at Test.bound [as fail] (/home/hrm/hrm-explorer/app/test/node_modules/tape/lib/test.js:80:32)
at /home/hrm/hrm-explorer/app/test/postgrespgtest.js:2:5157
at processTicksAndRejections (internal/process/task_queues.js:97:5)
...
Test fails of: # tests 65, # pass 43, # fail 22
Moreover npm ERR! Failed at the hyperledger-explorer-test#0.3.9 test script
The error has been fixed in the recent Pull Request. You won't see it any more in the latest codebase (v1.1.0).
I'm working on a dialogflow POC where I'm trying to invoke the v2 API provided by DialogFlow. While trying the NodeJS code example provided here, I'm getting the below error
{ Error: EHOSTUNREACH undefined: Getting metadata from plugin failed with error: request to https://www.googleapis.com/oauth2/v4/token failed, reason: connect EHOSTUNREACH 0.0.38.172:80 - Local (192.168.0.103:51468)
at Object.callErrorFromStatus (/Users/devuser/Development/workspaces/df-poc/node_modules/#grpc/grpc-js/build/src/call.js:30:26)
at Http2CallStream.call.on (/Users/devuser/Development/workspaces/df-poc/node_modules/#grpc/grpc-js/build/src/client.js:96:33)
at Http2CallStream.emit (events.js:203:15)
at process.nextTick (/Users/devuser/Development/workspaces/df-poc/node_modules/#grpc/grpc-js/build/src/call-stream.js:75:22)
at process._tickCallback (internal/process/next_tick.js:61:11)
code: 'EHOSTUNREACH',
details:
'Getting metadata from plugin failed with error: request to https://www.googleapis.com/oauth2/v4/token failed, reason: connect EHOSTUNREACH 0.0.38.172:80 - Local (192.168.0.103:51468)',
metadata: Metadata { internalRepr: Map {}, options: {} } }
I have imported GOOGLE_APPLICATION_CREDENTIALS and point the environment variable to the credentials. The invocation works fine if I try the REST API route with the Authorization header.
Kindly let me know if there is something which I'm missing here.
This means EHOST (the remote host of the files you are requesting) are unreachable. They are either down, or your computer cannot access them due to some other restriction, such as location, which can be solved with a VPN.