I'm repeatingly getting "socket recv error 104" errors and wallet/api seems to stuck.
debug.log shows this:
socket recv error 104
connect() to 104.238.169.50:44678 failed after select(): Connection refused
connect() to 54.37.91.251:44678 failed after select(): Connection refused
socket recv error 104
socket recv error 104
socket recv error 104
connect() to 45.32.89.169:48744 failed after select(): No route to host
connect() to 75.60.241.114:44678 failed after select(): Connection refused
socket sending timeout: 1201s
socket sending timeout: 1201s
While this is happening only killing the daemon helps as a stop using API doesn't seem to work anymore (no response, cli-client requesting stop using API stuck). Already had some BlockChain-DB "crashs" while forcing a hard stop by killing the daemon.
Is there any way to resolve this annoying procedure? May I need to activate IPv6 as my VM currently only has IPv4 behind NAT/Firewall.
Btw other wallets and masternodes are running fine on the same VM!
**edited**
I've enabled IPv6 to test if this will resolve the issue as other masternodes/clients may have IPv6 connection only?!