I have done extensive testing on this problem and need some help to resolve it, probably from someone on the technical side of the house.
If I am connected to a certain VPN provider and then start the ETH mainnet and the Incognito mainnet, the ETH starts and runs just fine, but the Incognito mainnet crashes instantly. This occurs when using the most up-to-date Docker image.
Doesn’t work: Connect server to “problem” VPN, start inc/eth mainnets, inc_mainnet crash/restart.
Does work: Start inc/eth mainnets using different VPN, switch server to “problem” VPN, both mainnets work and are actively using the “problem” VPN IP (which means it’s not really the problem).
- Other non-VPN IPs and other VPN providers do not cause this problem.
- All tested IPs from this one VPN provider cause issues.
- It is not a network configuration issue on the server machine (see following points).
- Same results occur whether the server is being routed through a VPN-connected router or the VPN client is being run locally on the server.
- Allowing the inc_mainnet to start and then switching to the VPN allows it to keep running while connected to the VPN.
- I confirmed the inc_mainnet was using the VPN IP, even when switching to the VPN after starting inc_mainnet, so there is not a problem with the VPN. I can even connect to the inc_mainnet server VPN IP:port successfully.
- Is there any way to enable or view logging from the container that might explain why it’s crashing?
- Can someone help me comb through the source code to find what might be causing the issue? I glanced at the source code (https://github.com/incognitochain/incognito-chain), but I don’t have nearly enough time to do this cold. I need someone already familiar with it. Since it only happens with this VPN provider, I suspect it’s an issue with DNS or something, or it’s calling out to a service that is blocking this VPN. I need to find out what exactly.