Login Error Code 5

[Ranchdad86]

The changelog says support for rx/yada was added to the proxy for 6.22, but I cannot get it to work.

When I set up the config on xmrig-proxy I get "login error code 5" Tried several tweaks to the config and a secondary pool to the same effect.

When I use the same config directly from xmrig, no login error so seems to be a proxy specific issue. Any ideas?

[Ranchdad86]

I have tried multiple config tweaks, and tried both pool and local node mining. All give the same login code error. The same config on the XMRIG miner going direct works fine. It's almost like something is missing in the proxy update to let it connect to YDA?

[xmrig]

What pool do you use? And you can't mine this coin directly (solo) to daemon.
Thank you.

[Ranchdad86]

I'm mining it directly to my own node. It is working fine using Xmrig miner 6.22 but not the proxy.

As far as pool I used the main yada coin pool as well as the secondary. Both pools gave the same error. As did mining to my node.

However when I use the same config and pools and go directly from Xmrig bypassing the proxy it works fine.

That is what is leading me to believe there is an issue with the proxy or something didn't get configured correctly.

I've been using XM proxy for quite a while on multiple other coins with no issue. I tried using various configurations and even copied and pasted my config from the older version of The proxy that was working fine and tried just changing the pool and wallet information and algo. I went line by line comparing to my configuration that is working fine in XM rig and there is nothing different between them that should be causing a login error.

[xmrig]

@pdxwebdev The proxy has a slightly different user agent string; anyway what exactly deal with a long target?
@Ranchdad86 As a temporary solution you can set global option "user-agent": "XMRig/6".

[pdxwebdev]

@pdxwebdev The proxy has a slightly different user agent string; anyway what exactly deal with a long target? @Ranchdad86 As a temporary solution you can set global option "user-agent": "XMRig/6".

No worries, we'll fix this on our end and deploy today.

[pdxwebdev]

The fix is now released. @Ranchdad86 please update your node with git pull origin master --tags, restart the node, and test.