Skip to content

Instantly share code, notes, and snippets.

@leto
Created November 16, 2019 14:48
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save leto/04fa4988292c6bf88ea37d2d9b2cb774 to your computer and use it in GitHub Desktop.
Save leto/04fa4988292c6bf88ea37d2d9b2cb774 to your computer and use it in GitHub Desktop.
SilentDragon Wormhole Update

SD Wormhole Update

Just 24hrs ago, we were much further from having a wormhole. The service was down, there was no routing from port 443 to the localhost:7070 port that the wormhole runs on, we were not using CloudFlare and our SSL certs were not working correctly.

Now we have a WormHole running, where CloudFlare listens on wormhole.myhush.org:443 and sends data to our haproxy instance maps that to the wormhole backend running localhost:7070.

SDA can initiate a connection, and attempts to register a websocket sessionid. This is where things go wrong:

2019-11-16 15:04:14 INFO  Connected Session
2019-11-16 15:04:14 INFO  Register f288285db0eee1432cbf97893953aa5e3fb8ab8282c32e9c0704c7d3ce1fc650[(register, f288285db0...{64})]
2019-11-16 15:04:14 INFO  Error: Peer is not connected[(nonce, 1600000000...{48}), (payload, 66cb90afb4...{544}), (to, f288285db0...{64})]
2019-11-16 15:04:14 INFO  Closed session f288285db0eee1432cbf97893953aa5e3fb8ab8282c32e9c0704c7d3ce1fc650
2019-11-16 15:05:16 INFO  Connected Session

This wormhole log shows that SDA connects correctly, sends a registration message, but then the next message it attempts to send, creates an error because there is no sessionid existing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment