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

FIWARE.Question.Lab.Spain.Unable to Access Filab Instace via SSH.

    Details

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

      Description

      Created question in FIWARE Q/A platform on 10-04-2015 at 01:04
      Please, ANSWER this question AT https://stackoverflow.com/questions/29550573/unable-to-access-filab-instace-via-ssh

      Question:
      Unable to Access Filab Instace via SSH

      Description:
      I have followed this guide (the only difference I noticed is that in the guide there is no "network selection" step, but I selected one when creating the instance).

      I have already created a security group with all ports open (TCP, UDP and ICMP), the Keypair and the floating IP. The problem is that I can not even ping the floating IP, which is currently assigned to a running instance. Therefore, I am unable to access it via SSH.

      I am working with Spain2. The floating IP is 130.206.114.76

        Activity

        fla Fernando Lopez made changes -
        Fix Version/s 2021 [ 12600 ]
        backlogmanager Backlog Manager made changes -
        Summary FIWARE.Question.Tech.Unable to Access Filab Instace via SSH. FIWARE.Question.Lab.Spain.Unable to Access Filab Instace via SSH.
        fla Fernando Lopez made changes -
        Assignee Backlog Manager [ backlogmanager ]
        fla Fernando Lopez made changes -
        Description
        Created question in FIWARE Q/A platform on 10-04-2015 at 01:04
        {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/29550573/unable-to-access-filab-instace-via-ssh


        +Question:+
        Unable to Access Filab Instace via SSH

        +Description:+
        I have followed this guide (the only difference I noticed is that in the guide there is no "network selection" step, but I selected one when creating the instance).

        I have already created a security group with all ports open (TCP, UDP and ICMP), the Keypair and the floating IP. The problem is that I can not even ping the floating IP, which is currently assigned to a running instance. Therefore, I am unable to access it via SSH.

        I am working with Spain2. The floating IP is 130.206.114.76
        Created question in FIWARE Q/A platform on 10-04-2015 at 01:04
        {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/29550573/unable-to-access-filab-instace-via-ssh


        +Question:+
        Unable to Access Filab Instace via SSH

        +Description:+
        I have followed this guide (the only difference I noticed is that in the guide there is no "network selection" step, but I selected one when creating the instance).

        I have already created a security group with all ports open (TCP, UDP and ICMP), the Keypair and the floating IP. The problem is that I can not even ping the floating IP, which is currently assigned to a running instance. Therefore, I am unable to access it via SSH.

        I am working with Spain2. The floating IP is 130.206.114.76
        HD-Node Spain [ 10846 ]
        fla Fernando Lopez made changes -
        Component/s FIWARE-LAB-HELP [ 10279 ]
        Component/s FIWARE-TECH-HELP [ 10278 ]
        backlogmanager Backlog Manager made changes -
        Summary [fiware-stackoverflow] Unable to Access Filab Instace via SSH FIWARE.Question.Tech.Unable to Access Filab Instace via SSH.
        backlogmanager Backlog Manager made changes -
        Resolution Done [ 10000 ]
        Status Answered [ 10104 ] Closed [ 6 ]
        backlogmanager Backlog Manager made changes -
        Status In Progress [ 3 ] Answered [ 10104 ]
        backlogmanager Backlog Manager made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        backlogmanager Backlog Manager made changes -
        Field Original Value New Value
        Component/s FIWARE-TECH-HELP [ 10278 ]
        backlogmanager Backlog Manager created issue -

          People

          • Assignee:
            backlogmanager Backlog Manager
            Reporter:
            backlogmanager Backlog Manager
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: