Deploy keeps crashing and i only have 3 variables
lindomaker
FREEOP

6 days ago

sui_keystore seems to be the problem. which format should it be

Awaiting Conductor Response$10 Bounty

4 Replies

Railway
BOT

6 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway 6 days ago


6 days ago

No idea what sui_keystore is, Any error on your Deploy Logs?


nightangelflowerwin-ops
FREETop 10% Contributor

6 days ago

) must be a valid JSON array of Base64-encoded private keys.


nightangelflowerwin-ops

) must be a valid JSON array of Base64-encoded private keys.

nightangelflowerwin-ops
FREETop 10% Contributor

6 days ago

sui client new-address ed25519 -bash

From mnemonic

sui keytool import "word1 word2 ... word12" ed25519

From Bech32 (starts with suiprivkey1...)

sui keytool import suiprivkey1q... ed25519

sui keytool convert

sui keytool export --key-identity


nightangelflowerwin-ops

sui client new-address ed25519 -bash From mnemonic sui keytool import "word1 word2 ... word12" ed25519 # From Bech32 (starts with suiprivkey1...) sui keytool import suiprivkey1q... ed25519 sui keytool convert <hex-or-base64> sui keytool export --key-identity <address-or-alias>

lindomaker
FREEOP

5 days ago

that worked thanks but now I have this error: Outbound HTTPS from container fails to reach a specific external API

I'm running the Walrus Publisher/Aggregator template (image cmdoss/walrus, MODE=publisher, NETWORK=mainnet). The container starts, reads its config, then fails immediately when it tries to open a connection to the Sui RPC endpoint https://fullnode.mainnet.sui.io:443:

INFO walrus_sui::config: using Sui wallet configuration from '/config/wallet-config.yml'

Error: Failed to get client from url: max failovers exceeded [max_tries=1]

The endpoint is healthy, it responds in under 0.4s from my own machine and the failure happens on the first attempt, so it looks like the connection is refused or unroutable rather than slow.

Is there anything about outbound egress from Railway containers that would prevent this?

Is egress IPv6-only, or dual-stack? (This endpoint may not have AAAA records.)

Is there any egress proxy, DNS restriction, or rate limiting on shared egress IPs?

Is there a way to see the container's outbound IP, or to open a shell to run curl against that URL for a direct test?

thanks in advance


Welcome!

Sign in to your Railway account to join the conversation.

Loading...