...
| Tip |
|---|
If the "Hot Wallet" test finished successfully, you've configured the BitGo Wallet properly! |
...
Troubleshooting Tips:
The Hot Wallet BUY test should be your focus. The other tests are irrelevant in this scope.
The master log will contain relevant information regarding any failures during the test.
Is your tunnel working?
You’ll see this in the log if the tunnel is connecting correctly:
DEBUG com.generalbytes.batm.server.e.b - opening new tunnel on port 22222, remoteWalletAddress: xxx.xxx.xxx.xxx:3080DEBUG com.generalbytes.batm.server.e.b - tunnel connected: ClientSessionImpl[batmsshtunnel@yyy.yyy.yyy.yyy/yyy.yyy.yyy.yyy:22222] 42087->3080
this indicates a secure connection is active between CAS (
yyy.yyy.yyy.yyy) and your BitGo Node (xxx.xxx.xxx.xxx). If you don’t see “connected”, then please double-check your tunnel password.
Have you whitelisted your BitGo Express node in your BitGo API keys?
See the instructions above.
BitGo must permit your BitGo Express node to connect to it’s network.