I deployed an nft collection on solana using metaplex and candymachine. It was working fine for 4-5 days now suddenly I am receiving this error. I was able to connect wallet and mint fine for a couple of days. I am not sure what's wrong now what I am getting 403 from rpc pool?
Uncaught (in promise) Error: failed to get balance of account
: Error: 403 Forbidden: {"jsonrpc":"2.0","error":{"code":
403, "message":"Access forbidden, contact your app developer or
support#rpcpool.com."}, "id": "" }
So Metaplex and NFT calls are not allowed on the free RPCs. You'll have to use a paid provider or go with https://api.metaplex.solana.com/
If you're doing any sort of NFT drop, it is still recommended to get a paid RPC.
You shouldn't have to re-upload again, as long as you did successfully on the other RPC.
Related
I’m new in the development, and I’m facing an issue with salesforce connect app.
We are using azure logic apps to integrate salesforce with Microsoft products, we had some processes in place working fine for the last few years but from last week all of them were disconnected, the error message being thrown is:
"status": 401, "message": "Salesforce failed to complete task:
Message: This session is not valid for use with the REST
API\r\nclientRequestId: XXXXXXXXXX", "error": null, "source":
"Salesforce.Common", "errors": []
code": "Unauthorized",
"message": "Failed to refresh access token for service: salesforce. Correlation Id=XXXXXXX, UTC TimeStamp=8/15/2022
9:09:38 AM, Error: OAuth 2 access token refresh failed. Client ID and
secret sent in form body. Response status code=BadRequest. Response
body: '{"error":"invalid_grant","error_description":"expired
access/refresh token"}'.
I’ve reconnected azure with salesforce and granted all permission, including Perform requests at any time
I had no luck, after a few minutes it disconnected again… so I installed the Azure Connected App, and refreshed the connection… still no luck, it keeps disconnecting throwing the same error message.
However, I kept getting disconnected from and getting the same error message.
Any help would be much appreciated.
We've set up our deployments to run using Workload Identity. Each deployment has its own technical identity, a GCP service account set up with the required IAM roles, and a Kubernetes service account to match (both linked as described in the Workload Identity documentation).
This all works just fine, with one small problem: almost every time a pod starts it gives this error:
Error: Could not load the default credentials. Browse to https://cloud.google.com/docs/authentication/getting-started for more information. at GoogleAuth.getApplicationDefaultAsync (/home/node/node_modules/google-auth-library/build/src/auth/googleauth.js:155:19) at processTicksAndRejections (internal/process/task_queues.js:97:5) at async GoogleAuth.getClient (/home/node/node_modules/google-auth-library/build/src/auth/googleauth.js:486:17) at async GrpcClient._getCredentials (/home/node/node_modules/google-gax/build/src/grpc.js:88:24) at async GrpcClient.createStub (/home/node/node_modules/google-gax/build/src/grpc.js:213:23)
It then crash-loops and typically comes up later, after 2 or 3 retries. Very very odd...
To make matters worse, every now and then we get this error instead:
Error: 403 undefined: Getting metadata from plugin failed with error: Could not refresh access token: A Forbidden error was returned while attempting to retrieve an access token for the Compute Engine built-in service account. This may be because the Compute Engine instance does not have the correct permission scopes specified: Could not refresh access token: Unsuccessful response status code. Request failed with status code 403 at Object.callErrorFromStatus (/home/node/node_modules/#grpc/grpc-js/build/src/call.js:31:26) at Object.onReceiveStatus (/home/node/node_modules/#grpc/grpc-js/build/src/client.js:176:52) at Object.onReceiveStatus (/home/node/node_modules/#grpc/grpc-js/build/src/client-interceptors.js:342:141) at Object.onReceiveStatus (/home/node/node_modules/#grpc/grpc-js/build/src/client-interceptors.js:305:181) at /home/node/node_modules/#grpc/grpc-js/build/src/call-stream.js:124:78 at processTicksAndRejections (internal/process/task_queues.js:79:11)
And when we see this, it's basically game over until we try all kinds of black voodoo to try and get the service back up (usually it boils down to us deleting the entire auth stuff for that service and recreating things from scratch).
Anyone has any idea what could be going on here?
Our cluster is running 1.16.13-gke.1, and has Istio 1.6.7 installed (using the Istio operator).
So... the mystery has been solved.
There was an obscure but stupid but in our operator that provisions both the IAM and Kubernetes service accounts, including the necessary bindings.
There was a situation with a namespace being deleted that could end up in removing all the bindings to any other namespace :-( So this explains the error above, the moment this happened we got 403 errors (obviously, looking back on it now).
Bug has been fixed today, so all should be well now.
When I call the bing speech rest api a few days ago, I get an error and do not return a result.
System.Net.WebException: The remote server returned an error: (503) Server Unavailable.
at System.Net.HttpWebRequest.GetResponse()
at SpeechRESTSample.Program.Main(String[] args) in C:\Users\kaki1\Source\Repos\Cognitive-Speech-STT-ServiceLibrary\sample\SpeechRESTSample\Program.cs:line 78
The remote server returned an error: (503) Server Unavailable.
Renewed token.
or Internal Server Error
Does not provide services?
If I use the sample code directly to get the token then I got the 401 error.
The FetchTokenUri is changed from https://api.cognitive.microsoft.com/sts/v1.0 to
https://{region}.api.cognitive.microsoft.com/sts/v1.0/issueToken
we could get the authentication endpoint from this link.
And the endpoints for the Speech to Text REST API is the following format
https://{region}.stt.speech.microsoft.com/speech/recognition/conversation/cognitiveservices/v1
I also test it locally I can get the token with the endpoint.
For more demo code, please refer to this.
After developing in the sandbox, we got our api key approved and promoted to a live account.
Since then we've been getting the following response -
response: {
"errorCode": "ACCOUNT_LACKS_PERMISSIONS",
"message": "This Account lacks sufficient permissions."
}
http code: 401
exeucted at: 2017-05-17 15:03:59
Based on my research and according to ACCOUNT_LACKS_PERMISSIONS error when creating envelope
A setting needs to be switched on the backend at Docusign. The user mentions -
"They changed a setting called In Session to Enabled in API section near limiter that only the account manager or tier 2 support can change. All is well."
The account ID is 30953035
API username bcbffa28-a316-473e-b2b7-48d964d909a7
The API request is below. This was working just fine under a Demo account. I've even upgraded to the Intermediate API in the hopes that it will resolve my issues but no dice.
Support says that I need to post here...
This is caused by a bad account baseUrl that's being used in the request. When your integration performs authentication for a given user, if you are using Legacy auth (X-DocuSign-Authentication header) then you need to point to the following /login_information endpoint for the live system:
https://www.docusign.net/restapi/v2/login_information
When you get the response you then need to parse the baseUrl value that was returned and use that sub-domain for subsequent API requests. (Note that there are multiple sub-domains in the live system such as NA1, NA2, EU, etc)
The baseUrl that's returned will look something like:
https://na2.docusign.net/restapi/v2/accounts/12345/envelopes
Make sure you configure your code to read this sub-domain and use in subsequent requests, otherwise you if you simply use www for instance you will not be hitting the correct account endpoint and you'll receive the "Account lacks permissions" error you're receiving.
Ergin's answer seems to work; however, he does not state which part of the baseUrl to keep after parsing. In his example the baseUrl = "https://na2.docusign.net/restapi/v2/accounts/12345/envelopes" In all subsequent calls after authApi.Login(); use "https://na2.docusign.net/restapi" as the URL and that should eliminate the error message.
Not long ago I used the following request to fetch some data for my application:
https://api.instagram.com/v1/tags/mytag/media/recent?access_token=mytoken
Now I am greeted with the following response:
{"meta": {"error_type": "OAuthPermissionsException", "code": 400, "error_message": "This request requires scope=public_content, but this access token is not authorized with this scope. The user must re-authorize your application with scope=public_content to be granted this permissions."}}
It seems I must have my application approved by Istagram to have access to the data I want.
So is this the only currently supported way to keep my application working?
I am grateful for any help.
Cheers
Yes, after June 1st 2016, all apps have to be reviewed by Instagram and approved to get API access
If not you can only access your latest 20 posts using API (sandbox mode)
https://www.instagram.com/developer/review/