Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SERVER ALERT: Fatal - Handshake Failure - malformed_handshake_data #696

Open
yk-eta opened this issue Mar 12, 2023 · 4 comments
Open

SERVER ALERT: Fatal - Handshake Failure - malformed_handshake_data #696

yk-eta opened this issue Mar 12, 2023 · 4 comments

Comments

@yk-eta
Copy link

yk-eta commented Mar 12, 2023

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

@yk-eta
Copy link
Author

yk-eta commented Mar 23, 2023

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

@yk-eta
Copy link
Author

yk-eta commented Mar 23, 2023

what is the different for script within user data and ssh? am I using a wrong command?

@yk-eta
Copy link
Author

yk-eta commented Mar 25, 2023

this issue happen when having multiple instance

@yk-eta
Copy link
Author

yk-eta commented Mar 26, 2023

the issue is also mentioned early in
Hubs-Foundation/hubs-cloud#272

on my research, it happened when having multi instance, not regarding to customized on reticulum service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant