Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-6840

FIWARE.Request.Lab.FIWARE Lab Assistance.

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-LAB-HELP
    • Labels:
      None

      Description

      Hi.

      I am not able to ssh my newly created instance by using my keypair. Always get the same message:

      ssh -i /drives/c/Users/A115764/Downloads/AGU_KP.pem root@130.206.115.215
      ##################################################################################
      NOTE: You have accessed a system owned by FIWARE Lab. You must have authorisation
      before using it, and your use will be strictly limited to that indicated in the
      authorisation.
      Unauthorised access to this system or improper use of the same is prohibited and
      is against the FIWARE Terms & Conditions Policy and the legislation in force. The
      use of this system may be monitored.
      #################################################################################

      Permission denied (publickey,gssapi-keyex,gssapi-with-mic).

      I have created and terminated the machine N times and tried almost everything.

      This is the instance

      • Name: AGU
      • ID: b9dadd7b-284a-479d-98a8-230728460036
      • Status: ACTIVE

      What am I doing wrong?

      Thanks in advance.

      This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it.
      As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

      Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional.
      Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje.
      Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes.
      Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus.

      Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
      Please, send your messages using the new domain (Fiware-lab-help@lists.fiware.org) instead of the old one.
      _______________________________________________
      Fiware-lab-help mailing list
      Fiware-lab-help@lists.fiware.org
      https://lists.fiware.org/listinfo/fiware-lab-help
      [Created via e-mail received from: "Aguero Blanco, Francisco Javier" <francisco.aguero@atos.net>]

        Activity

        Hide
        fla Fernando Lopez added a comment -

        For security reasons the root access is disabled for access, depends if you deploy an instance with ubuntu or centos you should use the ubuntu or centos user to access to your server.

        Please use those users to access to the server and tell us if the error persist.

        Show
        fla Fernando Lopez added a comment - For security reasons the root access is disabled for access, depends if you deploy an instance with ubuntu or centos you should use the ubuntu or centos user to access to your server. Please use those users to access to the server and tell us if the error persist.
        Hide
        fw.ext.user FW External User added a comment -

        Comment by francisco.aguero@atos.net :

        I used the ubuntu user and worked like a charm. I suggest you to change the "connect" instructions you provide.

        Thank you very much!

        -

        Show
        fw.ext.user FW External User added a comment - Comment by francisco.aguero@atos.net : I used the ubuntu user and worked like a charm. I suggest you to change the "connect" instructions you provide. Thank you very much! -
        Hide
        fla Fernando Lopez added a comment -

        What do you mean? Please give me details about that instructions in order to see how to change.

        Show
        fla Fernando Lopez added a comment - What do you mean? Please give me details about that instructions in order to see how to change.
        Hide
        fw.ext.user FW External User added a comment -

        Comment by francisco.aguero@atos.net :

        This is what the cloud lab says....

        Ubuntu/Mac terminal

        Open the Terminal
        Locate the keypair asocciate to this Instance when launching it.
        my_keypair.pem

        Modify the keypair permissions in order to make it not publicly viewable.
        chmod 400 my_keypair.pem

        Connect to the Instance using its public IP.
        ssh -i my_keypair.pem root@130.206.114.146

        Please note that the last command indicates the use of the root user.

        Regards

        -

        Show
        fw.ext.user FW External User added a comment - Comment by francisco.aguero@atos.net : This is what the cloud lab says.... Ubuntu/Mac terminal Open the Terminal Locate the keypair asocciate to this Instance when launching it. my_keypair.pem Modify the keypair permissions in order to make it not publicly viewable. chmod 400 my_keypair.pem Connect to the Instance using its public IP. ssh -i my_keypair.pem root@130.206.114.146 Please note that the last command indicates the use of the root user. Regards -
        Hide
        fla Fernando Lopez added a comment -

        We contact the user and see the problem. It is something that have to be cnaged in development, we will create a ticket in order to be resolved during this sprint.

        Fernando

        Show
        fla Fernando Lopez added a comment - We contact the user and see the problem. It is something that have to be cnaged in development, we will create a ticket in order to be resolved during this sprint. Fernando
        Hide
        fla Fernando Lopez added a comment -

        Created a ticket in Cloud Chapter to resolve the issue.

        Show
        fla Fernando Lopez added a comment - Created a ticket in Cloud Chapter to resolve the issue.

          People

          • Assignee:
            fla Fernando Lopez
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: