Why i get 403 error for http rpc access when permission in bitcoin.conf seems to be well #30557

1. 
   kosuodhmwa commented at 10:48 am on July 31, 2024: none

   https://github.com/sparrowwallet/sparrow/issues/1471

   

   Neither sparrowwallet (https://github.com/sparrowwallet/sparrow/issues/1471) nor cryptoadvance (https://github.com/cryptoadvance/specter-desktop/issues/2465) is working with REMOTE access from other IP while “miro bitcoin manager” is working on same vm as bitcoind stack (via 127.0.0.1)

2. 
   kosuodhmwa commented at 10:48 am on July 31, 2024: none

   does not make sense with that config params imo.

   and username and password is 100% correctly

3. 
   kosuodhmwa commented at 10:49 am on July 31, 2024: none

   i also added disablewallet=0, does not solve problem

   maybe problem is that it runs via tor? but miro bitcoin manager web gui also runs… (???)

   bitcoin stack i use is Satoshi:27.99.0

4. 
   kosuodhmwa commented at 10:50 am on July 31, 2024: none

   this
5. 
   kosuodhmwa commented at 10:51 am on July 31, 2024: none

   
6. 
   kosuodhmwa commented at 10:51 am on July 31, 2024: none

   same here
7. 
   pinheadmz commented at 10:52 am on July 31, 2024: member

   You need to set rpcuser and rpcpassword in bitcoin.conf
8. 
   kosuodhmwa commented at 10:55 am on July 31, 2024: none

   its set you lil genious, otherwise “miro bitcoin manager” would also not run on 127.0.0.1/localhost wtf

   Self-cite: <but miro bitcoin manager web gui also runs… (???)>

9. 
   kosuodhmwa commented at 10:56 am on July 31, 2024: none

   txindex = 1

   proxy = 127.0.0.1:9050 listen = 1 bind = 0.0.0.0

   server = 1 rpcallowip = 0.0.0.0 rpcbind = 0.0.0.0 rpcport = 8332

   rpcuser = ….. rpcusername = …..

   rpcpass = ….. rpcpassword = …..

   wallet = mywallet disablewallet=0

10. 
    pinheadmz commented at 10:57 am on July 31, 2024: member

    Cool. I didn’t see it in your screenshot in the original post and 403 is an authentication error. Since you are getting personal for some reason I am going to have to stop helping you and if you violate the comment policy at bitcoin-core/meta again you may be temporarily blocked from the repository.
11. 
    kosuodhmwa commented at 11:01 am on July 31, 2024: none

    sorry but that s**t really sucks
12. 
    maflcko commented at 11:11 am on July 31, 2024: member

    Usually the issue tracker is used to track technical issues related to the Bitcoin Core code base.

    General bitcoin questions and/or support requests are best directed to the Bitcoin StackExchange or the #bitcoin IRC channel on Libera Chat, or one of the Bitcoin subreddits, or any other place that you feel is well suited.

13. 
    maflcko commented at 12:17 pm on July 31, 2024: member

    Also, exposing the RPC to a remote over a public network is a security risk, see for example the release notes doc/release-notes/release-notes-0.18.0.md (section rpcallowip)
14. bitcoin deleted a comment on Jul 31, 2024
15. 
    willcl-ark commented at 11:17 am on August 1, 2024: member

    Closing this as this issue tracker is not for support questions.

    The comment above indicates some more appropriate venues to ask such support questions.

16. willcl-ark closed this on Aug 1, 2024

    ---

17. 
    kosuodhmwa commented at 10:37 pm on August 4, 2024: none

    ok thx
18. 
    kosuodhmwa commented at 7:46 pm on August 5, 2024: none

    Maybe the problem is a bug in master branch i’ve compiled from

Contributors
kosuodhmwa pinheadmz maflcko willcl-ark