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
I noticed recently that Mycelium wasn't working for me (no action on attempts to connect to SSH or ping other machines), even though it appeared to start up and run normally. After a bit of experimentation, I found that replacing my private key solved the problem.
While I can continue to use the network with a different key and IP, it's obviously not great if a given identity can suddenly become effectively invalid for use on the network without any obvious error being logged.
Here's a logfile generated with the debug flag enabled, showing what happens for about a minute after Mycelium starts up with this key file chosen. I also let a ping command to another Mycelium host run while capturing this log.
I noticed recently that Mycelium wasn't working for me (no action on attempts to connect to SSH or ping other machines), even though it appeared to start up and run normally. After a bit of experimentation, I found that replacing my private key solved the problem.
While I can continue to use the network with a different key and IP, it's obviously not great if a given identity can suddenly become effectively invalid for use on the network without any obvious error being logged.
Here's a logfile generated with the debug flag enabled, showing what happens for about a minute after Mycelium starts up with this key file chosen. I also let a ping command to another Mycelium host run while capturing this log.
myc.log
I'm also happy to donate the private key file to science, if anyone wants to have a poke at it.
The text was updated successfully, but these errors were encountered: