ML
    • Register
    • Login
    • Search
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups

    Can't Connect to AWS Server

    IT Discussion
    3
    11
    1106
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • thanksajdotcom
      thanksajdotcom last edited by

      So I tried setting up SSH trust between my locally-hosted SSH servers and the AWS server currently hosting my website. In that process, something got borked. Amazon uses public and private keys for additional levels of security and to ssh, you must have the public key. The issue is that now the public key is not being recognized, so I've totally lost SSH access to my server, which being it's Ubuntu Server, that means I've totally lost access. I'm also under the Basic plan for AWS, which doesn't include technical support. Is my only option to rebuild at this point? I can do it but it's a pain...

      Thanks,
      A.J.

      1 Reply Last reply Reply Quote -1
      • Ambarishrh
        Ambarishrh last edited by Ambarishrh

        Do you get any errors while connecting? What's the output when you ssh with -vvv switch?

        1 Reply Last reply Reply Quote 0
        • Ambarishrh
          Ambarishrh last edited by

          -v Verbose mode. Causes ssh to print debugging messages about its
          progress. This is helpful in debugging connection, authentica-
          tion, and configuration problems. Multiple -v options increase
          the verbosity. The maximum is 3.

          thanksajdotcom 1 Reply Last reply Reply Quote 0
          • thanksajdotcom
            thanksajdotcom @Ambarishrh last edited by

            @Ambarishrh said:

            -v Verbose mode. Causes ssh to print debugging messages about its
            progress. This is helpful in debugging connection, authentica-
            tion, and configuration problems. Multiple -v options increase
            the verbosity. The maximum is 3.

            It's rejecting the private key, which started after I tried to establish trust. I just don't know how to fix it when I can't get any console access to the machine.

            1 Reply Last reply Reply Quote 0
            • scottalanmiller
              scottalanmiller last edited by

              That's one of the reasons that I like CloudatCost vs. Amazon. Amazon is amazing, but the lack of console access and the necessity of keys is a big deal. Amazon expects you to treat everything as a true cloud and if you don't, well, there are risks. Things like this that until you deal with a pure cloud solution you don't realize how difficult and risky things can be.

              thanksajdotcom 1 Reply Last reply Reply Quote 3
              • thanksajdotcom
                thanksajdotcom @scottalanmiller last edited by

                @scottalanmiller said:

                That's one of the reasons that I like CloudatCost vs. Amazon. Amazon is amazing, but the lack of console access and the necessity of keys is a big deal. Amazon expects you to treat everything as a true cloud and if you don't, well, there are risks. Things like this that until you deal with a pure cloud solution you don't realize how difficult and risky things can be.

                Hmm...it is frustrating for sure...

                1 Reply Last reply Reply Quote 0
                • Ambarishrh
                  Ambarishrh last edited by

                  http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html#TroubleshootingInstancesServerError

                  Did you check this?

                  thanksajdotcom 1 Reply Last reply Reply Quote 0
                  • thanksajdotcom
                    thanksajdotcom @Ambarishrh last edited by

                    @Ambarishrh said:

                    http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html#TroubleshootingInstancesServerError

                    Did you check this?

                    Good find! I hadn't seen that! I'm already halfway through rebuilding the server anyways...

                    1 Reply Last reply Reply Quote 0
                    • Ambarishrh
                      Ambarishrh last edited by

                      I would suggest you still check the guide and fix it anyways the instance is free, but the knowledge you might get with that could be useful for ages 🙂

                      thanksajdotcom 1 Reply Last reply Reply Quote 2
                      • thanksajdotcom
                        thanksajdotcom @Ambarishrh last edited by

                        @Ambarishrh said:

                        I would suggest you still check the guide and fix it anyways the instance is free, but the knowledge you might get with that could be useful for ages 🙂

                        True that

                        1 Reply Last reply Reply Quote 0
                        • thanksajdotcom
                          thanksajdotcom last edited by

                          Read it over. No useful info. It basically says to verify you're using the correct username, which I am. Nothing more I can do without console access.

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post