Open extra topbar

Cannot connect to the wallet

I reply to all queries on the forums and via email, once per day, Monday to Friday (not weekends).

If you are new here, please see some information on how to ask for support. Thank you!

Cannot connect to the wallet

dashed-slug.net Forums General discussion Cannot connect to the wallet

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #10092
    alexg
    Keymaster

    Not responding: Dashed_Slug_Wallets_Coin_Adapter_RPC->get_balance() failed with status=”403″ and error=”HTTP_FORBIDDEN”

    #10096
    alexg
    Keymaster

    This means that the password you entered in the coin adapter settings does not match the one in your conf file.

    In Bitcoin there are two ways to specify RPC API credentials: rpcauth/rpcpassword, and rpcauth. Use one or the other, but not both. Check that the password you’ve entered in the coin adapter settings matches the password in your wallet config.

    A common problem is if your password contains the = character. This cannot be used with rpcpassword, as the = character is used as a separator between key and value in the .conf file. The simplest solution is not to use a password with the = character.

    Also check that the IP in your rpcallowip clause in in CIDR notation, i.e. it should have something in it specifying the network class (see here).

    #10097
    alexg
    Keymaster

    it is still not working

    #10119
    alexg
    Keymaster

    Hello,

    There are no other situations that I know of where bitcoin would respond with 403.

    Can you please be more specific? What did you try?

    1. Did you enter credentials using rpcuser/rpcpassword or using rpcauth?

    2. Did you enter an rpcbind config? If so, did you specify the network class as mentioned above?

    Let me know.

    with regards

    #10125
    alexg
    Keymaster

    It is Litecoin, I entered credentials using rpcuser/rpcpassword, and I have double check and they are correct.

    #10136
    alexg
    Keymaster

    Can you show me your rpcbind config?

    #10164
    alexg
    Keymaster

    rpcuser=xxxx
    rpcpassword=xxxx
    rpcallowip=127.0.0.1
    rpcallowip=45.87.80.226
    rpcallowip=45.87.80.240
    rpcallowip=45.87.80.254
    rpcport=9332
    server=1
    daemon=1
    txindex=1
    listen=1

    #10165
    alexg
    Keymaster

    Hello,

    There is no rpcbind statement in your config. Add the following:
    rpcbind=a.b.c.d
    where a.b.c.d is the public internet IP of your wallet server.

    Also, I believe that the rpcallowip statements must be in CIDR notation. Try:

    rpcallowip=127.0.0.1/8
    rpcallowip=45.87.80.226/24
    rpcallowip=45.87.80.240/24
    rpcallowip=45.87.80.254/24

    with regards

    #10166
    alexg
    Keymaster

    It isn’t working, even after I reboot the server

    #10172
    alexg
    Keymaster

    I fixed with rpcallowip=45.87.80.*

    #10180
    alexg
    Keymaster

    That’s great news. Thanks for letting us know.

    Just be careful. Anyone in that IP range can theoretically connect to your wallet, if they also have your RPC password.

    with regards

Viewing 11 posts - 1 through 11 (of 11 total)
  • You must be logged in to reply to this topic.