BitAxe doesn't connect if primary is Datum v0.4.0 server

[tlindi]

Note: Issues are not for customer support, configuration or discussion. For those topics please consult with your HW vendor or the OSMU Discord at: https://osmu.bitaxe.org

Describe the bug
If I configure my Datum service running on MyNodeBTC as primary pool on bitaxe, and eg ckpool as second. Bitaxe always connects to ckpool. But if I place exactly same datum settings as fallback, BitAxe connects to Datum correctly.

To Reproduce
Steps to reproduce the behavior:

1. Go to Poolsetup
2. set primary pool to datum
3. set fallback pool to some other pool
4. Restart bitaxe and Check logs
5. • You see it tries to connect to detam, but fallbacks without any error shown
6. Add datum also to fallback
7. Restart bitaxe and Check logs
8. You will see bitaxe connecting to datum.

Screenshots & Photos
Can deliver if needed.

Hardware (please complete the following information):

• Bitaxe HW version: 601
• Bitaxe HW vendor: * dunno *
• ESP-Miner FW version: 2.13.1 (BM1370)
• Hash Frequency: ( doesn't matter )
• Voltage: ( doesn't matter )
• Pool URL, Port, User: onprem Datum v0.4.0 on MyNodeBTC v0.3.40

Additional context
I have limited access to device so as many as needed debug advices appreciated given at once.

[mutatrum]

Is there a datum gateway publicly accessible, so we can test this?

[tlindi]

Unfor the one I encounted issue cant make public, but I could create clearnet one too.

How could I deliver address to it in private to you?

[mutatrum]

How could I deliver address to it in private to you?

Please join the OSMU Discord, that would make it easier.

[tlindi]

Will do. At latest Next friday when I'm back at BTCHEL Community Hub...