15:08:45 <m-relay> <f​ineopal:nope.chat> Greetings. I was trying to perform a very simple JSON RPC call to `monero-wallet-cli` which is running on port 28088. I first call `open_wallet` method, according to the docs:
15:08:45 <m-relay> <f​ineopal:nope.chat> ```
15:08:47 <m-relay> <f​ineopal:nope.chat> IP=127.0.0.1
15:08:49 <m-relay> <f​ineopal:nope.chat> PORT=28088
15:08:51 <m-relay> <f​ineopal:nope.chat> METHOD="open_wallet"
15:08:53 <m-relay> <f​ineopal:nope.chat> PARAMS='{"filename":"wallet","password":"pass1234"}'
15:08:55 <m-relay> <f​ineopal:nope.chat> curl \
15:08:57 <m-relay> <f​ineopal:nope.chat>     -u monero:password --digest \
15:08:59 <m-relay> <f​ineopal:nope.chat>     http://$IP:$PORT/json_rpc \
15:09:01 <m-relay> <f​ineopal:nope.chat>     -d '{"jsonrpc":"2.0","id":"0","method":"'$METHOD'","params":'"$PARAMS"'}' \
15:09:03 <m-relay> <f​ineopal:nope.chat>     -H 'Content-Type: application/json'
15:10:00 <m-relay> <f​ineopal:nope.chat> The params for get_transfers, along with wallet and password: `{"in": true, "account_index": 1}`
15:13:36 <m-relay> <f​ineopal:nope.chat> Am I doing it wrong? I tried different public nodes as well.
15:29:17 <selsta> did you try rpc wallet?
15:40:59 <m-relay> <f​ineopal:nope.chat> I created a normal wallet using `monero-wallet-cli`.
15:58:49 <m-relay> <f​ineopal:nope.chat> Does RPC commands not work for a normal wallet? The open_wallet seems to be working tho.
16:00:02 <moneromooo> monero-wallet-cli does not do RPC.
16:01:04 <moneromooo> I don't think it listens to any port either.
16:04:23 <m-relay> <f​ineopal:nope.chat> Shoot. I thought it did. Apologies.
16:05:10 <m-relay> <o​frnxmr:monero.social> You're using the rpc wallet
16:05:46 <m-relay> <o​frnxmr:monero.social> "i'm running monero-wallet-cli with this command: `monero-wallet-rpc`"
16:06:53 <m-relay> <o​frnxmr:monero.social> Your command flags dont make sense though
16:07:05 <m-relay> <f​ineopal:nope.chat> What's wrong?
16:07:51 <m-relay> <o​frnxmr:monero.social> Youre using --wallet-dir, so --password shouldnt be used
16:08:34 <m-relay> <f​ineopal:nope.chat> Yeah, that's incorrectly pasted. Not intending to use that flag.
16:09:52 <m-relay> <f​ineopal:nope.chat> Are there any wrong flags for the get_transfers?
16:09:56 <m-relay> <o​frnxmr:monero.social> if open_wallet works, then other methods should too. If the wallet us not synced / is brand new, it will have to sync the checkpoints before it will respond
16:10:29 <m-relay> <o​frnxmr:monero.social> [#monero-support:monero.social](https://matrix.to/#/%23monero-support:monero.social)
16:10:34 <moneromooo> If it's monero-wallet-cli, and the wallet is already open from command line args, it might *look* like open_wallet is working when it's failing.
16:10:35 <m-relay> <f​ineopal:nope.chat> I don't see any syncing logs in the RPC daemon which is running in foreground.
16:11:44 <m-relay> <o​frnxmr:monero.social> --log-level=4
16:16:02 <m-relay> <f​ineopal:nope.chat> Thanks. I am getting this logs:
16:16:03 <m-relay> <f​ineopal:nope.chat> ```
16:16:05 <m-relay> <f​ineopal:nope.chat> 2025-06-06 16:15:36.253	D Skipped block by height: 3386368
16:16:07 <m-relay> <f​ineopal:nope.chat> 2025-06-06 16:15:36.253	D Skipped block by height: 3387392
16:16:09 <m-relay> <f​ineopal:nope.chat> 2025-06-06 16:15:36.253	D Skipped block by height: 3388416
16:16:11 <m-relay> <f​ineopal:nope.chat> 2025-06-06 16:15:36.253	D Skipped block by height: 3389440
16:16:13 <m-relay> <f​ineopal:nope.chat> 2025-06-06 16:15:36.253	D Skipped block by height: 3390464
16:16:15 <m-relay> <f​ineopal:nope.chat> 2025-06-06 16:15:36.253	D Skipped block by height: 3391488
16:16:17 <m-relay> <f​ineopal:nope.chat> 2025-06-06 16:15:36.253	D Skipped block by height: 3392512
16:16:19 <m-relay> <f​ineopal:nope.chat> 2025-06-06 16:15:36.253	D Skipped block by height: 3393536
16:16:21 <m-relay> <f​ineopal:nope.chat> 2025-06-06 16:15:36.253	D Skipped block by height: 3394560
16:16:23 <m-relay> <f​ineopal:nope.chat> I am assuming it's syncing.
16:17:52 <m-relay> <f​ineopal:nope.chat> Now, it's just spam of this:
16:17:53 <m-relay> <f​ineopal:nope.chat> ```
16:17:55 <m-relay> <f​ineopal:nope.chat> 2025-06-06 16:17:21.863	T READ ENDS: Success. bytes_tr: 16384
16:17:57 <m-relay> <f​ineopal:nope.chat> 2025-06-06 16:17:23.365	T READ ENDS: Success. bytes_tr: 16384
16:17:59 <m-relay> <f​ineopal:nope.chat> 2025-06-06 16:17:24.309	T READ ENDS: Success. bytes_tr: 16384
16:18:01 <m-relay> <f​ineopal:nope.chat> 2025-06-06 16:17:25.359	T READ ENDS: Success. bytes_tr: 16384
16:18:03 <m-relay> <f​ineopal:nope.chat> 2025-06-06 16:17:26.463	T READ ENDS: Success. bytes_tr: 16384
16:18:05 <m-relay> <f​ineopal:nope.chat> 2025-06-06 16:17:27.783	T READ ENDS: Success. bytes_tr: 16384
16:18:07 <m-relay> <f​ineopal:nope.chat> 2025-06-06 16:17:28.679	T READ ENDS: Success. bytes_tr: 16384
16:18:09 <m-relay> <f​ineopal:nope.chat> 2025-06-06 16:17:30.310	T READ ENDS: Success. bytes_tr: 16384
16:18:11 <m-relay> <f​ineopal:nope.chat> ```
16:20:18 <moneromooo> If it's syncing, wait. It might not listen to RPC while syncing.
16:21:30 <m-relay> <f​ineopal:nope.chat> It was showing the block height but now it's a constant spam of the logs pasted above.
16:21:50 <m-relay> <o​frnxmr:monero.social> Its syncing through the checkpoints
16:22:16 <m-relay> <o​frnxmr:monero.social> Will take a few minutes because youre using a remote node. Locally takes like 1min
16:22:24 <m-relay> <f​ineopal:nope.chat> It has stopped now, does it mean it's done?
16:22:36 <m-relay> <o​frnxmr:monero.social> Probably
16:23:07 <m-relay> <f​ineopal:nope.chat> Still the same, it's stuck.
16:23:16 <m-relay> <f​ineopal:nope.chat> Still the same, it's stuck when I call get_transfers.
16:24:29 <m-relay> <o​frnxmr:monero.social> https://zerobin.net << paste your command here
16:24:45 <m-relay> <o​frnxmr:monero.social> Also try a simple command like get_height
16:25:16 <m-relay> <o​frnxmr:monero.social> if its not finished, its because the wallet is still not synced. Will take a few mins
16:26:05 <m-relay> <o​frnxmr:monero.social> [#monero-support:monero.social](https://matrix.to/#/%23monero-support:monero.social)  (-dev is got development, not support)
16:26:28 <m-relay> <o​frnxmr:monero.social> or #monero-support on irc
23:17:56 <rsch> hi
23:18:26 <rsch> there is a bug in monero-wallet-cli
23:19:05 <rsch> if you type --wallet-file test.keys and change password he save the password in a way that its corrupt
23:19:14 <rsch> can someone explain how the filename is used in password change?
23:21:04 <m-relay> <v​tnerd:monero.social> I assume you are the same person that reported here -> https://github.com/monero-project/monero/issues/9943   ?
23:21:23 <rsch> yes
23:21:39 <rsch> I changed the password of my wallet with my lalbels and descriptions
23:21:47 <rsch> I cannot login back
23:24:31 <rsch> vtnerd: why asking?
23:25:00 <m-relay> <v​tnerd:monero.social> this was already being tracked in the issue system, didn’t need to report here too
23:26:14 <rsch> I dont report it here
23:26:32 <rsch> I have asked a question to understand the code base better
23:34:18 <rsch> I would like to understand the code structure better. You have some documentation for it?
23:35:15 <m-relay> <o​frnxmr:xmr.mx> "Is there a way to restore the wallet with the incorrect password setting?"
23:35:15 <m-relay> <o​frnxmr:xmr.mx> Use your seed / mnemonic
23:35:39 <rsch> I know but I lose labels and descriptions
23:59:20 <rsch> vtnerd: do you have an idea where the problem could come from?