tried:
solana airdrop 1
solana airdrop 1 <address> --url devnet
solana airdrop 1 <address> --url https://api.devnet.solana.com
all returns this error:
Error: airdrop request failed. This can happen when the rate limit is reached.
i can confirm that my cli config is set to devnet, also it affects my typescript function airdropSol() which returns an error:
Error: airdrop to GFfY2JVH2iB9gRmg7oKdwgGJcbXuhGu8vEsMY5yJryeq failed: Internal error
at Connection.requestAirdrop (/home/user/hellow_world/node_modules/#solana/web3.js/src/connection.ts:3905:13)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
Try running this
curl -v https://api.devnet.solana.com --resolve api.devnet.solana.com:443:139.178.65.155 -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1, "method":"requestAirdrop", "params":["<wallet pub key>", 1000000000]}'
more expannation - https://solana.stackexchange.com/a/4240/3028
Related
I am using following command to create an EKS cluster :
eksctl create cluster --name cqpocsefkdemo --node-type t2.micro --nodes 3 --nodes-min 3 --nodes-max 5 --region us-east-1 --zones us-east-1a,us-east-1b,us-east-1c,us-east-1d,us-east-1f
But I am getting error that I am unable to resolve, the error looks like this:
SDK 2022/04/15 19:20:50 DEBUG request failed with unretryable error
https response error StatusCode: 403, RequestID:
56fa150b-5c94-499f-be10-d9a318557f15, api error SignatureDoesNotMatch:
Signature expired: 20220415T135049Z is now earlier than
20220415T143550Z (20220415T145050Z - 15 min.)
Error: checking AWS STS access – cannot get role ARN for current
session: operation error STS: GetCallerIdentity, https response error
StatusCode: 403, RequestID: 56fa150b-5c94-499f-be10-d9a318557f15, api
error SignatureDoesNotMatch: Signature expired: 20220415T135049Z is
now earlier than 20220415T143550Z (20220415T145050Z - 15 min.)
The error occurred because the system time was not in sync, I resolved this error by going to windows setting and sync up my date and time.
I followed this tutorial on macOS and upgraded to v0.0.2 using these model files. The POST SetupDemo API (curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' -d '{}' 'http://127.0.0.1:3000/api/SetupDemo') returns
{
"error": {
"statusCode": 500,
"name": "Error",
"message": "Error trying invoke business network. Error: No valid responses from any peers.\nResponse from attempted peer comms was an error: Error: transaction returned with failure: ReferenceError: require is not defined",
"stack": "Error: Error trying invoke business network. Error: No valid responses from any peers.\nResponse from attempted peer comms was an error: Error: transaction returned with failure: ReferenceError: require is not defined\n at HLFConnection.invokeChainCode (/Users/jps/.nvm/versions/node/v8.12.0/lib/node_modules/composer-rest-server/node_modules/composer-connector-hlfv1/lib/hlfconnection.js:994:30)\n at <anonymous>"
}
}
The SetupDemo API did work on IBM Cloud BC before without this error.
$ node -v
v8.12.0
I'm trying to check if user purchased an application with request like this:
curl -X GET -H "Content-Type: application/x-www-form-urlencoded" 'https://api.steampowered.com/ISteamUser/CheckAppOwnership/v1?key=< VALID_KEY>&appid=< VALID_APP_ID>&steamid=<...>'
Every parameter is valid and was successfully used in other requests, but with all requests to ISteamUser I get same strange error
Failed to forward request message to internal server
And same error when requesting partner.steam-api.com
I tried to receive in .NET information about TeamCity build. All works fine, except one: I tried to get build name, using request to REST API.
Here is my request:
https://myteamcity/httpAuth/app/rest/buildTypes/id:<build_id>/name
And here is my error: Error has occurred during request processing (Not Acceptable).
Error: javax.ws.rs.WebApplicationException
Not supported request. Please check URL, HTTP method and transfered data are correct.
In browser I received correct plain text information. What's wrong with REST API? All another requests work well.
Accept header might cause the problem, try changing it to Accept: text/plain or removing it.
For example, when I request
curl -H "Accept: application/json" http://teamcity/httpAuth/app/rest/buildTypes/id:buildId/name --user user:pass
I'm getting the same error, but the name is returned after changing value of the header to text/plain
curl -H "Accept: text/plain" http://teamcity/httpAuth/app/rest/buildTypes/id:buildId/name --user user:pass
or after removing the header from the request
curl http://teamcity/httpAuth/app/rest/buildTypes/id:buildId/name --user user:pass
I created pep proxy user in Horizon.
Username:
pep_proxy_4ac90a28a7e0465caf0a9f32998ab47b
Password:
##################
And than i changed config.js of PEP proxy:
config.username = 'pep-proxy-aadd736bf4ea4739bd3bfe2cac4178c0';
config.password = '##################';
And when i start pep proxy i get this error:
ERROR: Server - Error in keystone communication {"error": {"message":
"The request you have made requires authentication.",
"code": 401, "title": "Unauthorized"}}
Can you help me with this.What might be the problem?
Thanks!
It seems that even though this user is created via Horizon it isn't granted any assignment in default domain.
I just ran
curl -v -s -X PUT -H "X-Auth-Token: ............................"
-H "Content-type: application/json"
http://192.168.4.180:5000/v3/domains/default/users/pep-proxy-aadd736bf4ea4739bd3bfe2cac4178c0/roles/4475dadfface4582ba8c7ab0c6f48d1c
where '4475dadfface4582ba8c7ab0c6f48d1c' is id of admin role.