selsta
selsta
ping @saravananp-001, can you reply to the above comment?
We don't want to support any integrated subaddresses at all. This was an intentional decision. At best I'm for adding code that blocks sending to integrated subaddresses in all cases.
I'm quite sure that the HTTP code is not the same as the return code? Also can you show what command you are executing?
> but http response code is always 200 even if there is an error. https://softwareengineering.stackexchange.com/a/305294 Seeing that this is an application related error (monero-wallet-rpc being the application), I don't think...
Also again, please post the input examples, not only response.
What cap did you set at 25? Also are these connections on port 18080 (P2P) or 18081 (RPC)? Is your port 18081 open?
From what I can tell there is nothing relevant to your issue changed between v0.17.3.0 and v0.17.3.2. Maybe you simply didn't look for it with the old version? Regarding json...
What exactly is UptimeRobot.com checking? RPC availability?
It's difficult to tell. I think there are different issues at play here. RPC being unresponsive is related to a bug fixed in #7760, as I wrote in my previous...
Yes, because the current SSL code for RPC has bugs.