BUG: Cannot connect to VM using planetary network from Windows

[nbabenko]

Hi, looks like there some problems with planetary network on windows, while it works well on OSX.

SSH Keys are set up properly for both machines.

See screenshots attached:

Error on windows:

Works on OSX:

Full VM's json:

          {
"version": 0,
"contractId": 30914,
"nodeId": 485,
"name": "VM5f4f256a",
"created": 1680979306,
"status": "ok",
"message": "",
"flist": "https://hub.grid.tf/tf-official-vms/ubuntu-22.04.flist",
"publicIP": null,
"planetary": "300:2137:d9ff:99e6:38a7:f882:cbc3:f560",
"interfaces": [
    {
        "network": "NWdfbdf57f",
        "ip": "10.20.2.2"
    }
],
"capacity": {
    "cpu": 4,
    "memory": 8192
},
"mounts": [
    {
        "name": "DISK6bbf8307",
        "mountPoint": "/",
        "size": 268435456000,
        "state": "ok",
        "message": ""
    }
],
"env": {
    "SSH_KEY": "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCvBeN99QCt0kEaRTK2WWTC72KqIyB76B/rIEJ/oUbIIRSTRpqp24PFC7ZvB9M9Q7Lsq3SAOYyW3vm5r1u8ndT9Kna08NZ/hZvRyxKfRBw4D4WuLvUuHoq1mZnJWOlB0mhzK2vi99ASvqLaXg6W3Eu1bqf7AWD+T9xqxTgTsMJZ2ihV9O8nIBkPTRdJSESNzrTO0BXB7D3+oZrZkkL2QFkke2r4fVDlWdMdRQbvhNwcwvbY1WKnHIpy+qbkUAoaQlgsgwjBy95YceNsLfaLmCLakq7Tp7gwIREul/jI7O+4AwTbB4tsj6otn3UuBw+HFDC+mma4GJkSmJr6+4mcTsVYaeQ5fQY32Sg/EW0S/5KMwJSTynXWCBH59R7sUNdHwG9YwbcCL2Rq+psnKRp4cLtYSztbjVtPcxGBVijNrMTQT55lrll2z3yig/XYj3SZri3JCmsUjB5J3p9RcM+wOdbZEThao8zEQp0pDS1Rza02PvUIFqTBgNPoKS+ZGfZQlZc= mykolababenko@Mykolas-MacBook-Air.local"
},
"entrypoint": "/init.sh",
"metadata": "{\"type\":\"Fullvm\",\"name\":\"VM5f4f256a\",\"projectName\":\"Fullvm\"}",
"description": "",
"rootfs_size": 0,
"corex": false

}

[shng4you]

Per your second image, you successfully did SSH via the planetary network. What error are you getting when you try to connect to a VM using Planetary?

[nbabenko]

ah, sorry, updated description. It works on OSX but does not work on Windows. The error is shown on the first screenshot.

[shng4you]

Not an issue at all. I suggest you regenerate the ssh key, reconfigure/redeploy the VM, and try again. Hopefully, it will work.

[nbabenko]

we tried this already several times

[shng4you]

So after reconfiguring/redeployment, are you still getting the same error? If yes, please share the entire error screenshot/log for further investigation.

[nbabenko]

Please see full screenshot on the first attached image. Please let me know how we can contact you to know details if you are looking for something else.