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

Help restoring Cloudron backup on new server

Scheduled Pinned Locked Moved Solved Support
restore
4 Posts 2 Posters 1.0k Views 3 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.
  • timconsidineT Offline
    timconsidineT Offline
    timconsidine
    App Dev
    wrote on last edited by girish
    #1

    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 ?

    timconsidineT 1 Reply Last reply
    0
    • timconsidineT timconsidine

      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 ?

      timconsidineT Offline
      timconsidineT Offline
      timconsidine
      App Dev
      wrote on last edited by
      #2

      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

      scookeS 1 Reply Last reply
      0
      • timconsidineT timconsidine

        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

        scookeS Offline
        scookeS Offline
        scooke
        wrote on last edited by
        #3

        @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

        timconsidineT 1 Reply Last reply
        1
        • scookeS scooke

          @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).

          timconsidineT Offline
          timconsidineT Offline
          timconsidine
          App Dev
          wrote on last edited by
          #4

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

          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