How to debug RPC 500 Internal Server Error ? #12673

issue congnghiakhiem opened this issue on March 12, 2018

congnghiakhiem commented at 5:44 AM on March 12, 2018: none
walletpassphrase
- About to connect() to 10.130.xx.xx port 8332 (#1)
- Trying 10.130.xx.xx...
- Connected to 10.130.xx.xx (10.130.xx.xx) port 8332 (#1)
- Server auth using Basic with user 'xxx'
POST / HTTP/1.1 Authorization: Basic xxx== Accept: / Host: 10.130.xx.xx:8332 Content-Type: application/json Content-Length: 113
- upload completely sent off: 113 out of 113 bytes < HTTP/1.1 500 Internal Server Error < Content-Type: application/json < Date: Mon, 12 Mar 2018 05:34:31 GMT < Content-Length: 984 <
- Connection #1 to host 10.130.xx.xx left intact NULL
I have set debug=rpc. But I've only got 2018-03-12 05:34:31 ThreadRPCServer method=walletpassphrase How to find out the error ?
fanquake added the label RPC/REST/ZMQ on Mar 12, 2018
achow101 commented at 2:45 PM on March 12, 2018: member

A HTTP 500 error still returns JSON formatted data containing the error. It looks like your client isn't reading it/displaying it to you.
laanwj commented at 2:23 PM on March 14, 2018: member

Please ask questions about use of the RPC API on the bitcoin stack exchange, not on the bug tracker.
laanwj closed this on Mar 14, 2018
ramontayag referenced this in commit a58d0c37e6 on Feb 5, 2019
ramontayag referenced this in commit ff585c461d on Feb 5, 2019
MarcoFalke locked this on Sep 8, 2021

Contributors

Labels