Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Retired AWS Instance - Unknown Issue

Retired AWS Instance - Unknown Issue

Scheduled Pinned Locked Moved Solved Support
aws
7 Posts 2 Posters 1.3k Views 2 Watching
  • 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.
  • S Offline
    S Offline
    scuba9273
    wrote on last edited by girish
    #1

    Got notified my instance hardware was compromised, which forced a shutdown. After restart, I can see cloudron is still installed (I use InstanceConnect, not SSH) but am unable to get the cloudron dashboard to load.

    Following the basic troubleshooting I get this...

    Screenshot from 2021-09-20 10-40-14.jpg

    Then [systemctl status box] returns:

    Screenshot from 2021-09-20 10-40-50.jpg

    I have checked that DNS hostnames and resolutions are indeed enabled for my VPC on AWS.

    I also tried restarting the box, but was asked for a password, which I don't know what it would be.

    My skill level with AWS and Cloudron is, at best 3/10. Hoping someone can see where I'm going wrong here!

    nebulonN 1 Reply Last reply
    0
    • S scuba9273

      Got notified my instance hardware was compromised, which forced a shutdown. After restart, I can see cloudron is still installed (I use InstanceConnect, not SSH) but am unable to get the cloudron dashboard to load.

      Following the basic troubleshooting I get this...

      Screenshot from 2021-09-20 10-40-14.jpg

      Then [systemctl status box] returns:

      Screenshot from 2021-09-20 10-40-50.jpg

      I have checked that DNS hostnames and resolutions are indeed enabled for my VPC on AWS.

      I also tried restarting the box, but was asked for a password, which I don't know what it would be.

      My skill level with AWS and Cloudron is, at best 3/10. Hoping someone can see where I'm going wrong here!

      nebulonN Away
      nebulonN Away
      nebulon
      Staff
      wrote on last edited by
      #2

      @scuba9273 hi and welcome here.

      For a start, can you run the star.sh script with sudo as it requires root access.
      Then we can hopefully see some more issues.

      S 2 Replies Last reply
      0
      • nebulonN nebulon

        @scuba9273 hi and welcome here.

        For a start, can you run the star.sh script with sudo as it requires root access.
        Then we can hopefully see some more issues.

        S Offline
        S Offline
        scuba9273
        wrote on last edited by
        #3

        @nebulon Thanks for the quick reply!

        Do you mean start.sh? I have not spent much (any) time using dockerfile etc since I just installed cloudron straight onto my instance and haven't poked around much.

        Using the browser-based SSH, I am root, though. I was able to set a password and restart the box, and one of the host issues w/ yellowtent did resolve... but no fix.
        Screenshot from 2021-09-20 11-10-32.png

        1 Reply Last reply
        0
        • nebulonN nebulon

          @scuba9273 hi and welcome here.

          For a start, can you run the star.sh script with sudo as it requires root access.
          Then we can hopefully see some more issues.

          S Offline
          S Offline
          scuba9273
          wrote on last edited by
          #4

          @nebulon I think I did what you asked... Here's the gist.
          Screenshot from 2021-09-20 11-28-47.jpg

          1 Reply Last reply
          0
          • S Offline
            S Offline
            scuba9273
            wrote on last edited by
            #5

            I think I may have found the issue? When AWS retires hardware, on restarting the instance, a new public ipv4 address is generated. Pinging the new one shows this text on the page...

            You are seeing this page because this domain points to Cloudron server IP but no app is installed on that domain.

            If I change all the A records in godaddy, maybe that will solve? Or do I need to alter some config files within cloudron box?

            S 1 Reply Last reply
            0
            • S scuba9273

              I think I may have found the issue? When AWS retires hardware, on restarting the instance, a new public ipv4 address is generated. Pinging the new one shows this text on the page...

              You are seeing this page because this domain points to Cloudron server IP but no app is installed on that domain.

              If I change all the A records in godaddy, maybe that will solve? Or do I need to alter some config files within cloudron box?

              S Offline
              S Offline
              scuba9273
              wrote on last edited by scuba9273
              #6

              THIS SOLVED IT

              1. AWS instance restarted - new public ipv4 issued
              2. Update new A records in DNS with new ipv4
              3. SSH into instance and run migration command and restart box

              Be sure to purge your browser like the troubleshooting docs say: "You may have to purge the site from your browser's history to get over HSTS certificate issues."

              BACK IN BUSINESS thanks for your help @nebulon

              nebulonN 1 Reply Last reply
              2
              • S scuba9273

                THIS SOLVED IT

                1. AWS instance restarted - new public ipv4 issued
                2. Update new A records in DNS with new ipv4
                3. SSH into instance and run migration command and restart box

                Be sure to purge your browser like the troubleshooting docs say: "You may have to purge the site from your browser's history to get over HSTS certificate issues."

                BACK IN BUSINESS thanks for your help @nebulon

                nebulonN Away
                nebulonN Away
                nebulon
                Staff
                wrote on last edited by
                #7

                @scuba9273 glad you figured it out and thanks for sharing the solution!

                1 Reply Last reply
                0
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                • Login

                • Don't have an account? Register

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • Bookmarks
                • Search