search

movementlabsxyz / M1

An L1 for Move VM built on Avalanche.
https://docs.movementlabs.xyz
BSD 3-Clause "New" or "Revised" License
72 stars 53 forks source link

Numerous complaints about faucet being down #125

Closed andygolay closed 5 months ago

andygolay commented 6 months ago

Both faucet website and with CLI.

Example output from CLI:

  $ movement aptos init
  Configuring for profile default
  Choose network from [devnet, testnet, mainnet, local, custom | defaults to devnet]
  testnet
  Enter your private key as a hex literal (0x...) [Current: None | No input: Generate new key (or keep one if present)]
  **
  Account * doesn't exist, creating it and funding it with 100000000 Octas
  res: Err(aptos error: "{\n  "Error": "API error: Faucet issue: FaucetClientError { inner: Inner { kind: HttpStatus(404), source: None } }"\n}")
  gitpod /workspace/movement-deploy (main)
radupopa369 commented 6 months ago

according to our docs https://docs.movementlabs.xyz/ecosystem/faucet

the faucet for m1 cli is https://aptos.devnet.m1.movementlabs.xyz

andygolay commented 6 months ago

according to our docs https://docs.movementlabs.xyz/ecosystem/faucet

the faucet for m1 cli is https://aptos.devnet.m1.movementlabs.xyz

Okay I checked this and yes it worked. Seems like the user-reported error was caused by user error such as perhaps an incorrect RPC url.

It looks like specifically M2 and MEVM faucets are not working from the faucet website.

@tonyxia2023 did you happen to make any changes to M2 or MEVM which are affecting the faucet?