Details
-
Type:
extRequest
-
Status: Closed
-
Priority:
Major
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: FIWARE-LAB-HELP
-
Labels:None
-
External Participants:
Description
so, I change my IP and bow can able ping VM, but get error when try to connect via ssh:
ubuntu@180.179.214.174: Permission denied (publickey).
(and, for sure, I used right key)
__________________________________________________________________________________________
You can get more information about our cookies and privacy policies on the following links:
fiware-lab-help mailing list
fiware-lab-help@lists.fiware.org
To unsubscribe from fiware-lab-help mailing list, go to the information page of the list at:
https://lists.fiware.org/listinfo/fiware-lab-help
[Created via e-mail received from: andrii3 <spivak.a.o@protonmail.com>]
Activity
Also, I can attach log of one of machines:
https://cloud.lab.fiware.org/project/instances/472c3504-9bfc-48c3-83e5-624a3914c058/console
@fla Looks like ticket was assigned to the team from wrong region.
The reason is because I recreate vm a lot of times. So for now - I launch vm with this ip 180.179.214.174 and don't terminate it.
Also, I can ping it, but can't ssh because of "permission denied" error.
Can you clarify please, which exactly details you await?
Sent from ProtonMail mobile
Hi, recently there is VM existed in your name on Our NOde.
You cannot SSH that Machine mentioned below. Which image you used to create the VM
195.134.187.34
Floating IPs:
180.179.214.174
Thanks & Regards
FI-lab Noida
Last time I use "ubuntu 20.04" image
Also, I try this images:
- ubuntu 16.04
- ubuntu 18.04
- ubuntu 14.04
- orion.docker
For all cases I used "ubuntu" username for ssh
(also, try "root", "fiware", "user" user-names)
In all cases I get same error
Also, I try to use "cloud-init" scripts, but didn't help
Sent from ProtonMail mobile
connected with user in Person on another platform.
Suggested Him necessary steps for accessing Vm using pem file mentioned below.
Security Groups
permission of pem file
ubuntu /centos user should be used firsttime.
user can access the machine. Closing the Ticket.
Also, it was issue with accessing to VM via "native" ip that I using (so I used VPN to change ip and get access to VM)
Sent from ProtonMail mobile
Also, I try to add cloud-init script to the VM (with pre-defined keys), but this not help and I still get the same error.
(Also, I don't see in VM log that any steps defined in 'cloud-init' happens)
Sent with [ProtonMail](https://protonmail.com/) Secure Email.