- This topic has 9 replies, 3 voices, and was last updated 1 year, 10 months ago by
.
-
Posts
-
edit: when i curl without –digest then request works. with — digest the terminal says me: login required
Hello,
The Monero coin adapter returns this error if the response it gets from your wallet is a valid JSON response, but it does not include a “result” field.
In practice this could mean that there was a problem with authentication.
1. Is this error on a new wallet or on an existing wallet that suddenly stopped working?
2. Have you used the
--rpc-loginargument when startingmonero-wallet-rpc?3. Is this a Monero wallet or other Monero fork? The Monero docs clearly state that
--digestshould be used. If you cannot curl to your wallet using--digestthen this is likely a wallet that is not exactly the same as Monero, so it would be best to contact the developers of the wallet about this.Let me know about points 1,2 and 3 please.
And, if there’s an issue with a Monero fork, I’d like to know what that wallet is, so I can make the adapters work with it.
with regards
1: it is a new wallet
2: yes.
3: 3: This is the git.i was thinking about copy the adapter code an comment out CURLOPT_HTTPAUTH => CURLAUTH_DIGEST,
Hello,
Thank you for the additional details. I will investigate this wallet soon.
You could comment out that line to test what happens. If you do, let me know. Does the wallet work without it?
But this is not a permanent solution because it would affect your other Monero-based wallets. You can’t just copy the code into a new plugin, there would be too many name collisions.
I have to build that wallet, understand what its authentication method is, if any, and then understand why it’s different. As you know, there are several possible authentication methods on HTTP: https://curl.se/libcurl/c/CURLOPT_HTTPAUTH.html
Perhaps it’s a fork from an earlier version of Monero, or it’s simply modified.
Once I have a clear picture of what other authentication methods are possible with these types of wallets, I can add to the coin adapter settings.
I have added this to my backlog. I will get back to you about this, hopefully in the next week.
with regards
ok i comment this out:
// CURLOPT_HTTPAUTH => CURLAUTH_DIGEST,
and the adapter works as expected. However, the other adapters then no longer work as you had mentionedThank you. That makes sense.
Italo is a fork of Oxen (previously Loki).
This is considerably different from Monero. For example, Oxen distinguishes between a restricted admin RPC port and a public RPC port, and Italo does the same.
I can now confirm that, as you say, without digest authentication the wallet API authenticates correctly. (I didn’t get the chance to fully test the italo wallet.)
In version 1.1.4 of the Monero coin adapter, I have added an option for basic authentication, so that all Oxen forks can be supported.
with regards
Thanks, it was based on your idea to try it without digest auth.
So, I’m curious, does the Italo wallet work fine? Did you test deposits/withdrawals? If you want, let us know.
- You must be logged in to reply to this topic.