Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The supplied pubkey is not authorized to generate a token #35

Open
CValeron opened this issue Dec 14, 2024 · 2 comments
Open

The supplied pubkey is not authorized to generate a token #35

CValeron opened this issue Dec 14, 2024 · 2 comments

Comments

@CValeron
Copy link

Hi

When I run below script,

cargo run --release --bin jito-shredstream-proxy -- shredstream --block-engine-url https://ny.mainnet.block-engine.jito.wtf --auth-keypair my_keypair.json --desired-regions amsterdam,ny --dest-ip-ports 127.0.0.1:8001

I got below warning and I cannot receive any data

[2024-12-14T11:27:55Z WARN jito_shredstream_proxy::heartbeat] Failed to connect to block engine, retrying. Error: BlockEngineConnectionError client error: status: PermissionDenied, message: "The supplied pubkey is not authorized to generate a token.", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "server": "jito-block-engine", "x-request-received-at": "2024-12-14T11:27:55.369Z", "content-length": "0", "date": "Sat, 14 Dec 2024 11:27:54 GMT", "x-envoy-upstream-service-time": "0"} }

[2024-12-14T11:27:55Z INFO solana_metrics::metrics] metrics disabled: environment variable not found
[2024-12-14T11:27:55Z WARN solana_metrics::metrics] datapoint: shredstream_proxy-heartbeat_client_error,block_engine_url=https://ny.mainnet.block-engine.jito.wtf errors=1i error_str="BlockEngineConnectionError client error: status: PermissionDenied, message: "The supplied pubkey is not authorized to generate a token.", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "server": "jito-block-engine", "x-request-received-at": "2024-12-14T11:27:55.369Z", "content-length": "0", "date": "Sat, 14 Dec 2024 11:27:54 GMT", "x-envoy-upstream-service-time": "0"} }"

I tried different pubkeys and made them approved but didn't work. Is there anyway to fix this issue ?

@CValeron
Copy link
Author

const keyPair = solanaWeb3.Keypair.generate();
my_keypair.json -> keyPair.secretKey as 64 int array
and I submitted keyPair.publicKey as string to be approved

Are those correct ways ?

@CValeron
Copy link
Author

I was recently registered an account at jitolabs, could that be the reason ? should I wait for a time ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant