You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Currently requests from localhost which have an incorrect rpc_pass will earn an IP ban. This is most often due to an older / competing app, script or docker container sending a request to 127.0.0.1:7783, with the effect of rendering the newer or competing instance (or both) unresponsive, and logs full of Your ip is banned.
Proposed solution
A new config param for MM2.json with the effect of not counting failed requests from localhost (or rpc_ip) towards an IP ban. In the event of a local request failing to authenticate, the rpc should respond withincorrect credentials from localhost or rpc_ip without it causing a denial of service for aithenticated requests from the same defined source.
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently requests from localhost which have an incorrect rpc_pass will earn an IP ban. This is most often due to an older / competing app, script or docker container sending a request to
127.0.0.1:7783
, with the effect of rendering the newer or competing instance (or both) unresponsive, and logs full ofYour ip is banned
.Proposed solution
A new config param for MM2.json with the effect of not counting failed requests from localhost (or
rpc_ip
) towards an IP ban. In the event of a local request failing to authenticate, the rpc should respond withincorrect credentials from localhost or rpc_ip
without it causing a denial of service for aithenticated requests from the same defined source.The text was updated successfully, but these errors were encountered: