You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I successfully installed the 'myst' CLI on a Linux server. I was able to topping up my identity and list 'proposals'. However, when I try to issue the 'connect' command via either of the following methods:
The process hangs on 'CONNECTING' and the SSH connection gets disconnected with the following message: client_loop: send disconnect. broken pipe.
Until I perform a restart through the dashboard, I am unable to establish an SSH connection to the machine.
To Reproduce
Steps to reproduce the behavior:
ssh into linux server
myst connection up <provider-id>
ssh gets disconnected
Expected behavior
It's expected to see the result of connect command, whether connection was successful or not without disrupting ssh connection.
Environment (please complete the following information):
Node version: 1.29.20
OS: Linux 20.04.6 LTS (Focal Fossa)
Additional context
I am connected to the server by extending the SSH connectivity timeout using the following command: ssh -o ServerAliveInterval=300 root@<server-ip> to no vail.
IP forwarding is enabled.
All iptables rules are purged before using myst ( no conflicting rules) and all ports are open ( no firewall ).
I also tested it on a second VPS in a different datacenter; same issue: SSH gets disconnected on issuing the connect command.
consumer logs does not show any remarkable errors: sudo journalctl -u mysterium-consumer.service | grep ERR
May 06 07:59:24 8285 myst[12841]: 2024-05-06T07:59:24.485 ERR core/quality/mysterium_morqa.go:212 > Failed to sign metrics event error="failed to sign metrics event: authentication needed: password or unlock"
May 06 08:17:32 8285 myst[718]: 2024-05-06T08:17:32.789 ERR core/quality/mysterium_morqa.go:212 > Failed to sign metrics event error="failed to sign metrics event: authentication needed: password or unlock"
May 06 08:26:02 8285 myst[719]: 2024-05-06T08:26:02.472 ERR core/quality/mysterium_morqa.go:212 > Failed to sign metrics event error="failed to sign metrics event: authentication needed: password or unlock"
May 06 08:37:49 8285 myst[719]: 2024-05-06T08:37:49.435 ERR core/quality/mysterium_morqa.go:212 > Failed to sign metrics event error="failed to sign metrics event: authentication needed: password or unlock"
May 06 09:15:24 8285 myst[716]: 2024-05-06T09:15:24.641 ERR core/quality/mysterium_morqa.go:212 > Failed to sign metrics event error="failed to sign metrics event: authentication needed: password or unlock"
May 06 11:20:12 8285 myst[720]: 2024-05-06T11:20:12.737 ERR core/quality/mysterium_morqa.go:212 > Failed to sign metrics event error="failed to sign metrics event: authentication needed: password or unlock"
May 06 11:29:18 8285 myst[720]: 2024-05-06T11:29:18.206 ERR core/quality/mysterium_morqa.go:212 > Failed to sign metrics event error="failed to sign metrics event: authentication needed: password or unlock"
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the bug
I successfully installed the 'myst' CLI on a Linux server. I was able to topping up my identity and list 'proposals'. However, when I try to issue the 'connect' command via either of the following methods:
myst cli >> connect <my-identity> <provider-identity> wireguard
myst connection up <provider-identity>
The process hangs on 'CONNECTING' and the SSH connection gets disconnected with the following message:
client_loop: send disconnect. broken pipe
.Until I perform a restart through the dashboard, I am unable to establish an SSH connection to the machine.
To Reproduce
Steps to reproduce the behavior:
myst connection up <provider-id>
Expected behavior
It's expected to see the result of
connect
command, whether connection was successful or not without disrupting ssh connection.Environment (please complete the following information):
Additional context
ssh -o ServerAliveInterval=300 root@<server-ip>
to no vail.iptables
rules are purged before using myst ( no conflicting rules) and all ports are open ( no firewall ).sudo journalctl -u mysterium-consumer.service | grep ERR
The text was updated successfully, but these errors were encountered: