Heya, this is interesting! NATS websockets seems like a good method of cross-communication between instances. Unfortunately, the nats-cluster example fails to deploy.
First deploy fails with critical errors. Likewise, adding regions fails. Authentication failure?
ord [info]nats-server | [557] [INF] Connecting to explicit gateway "cdg" (fly-local-6pn:7222) at [fdaa:0:4cc2:a7b:7d:c7bc:5829:2]:7222 (attempt 1)
ord [info]nats-server | [557] [INF] [fdaa:0:4cc2:a7b:7d:c7bc:5829:2]:7222 - gid:8 - Creating outbound gateway connection to "cdg"
ord [info]nats-server | [557] [INF] [fdaa:0:4cc2:a7b:7d:c7bc:5829:2]:48256 - gid:9 - Processing inbound gateway connection
ord [info]nats-server | [557] [ERR] [fdaa:0:4cc2:a7b:7d:c7bc:5829:2]:7222 - gid:8 - Failing connection to gateway "cdg", remote gateway name is "ord"
ord [info]nats-server | [557] [INF] [fdaa:0:4cc2:a7b:7d:c7bc:5829:2]:7222 - gid:8 - Gateway connection closed: Wrong Gateway
ord [info]nats-server | [557] [ERR] [fdaa:0:4cc2:a7b:7d:c7bc:5829:2]:48256 - gid:9 - authentication error
ord [info]nats-server | [557] [INF] [fdaa:0:4cc2:a7b:7d:c7bc:5829:2]:48256 - gid:9 - Gateway connection closed: Authentication Failure
Is this to be expected?