Log file still empty. TFW you wish something broke so you can know why...
@greg Just FYI: the ElasticSearch job ran through successfully, and I get search results for posts back to 2017 now.
I have just successfully set up the multi-sig community wallet in BTCPay (with the Kosmos Accounts store), and after re-scanning the chain for transactions it now also displays the past txs and correct balance.
New receiving addresses are now correctly generated/displayed from the next unused derivation path.
You can see txs, and a valid receiving address in the attached screenshots.
@greg I was thinking about the most simple, low-tech, and stable solution for updating postgres the master address, and my last idea was:
- Configure clients to use a hostname instead of IP address for the master connection (the obvious first step)
- Write a script (maybe just postgres client Chef recipe), which simply updates an
/etc/hostsentry on all postgres client VMs
This way, we don't need our own DNS server at all, and there's no extra connection or caching to think about. WDYT?
Just a quick status update: the log file is still empty, and the two nodes are still connected.