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

FIWARE.Request.Lab.Spain.Cannot access console of a VM within the FI-LAB region

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: Sprint 4.1.1
    • Component/s: FIWARE-LAB-HELP
    • Labels:
      None
    • HD-Node:
      Spain

      Description

      Hi,
      I created a VM (id: 8772b308-bd75-4dd9-b0d4-4a3c735a7b67) in the FI-LAB
      region. When I try to access its console over the dashboard, my browser
      tells me that it cannot connect (Instances -> ... -> Connection -> View
      display). And indeed, this is what curl reports (token removed for obvious
      reasons):

      $ curl -v http://130.206.82.10:6080/vnc_auto.html?token=...

      • Hostname was NOT found in DNS cache
      • Trying 130.206.82.10...
      • Adding handle: conn: 0x7f450d71b610
      • Adding handle: send: 0
      • Adding handle: recv: 0
      • Curl_addHandleToPipeline: length: 1
      • - Conn 0 (0x7f450d71b610) send_pipe: 1, recv_pipe: 0
      • connect to 130.206.82.10 port 6080 failed: Connection refused
      • Failed to connect to 130.206.82.10 port 6080: Connection refused
      • Closing connection 0

      curl: (7) Failed to connect to 130.206.82.10 port 6080: Connection refused

      With kind regards,
      Jan


      Trojitá, a fast Qt IMAP e-mail client – http://trojita.flaska.net/
      _______________________________________________
      Fiware-lab-help mailing list
      Fiware-lab-help@lists.fi-ware.org
      https://lists.fi-ware.org/listinfo/fiware-lab-help

        Activity

        Hide
        FIWARE-LAB-HELP FIWARE-LAB-HELP added a comment -

        No, in fact you can't access VNC in this node. We'll correct this in the
        future.

        Best regards,
        José Ignacio.

        El 19/05/14 12:08, Jan Kundrát escribió:
        > Hi,
        > I created a VM (id: 8772b308-bd75-4dd9-b0d4-4a3c735a7b67) in the
        > FI-LAB region. When I try to access its console over the dashboard, my
        > browser tells me that it cannot connect (Instances -> ... ->
        > Connection -> View display). And indeed, this is what curl reports
        > (token removed for obvious reasons):
        >
        > $ curl -v http://130.206.82.10:6080/vnc_auto.html?token=...
        > * Hostname was NOT found in DNS cache *
        > Trying 130.206.82.10... * Adding handle:
        > conn: 0x7f450d71b610 * Adding handle: send: 0
        > * Adding handle: recv: 0
        > * Curl_addHandleToPipeline: length: 1
        > * - Conn 0 (0x7f450d71b610) send_pipe: 1,
        > recv_pipe: 0 * connect to 130.206.82.10 port
        > 6080 failed: Connection refused * Failed to
        > connect to 130.206.82.10 port 6080: Connection refused
        > * Closing connection 0
        > curl: (7) Failed to connect to 130.206.82.10
        > port 6080: Connection refused
        >
        > With kind regards,
        > Jan
        >

        ________________________________

        Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
        This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
        http://www.tid.es/ES/PAGINAS/disclaimer.aspx
        _______________________________________________
        Fiware-lab-help mailing list
        Fiware-lab-help@lists.fi-ware.org
        https://lists.fi-ware.org/listinfo/fiware-lab-help

        Show
        FIWARE-LAB-HELP FIWARE-LAB-HELP added a comment - No, in fact you can't access VNC in this node. We'll correct this in the future. Best regards, José Ignacio. El 19/05/14 12:08, Jan Kundrát escribió: > Hi, > I created a VM (id: 8772b308-bd75-4dd9-b0d4-4a3c735a7b67) in the > FI-LAB region. When I try to access its console over the dashboard, my > browser tells me that it cannot connect (Instances -> ... -> > Connection -> View display). And indeed, this is what curl reports > (token removed for obvious reasons): > > $ curl -v http://130.206.82.10:6080/vnc_auto.html?token= ... > * Hostname was NOT found in DNS cache * > Trying 130.206.82.10... * Adding handle: > conn: 0x7f450d71b610 * Adding handle: send: 0 > * Adding handle: recv: 0 > * Curl_addHandleToPipeline: length: 1 > * - Conn 0 (0x7f450d71b610) send_pipe: 1, > recv_pipe: 0 * connect to 130.206.82.10 port > 6080 failed: Connection refused * Failed to > connect to 130.206.82.10 port 6080: Connection refused > * Closing connection 0 > curl: (7) Failed to connect to 130.206.82.10 > port 6080: Connection refused > > With kind regards, > Jan > ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help
        Hide
        FIWARE-LAB-HELP FIWARE-LAB-HELP added a comment -

        Hi Jan

        Thanks for contacting us. VNC is not able in FI-LAB region. You can access to the VM by ssh. We have some videos in lab.fi-ware.org, which can help you.
        Regards,
        Henar

        ----Mensaje original----
        De: fiware-lab-help-bounces@lists.fi-ware.org fiware-lab-help-bounces@lists.fi-ware.org En nombre de Jan Kundrát
        Enviado el: lunes, 19 de mayo de 2014 12:08
        Para: fiware-lab-help@lists.fi-ware.org
        Asunto: [Fiware-lab-help] Cannot access console of a VM within the FI-LAB region

        Hi,
        I created a VM (id: 8772b308-bd75-4dd9-b0d4-4a3c735a7b67) in the FI-LAB region. When I try to access its console over the dashboard, my browser tells me that it cannot connect (Instances -> ... -> Connection -> View display). And indeed, this is what curl reports (token removed for obvious
        reasons):

        $ curl -v http://130.206.82.10:6080/vnc_auto.html?token=...

        • Hostname was NOT found in DNS cache
        • Trying 130.206.82.10...
        • Adding handle: conn: 0x7f450d71b610
        • Adding handle: send: 0
        • Adding handle: recv: 0
        • Curl_addHandleToPipeline: length: 1
        • - Conn 0 (0x7f450d71b610) send_pipe: 1, recv_pipe: 0
        • connect to 130.206.82.10 port 6080 failed: Connection refused
        • Failed to connect to 130.206.82.10 port 6080: Connection refused
        • Closing connection 0

        curl: (7) Failed to connect to 130.206.82.10 port 6080: Connection refused

        With kind regards,
        Jan


        Trojitá, a fast Qt IMAP e-mail client – http://trojita.flaska.net/ _______________________________________________
        Fiware-lab-help mailing list
        Fiware-lab-help@lists.fi-ware.org
        https://lists.fi-ware.org/listinfo/fiware-lab-help

        ________________________________

        Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
        This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
        http://www.tid.es/ES/PAGINAS/disclaimer.aspx
        _______________________________________________
        Fiware-lab-help mailing list
        Fiware-lab-help@lists.fi-ware.org
        https://lists.fi-ware.org/listinfo/fiware-lab-help

        Show
        FIWARE-LAB-HELP FIWARE-LAB-HELP added a comment - Hi Jan Thanks for contacting us. VNC is not able in FI-LAB region. You can access to the VM by ssh. We have some videos in lab.fi-ware.org, which can help you. Regards, Henar ---- Mensaje original ---- De: fiware-lab-help-bounces@lists.fi-ware.org fiware-lab-help-bounces@lists.fi-ware.org En nombre de Jan Kundrát Enviado el: lunes, 19 de mayo de 2014 12:08 Para: fiware-lab-help@lists.fi-ware.org Asunto: [Fiware-lab-help] Cannot access console of a VM within the FI-LAB region Hi, I created a VM (id: 8772b308-bd75-4dd9-b0d4-4a3c735a7b67) in the FI-LAB region. When I try to access its console over the dashboard, my browser tells me that it cannot connect (Instances -> ... -> Connection -> View display). And indeed, this is what curl reports (token removed for obvious reasons): $ curl -v http://130.206.82.10:6080/vnc_auto.html?token= ... Hostname was NOT found in DNS cache Trying 130.206.82.10... Adding handle: conn: 0x7f450d71b610 Adding handle: send: 0 Adding handle: recv: 0 Curl_addHandleToPipeline: length: 1 - Conn 0 (0x7f450d71b610) send_pipe: 1, recv_pipe: 0 connect to 130.206.82.10 port 6080 failed: Connection refused Failed to connect to 130.206.82.10 port 6080: Connection refused Closing connection 0 curl: (7) Failed to connect to 130.206.82.10 port 6080: Connection refused With kind regards, Jan – Trojitá, a fast Qt IMAP e-mail client – http://trojita.flaska.net/ _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help ________________________________ Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at: http://www.tid.es/ES/PAGINAS/disclaimer.aspx _______________________________________________ Fiware-lab-help mailing list Fiware-lab-help@lists.fi-ware.org https://lists.fi-ware.org/listinfo/fiware-lab-help

          People

          • Assignee:
            jicg José Ignacio Carretero Guarde
            Reporter:
            fw.ext.user FW External User
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: