Hello,
1. I am not sure why only IPv6 worked. In any case running your wallets on a home machine is tricky. If it works now, then that means that you’ve set up NAT forwarding correctly. Don’t forget to put your machine and modem on a UPS for maximum uptime. Also, you’ll need a static IP for this to work. If your residential modem restarts or reconnects and you have a dynamic IP, it will be different each time.
2. The “Renew deposit addresses” feature simply marks all deposit addresses as “old”. Next time the user logs in to the frontend they will be assigned a new deposit address. I am not sure why this happens but I will test with the latest Bitcoin core and will report back. In the meantime you can check your wallet’s log file, or enable WordPress logging and check the debug log for any problems. If there is an issue it will show up when you call the get_coins_info endpoint: (https://www.example.com/?__wallets_apiversion=3&__wallets_action=get_coins_info)
There shouldn’t be any problem with bech32 addresses as far as the plugin is concerned. If you want to force your wallet to generate another type of address, you can set addresstype in your conf file. Consult bitcoin-cli help getnewaddress for details.
I will test with 0.19.1 and get back to you.
with regards