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 Help restoring Cloudron backup on new server

    Support
    restore
    2
    4
    240
    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.
    • timconsidine
      timconsidine last edited by girish

      I decided to move the VPS of my Cloudron for bigger size/cheaper costs (from Linode to Netcup).
      I followed instructions in https://docs.cloudron.io/backups

      • made backup on old cloudron
      • did fresh cloudron install manually (wget etc) on Ubuntu 20.04
      • visited http://new-ip
      • chose small restore link at bottom of page
      • completed details of backup location (Digital Ocean Spaces)
      • got message waiting for DNS of my.<cloudron>
      • updated ip address of all domains in various DNS registries (I use the *.domain approach as registries not listed in Cloudron)
      • after allowing time for DNS propagation, visiting my.<cloudron> still takes me to old instance
      • visiting http://new-ip gives me 'you found cloudron in the wild'

      (a) How do I check the new cloudron for completion of restore of backup? (I have SSH access)

      (b) did I miss a step ?

      (c) is it just a case of waiting ?

      timconsidine 1 Reply Last reply Reply Quote 0
      • timconsidine
        timconsidine @timconsidine last edited by

        Maybe it was (c) just wait
        Network view after logging in on https://my.<DOMAIN> does now show the new VPS ip address

        Interesting that 23 apps installed but only 8 "app back online" messages.

        Will start to check apps data

        Sorry if original post was false alarm

        scooke 1 Reply Last reply Reply Quote 0
        • scooke
          scooke @timconsidine last edited by

          @timconsidine When I'm checking possible time-sensitive things like DNS propagation, I always use Incognito mode on Chrome (or the equivalent on other browsers). Very often a problem like you experienced is residual on the normal mode, but Incognito shows me what's current (since it doesn't use the cache).

          A life lived in fear is a life half-lived

          timconsidine 1 Reply Last reply Reply Quote 1
          • timconsidine
            timconsidine @scooke last edited by

            @scooke Thank you. Good tip. I shall use this.

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