If it’s a docker install originally, then we hide the private address as you never need to change it.
I’m wondering though if you have an incorrect value in there, causing your slow maintenance run.
You can check by connecting to MySQL, and running the following SQL:
SELECT setting, value from setting where setting like "XMR_%";
That should show you the XMR public and private address. The public address is inconsequential from the point of view of slow running Daily Maintenance task. If it’s wrong, the Players won’t be able to connect to XMR, but that’s not the issue we’re troubleshooting here. The XMR_ADDRESS is the one we’re concerned with. That should be set to
tcp://cms-xmr:50001
If it’s not, we have our culprit, and you can set it correctly by running the following SQL:
UPDATE setting set value="tcp://cms-xmr:50001" where setting="XMR_ADDRESS";
Instructions on connecting to MySQL are here:
If that isn’t the issue, then I think we’re at the stage where I need to see this first hand. I’ll need a copy of your data sent over (if you’re happy to do that) so I can recreate here and see what the issue is. If you want to do that, I can send over details of how to send your data to us.