Closed tmitchell closed 4 years ago
For posterity, it currently resolves as a CNAME to me-krypt-co-800488383.us-east-1.elb.amazonaws.com
Not anymore.
Apologies this test server was moved.
ssh me.krypt.co
should now be deployed and working again.
The post-setup instructions say to attempt to ssh to
me.krypt.co
but this is failing with a DNS lookup error:For posterity, it currently resolves as a CNAME to
me-krypt-co-800488383.us-east-1.elb.amazonaws.com