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. Redash restore failure

Redash restore failure

Scheduled Pinned Locked Moved Solved Support
updatepostgresql
6 Posts 2 Posters 1.2k 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.
  • C Offline
    C Offline
    cdolson
    wrote on last edited by girish
    #1

    After some recent updates this weekend our Redash installation is now unresponsive. Attempting to restore, or clone a working backup to a new instance, throws this error.

    An error occurred during the restore operation: Addons Error: Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/dc95a87a-2048-4187-b2a7-7310de48e50a/postgresqldump to http://172.18.30.2:3000/databases/dbdc95a87a20484187b2a77310de48e50a/restore?access_token=REDACTED&username=REDACTED: status 408 complete false
    

    Any help anyone could offer would be greatly appreciated.

    girishG 1 Reply Last reply
    0
    • C cdolson

      After some recent updates this weekend our Redash installation is now unresponsive. Attempting to restore, or clone a working backup to a new instance, throws this error.

      An error occurred during the restore operation: Addons Error: Unexpected response code or HTTP error when piping /home/yellowtent/appsdata/dc95a87a-2048-4187-b2a7-7310de48e50a/postgresqldump to http://172.18.30.2:3000/databases/dbdc95a87a20484187b2a77310de48e50a/restore?access_token=REDACTED&username=REDACTED: status 408 complete false
      

      Any help anyone could offer would be greatly appreciated.

      girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #2

      @cdolson are you on 7.4.0 ? We got a couple of reports on error when restoring to Postgres (pretty much the same error you posted). So , just cheking if these are all related.

      C 1 Reply Last reply
      1
      • girishG girish

        @cdolson are you on 7.4.0 ? We got a couple of reports on error when restoring to Postgres (pretty much the same error you posted). So , just cheking if these are all related.

        C Offline
        C Offline
        cdolson
        wrote on last edited by
        #3

        @girish Yes, 7.4.0

        girishG 1 Reply Last reply
        0
        • C cdolson

          @girish Yes, 7.4.0

          girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by
          #4

          @cdolson are you able to contact us at support@cloudron.io ?

          C 1 Reply Last reply
          0
          • girishG girish

            @cdolson are you able to contact us at support@cloudron.io ?

            C Offline
            C Offline
            cdolson
            wrote on last edited by
            #5

            @girish done

            1 Reply Last reply
            0
            • girishG girish moved this topic from Redash on
            • girishG Offline
              girishG Offline
              girish
              Staff
              wrote on last edited by
              #6

              This was a bug in 7.4.0 and is now fixed in 7.4.1.

              We updated node to v18 (from v16). There was a subtle but impact change hidden... In node 16, the requestTimeout was 0. This meant unlimited time. In node 18, the requestTImeout is now 5 mins. This meant that large restores were failing if the upload didn't finish within 5 mins.

              1 Reply Last reply
              2
              • girishG girish marked this topic as a question on
              • girishG girish has marked this topic as solved on
              • girishG girish referenced this topic on
              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