Open yk-eta opened 1 year ago
I found that I am able to reproduce this error by spin up an instance without polycosm_boot on user data and run the boot script with ssh with command sudo su /usr/bin/env bash /opt/polycosm/polycosm_boot.sh aws aws
what is the different for script within user data and ssh? am I using a wrong command?
this issue happen when having multiple instance
the issue is also mentioned early in https://github.com/mozilla/hubs-cloud/issues/272
on my research, it happened when having multi instance, not regarding to customized on reticulum service.
When I tried to run a new AMI that running customized reticulum server with different origin, on service log spamming [info] TLS server: In state hello at tls_handshake.erl:212 generated SERVER ALERT: Fatal - Handshake Failure - malformed_handshake_data