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


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved Retired AWS Instance - Unknown Issue

    Support
    aws
    2
    7
    286
    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.
    • S
      scuba9273 last edited by girish

      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!

      nebulon 1 Reply Last reply Reply Quote 0
      • nebulon
        nebulon Staff @scuba9273 last edited by

        @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 Reply Quote 0
        • S
          scuba9273 @nebulon last edited by

          @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 Reply Quote 0
          • S
            scuba9273 @nebulon last edited by

            @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 Reply Quote 0
            • S
              scuba9273 last edited by

              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 Reply Quote 0
              • S
                scuba9273 @scuba9273 last edited by 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

                nebulon 1 Reply Last reply Reply Quote 2
                • nebulon
                  nebulon Staff @scuba9273 last edited by

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

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Powered by NodeBB