You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Gateway - Solana wallet creation fails when nodeURL has leading whitespace #233
While adding a Solana wallet through the Gateway wallet flow, the request failed instead of creating the wallet. Gateway returned Endpoint URL must start with http: or https: from /wallet/add.
#### HAPI logs
2026-09-11 00:17:42 | info | Adding new wallet for chain: solana
2026-09-11 00:17:42 | error | Unhandled error: {
"error": "Endpoint URL must start with `http:` or `https:`.",
"url": "/wallet/add",
"params": {}
}
The configured solana-mainnet-betanodeURL contained a leading space before https://. Gateway accepted this configuration but passed the untrimmed value to the Solana client, which rejected it while the connection was being initialized. Removing the leading space allows the endpoint to use the expected URL format. Gateway should trim surrounding whitespace or reject the value when the configuration is saved, before it can break wallet operations.
Current shape:
nodeURL: ' https://...'
Required shape:
nodeURL: 'https://...'
This was found during QA testing after whitespace was accidentally added to the saved nodeURL. Solana is the confirmed reproduction. Ethereum was not tested, but the same mistake may affect Ethereum and other networks that accept a user-provided node URL, so those network configurations should be checked as well.
Fixed after i remove the whitespace
Steps to reproduce bug
Configure the Solana mainnet-beta nodeURL with a leading space before https://
Save the network configuration
Attempt to add a new Solana wallet
Check the Gateway response or log for Endpoint URL must start with http: or https:
Thanks @rapcmia for the clear repro. Condor now strips surrounding whitespace from every string value in a Gateway network config before saving it from the dashboard, so a pasted https://... nodeURL reaches Gateway as https://...: hummingbot/condor@040bb73 (branch general_improvements). The Telegram flows already trimmed their input.
Two things this doesn't cover:
A nodeURL that was already saved with a space stays broken until it's re-saved.
Writes that bypass Condor (direct Gateway API, Swagger, editing the YAML) can still store it.
So Gateway should still trim or reject the value on save, as the issue suggests.
Activity
Strip whitespace from Gateway network config values before saving the…
cardosofede commentedon Sep 11, 2026
Thanks @rapcmia for the clear repro. Condor now strips surrounding whitespace from every string value in a Gateway network config before saving it from the dashboard, so a pasted
https://...nodeURL reaches Gateway ashttps://...: hummingbot/condor@040bb73 (branchgeneral_improvements). The Telegram flows already trimmed their input.Two things this doesn't cover:
So Gateway should still trim or reject the value on save, as the issue suggests.