-
Notifications
You must be signed in to change notification settings - Fork 403
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Samourai Server] - JSON-RPC Error: jsonrpc field must be a string #1774
Comments
Hey @nmfretz , I understand you probably have a lot on your plate. I just wanted to gently remind you about this issue in case it got overlooked. The app has been broken for over two weeks, and I’d greatly appreciate an update when you have the chance. Thank you for your time and effort! |
Have the same issue, been using samurai server app a lot as a backend to sentinel app. |
Hey, @nmfretz any news on this? |
? Silence, no reaction or solution in almost 2 Month? Then you should remove Samurai server from your appstore as well if there is no solution for it or specter. |
@lukechilds @mayankchhabra @nmfretz Can you please take care of this? 🙏 |
Solved by todays umbrel update! Samurai server working perfectly as a backend to sentinel app again! Thanks umbrel team! |
Description:
I am encountering a recurring error with Samourai Server when it attempts to interact with Bitcoin Core. The error log shows the following message repeatedly:
See also here:
https://community.umbrel.com/t/samourai-broken-after-upgrade-bitcoin-core-to-28-0/19811
Steps to Reproduce:
Start Samourai Server and Bitcoin Core. Observe the error messages in the Samourai Server logs.
Expected Behavior:
Samourai Server should interact with Bitcoin Core without JSON-RPC field errors.
Actual Behavior:
The server logs an error indicating that the
jsonrpc
field must be a string, preventing normal operation.Troubleshooting Attempts:
Additional Information:
This error may indicate an incompatibility between the versions of Samourai Server and Bitcoin Core, or a possible configuration issue with JSON-RPC fields.
The text was updated successfully, but these errors were encountered: